Lemmy account of natanox@chaos.social

  • 0 Posts
  • 7 Comments
Joined 3 months ago
cake
Cake day: October 7th, 2024

help-circle
  • Can confirm. Meddled with it a little bit a while ago trying to productively use it to host Lutris installer files. It’s an absolute mess; slow, unreliable, without proper documentation and a really bad default node application.

    Also it managed to get our server temporarily banned by the hosting provider since the “sane default settings” includes the node doing a whole sweep of your local subnet on all NICs respectively, knocking at multiple ports of every device it can find. Because the expected environment of a node apparently is your home network… a default setting that caused problems for many people for many years by now.

    A project like in this post might benefit from looking at more modern/mature reimplementations of IPFS’ concept, like Veilid (which would also offer additional features as well).





  • This. I wholeheartedly concur that corporate “social” media is fucking shit up like hell, however as long as people are socially stuck there they will be around, as as long as that is the case people who need to make a living will have to roll out stuff and communicate with people there.

    In fact this is specifically the kind of tool a friend and me looked for but couldn’t find as FOSS until now, although we’d definitely need support for the Mastodon API / Lemmy.

    One may argue which platforms to choose (depending on what you want to show people or who you want to reach). But completely abandoning garbage platforms ain’t possible right now, especially for small businesses who need to be seen somewhere.



  • This is part of Googles strategy. Ever since the Chromium engine took off enough and everyone else fell behind they began introducing more and more changes that merely benefits them, with less public debate or proper communication (or even adherence to common standards). Last thing I remember, aside of manifest v3, was them killing off JPEG XL as it was a competitor to webp and webm (which they control). JPEG XL was actively worked on and would’ve probably turned out better before they killed it without any previous notice.

    Given Googles dominant market position, their influence and everyone wanting to cut corners wherever possible sometimes Firefox support is just ignored.

    tl;dr It’s not Firefox’ fault. It’s Google’s sabotage.