• 0 Posts
  • 20 Comments
Joined 6 months ago
cake
Cake day: February 27th, 2025

help-circle



  • manxu@piefed.socialtoLinux@lemmy.mlMacOS Preview equivalent
    link
    fedilink
    English
    arrow-up
    2
    ·
    2 months ago

    Completed task successfully! For future readers, the process seems to have slightly changed. Now you go to Okular preferences, Annotations, Add annotation, call it Signature, etc. You can even resize the signature, which is really useful when the resolution of the PDF varies.




  • Did you look at Pelican? I share the frustration with much of Hugo’s infrastructure: the template language is buggy and inscrutable, and the plugin architecture wanting.

    I ended up with Hugo, but I considered Pelican. It uses standard Jinja templates, which I find much more rational (but it might just be me) and I recall there were plugins for a lot of things, including different source formats. The code is written in Python, so that even if there isn’t a plugin for a format you need, there probably is a Python library for it and it should be relatively easy to make it a plugin.

    Crap, now I want to switch to Pelican…


  • Hugo watch mode (both server and build) does not produce accurate sites on change and is really meant for development. I find after a developing for a while, I have to kill the process and restart it and then things are “fresh”

    From reading the documentation, I strongly have the impression that hugo focuses on being fast on re-render and that the idea is to build and deploy to public site each time there is a change. The big difference is probably whether to render locally and push the generated content, or to push the source markdown and render remotely (which I chose).


  • I ended up with Hugo, a git repository, and a cron job for the build. I write an article, check it in, the server picks up the git change and rebuilds the site. What I like about the setup is that the server only has the binaries hugo and git, and a shell script for the rebuild. Also, I write in Markdown, add media to the git repository, and articles are published soon after I check in without any remoting on my part.

    I did look at WriteFreely after the setup, though. I find the minimalist design very beautiful. Didn’t switch to it, but may look at it again for another project. https://github.com/writefreely/writefreely




  • I used to work for one of the big Internet companies when we came out with the Personals product. We poured over the data constantly, mostly because the thing was so insanely cheap to make (2 devs, 1 ued, 1 pm, 3 months) and so insanely lucrative.

    Basically, there were two types of sites: data/matrix driven where you could get a ton of results and filter them as you saw fit, and algorithm driven, where you would get a select number of profiles presented that you could either interact with (swipe right) or deny (swipe left).

    The first kind generally suffered from a very simple problem: people don’t meet and like people because of data. We couldn’t figure out why people like people, because we didn’t see that part of the equation, but we saw that the data driven approach pushed people into being too selective on the data, ending up with really unrealistic expectations, and correspondingly with people increasingly lying to match those expectations. We could tell both, because we could see the filters (e.g. the scary number of men in their 50s having 25 as max age for their dates) and the distribution of the data, that didn’t match any normal distribution (e.g. the remarkable doubling of people with ages ending in 9).

    The algorithm-driven approach suffers from doom scroll syndrome. Since you are separated from the perfect person for you by a bunch of “losers” in the way, you scroll over them quickly to get to the good stuff. Nobody gets the time they deserve, and while the algorithmic approach doesn’t allow you to filter unrealistically, it gives you impatience and makes the unrealistic expectations worse.

    Unrealistic expectations breed lies. If only the impossible is good enough for you, only the liar can deliver.

    I left as we were discussing a blended approach: the algorithm presents a grid of potential mates it selects for you, but you can see them all (a thumb, at least) and interact with each independently. Then the company hit trouble and Personals was frozen in time.

    My takeaway: for a change, capitalism and monetization are not the core problem. People’s sense of entitlement is.



  • I went the same direction, from WordPress to static site generation. I did the same evaluation as you are trying to do and ended up with Hugo, mostly because there is a lot of support available for it. My runner up was Pelican, because I was fluent in Jinja2, but I didn’t want to mess around with the templates and Hugo’s were prettier. Sue me, I am shallow.

    The one regret I have about Hugo is that the templating language is challenging. I am trying to be as neutral as possible, but it seemed like even simple things were complicated to achieve. If someone would come up with a Hugo that speaks Jinja2, I’d be really delighted.

    Other than that, conversion from WordPress to Hugo was relatively straightforward, despite needing to find a gallery component and converting menus. Hugo is indeed very fast in processing, which become important when your blog has thousands of articles.

    I set up the blog as a private git repository. The server pulls from it, then runs Hugo and a full text search engine, and the content is visible and searchable within five minutes on update.


  • I think it’s the “basically” part in basically right back where we started that makes the difference. Even if 100% of Fediverse users were on a single instance, once that instance starts pulling Musk moves, the users can move somewhere else.

    Only if that instance defederates from everyone else do we get the Twitter situation again. Or, since that’s actually what happened, Truth Social, which I think is just a slightly modified Mastodon instance with federation disabled/deactivated.


  • manxu@piefed.socialtoLinux@lemmy.mlscanner
    link
    fedilink
    English
    arrow-up
    4
    ·
    3 months ago

    I used to have a Canon Pixma, and the SANE drivers recognized it and scanned from it with no issues, down to the ADF feeder. It was really surprisingly simple, zero setup configuration.

    I basically just used the preinstalled software, Skanlite, and it showed with the scanner pre-selected and ready to go.

    Of course, YMMV.


  • Interesting study. It says, in a nutshell, that it can replicate previous findings that physical fitness in youth reduces the rate of premature mortality due to many conditions, like cardiovascular issues or cancer. That was expected.

    Then it looks at the rate of premature mortality due to random accidents (I assume things like car crashes and being run over by trolleys) and finds the same reduced rate, but there should be no correlation.

    So something non-causal is probably happening to reduce the stroke, heart attack, and cancer risk of people that were physically active as young adults.