• 20 Posts
  • 606 Comments
Joined 8 months ago
cake
Cake day: November 3rd, 2023

help-circle







  • kbal@fedia.iotoFediverse@lemmy.worldLemmy is a failed Reddit alternative
    link
    fedilink
    arrow-up
    10
    arrow-down
    1
    ·
    edit-2
    1 day ago

    I’d not yet call it failed, but it’s not yet fully succeeded either. To my mind, one impediment is something that lemmy.world shares with today’s reddit: If you look at the front page it’s 99% memes and images. That’s the first impression people get, and it probably drives away a lot of people who might want anything else. We need those people to make more text-based communities come alive, if it’s to evolve into anything like the old reddit.

    I mean obviously there are lots of people who do mostly want to see memes and that’s fine, but I think it’s getting to the point where it might be useful to have an option that filters out all posts that are just a title and an image.



  • kbal@fedia.iotoLinux@lemmy.mlSSH as a sudo replacement
    link
    fedilink
    arrow-up
    13
    arrow-down
    7
    ·
    edit-2
    1 day ago

    It has some advantages. It can be configured with simple text files and normal filesystem permissions. The sshd code is mature and has a proven record of good security. It doesn’t add yet another thing to systemd that has no business being part of systemd.









  • In this case it’s not “carbon neutral” as in carbon neutral if you subtract the credit that a carbon offset company gave us for using our giant pile of money to bribe someone not to burn down a bit of rainforest on the far side of the world. It’ll be genuinely carbon neutral. Unlike the rest of us, F1 can afford to use the finest pure synthetic fuel made from organic hand-picked potatoes with energy from 100% green electrons.

    It may be only a small gesture compared to the vast enterprise of shipping so many tons of equipment and people all around the world, but it’s sort of cool nonetheless.



  • Interesting choice over there to close the issue so quickly rather than asking for more info, although you didn’t give them much to go on.

    I wonder what was the resolution of the previous problem that frequently caused this sort of thing? Was the error handling improved such that we might reasonably expect the processing to keep going when it hits something it doesn’t like, or was it just a quick fix for the one specific thing that happened to be breaking it at the time? Did that one make it to the github tracker?