• 2 Posts
  • 60 Comments
Joined 1 year ago
cake
Cake day: June 9th, 2023

help-circle





  • also remember just like how lemmy has it’s kbin, mastodon has it’s interoperable alternatives.

    i bet a fair bit of the complaints i hear from people on lemmy (low character count, wanting to follow topics instead of people) would be solved by trying out a misskey fork such as firefish, iceshrimp or sharkey.

    i don’t think there’s any instance out there with a char count lower than 1000, and antennas are really good (why limit youself to following a single hashtag when you can follow any number of arbitrary keywords?) if you’re in a well federated instance (provided you’re ok with them not feeding into your home feed and them not being retroactive (so after you set up an antenna you’ll need to wait for new posts to filter in))

    they aren’t as polished as mastodon since mastodon kinda ate everyone’s lunch in terms of developer attention (and upstream misskey is an almost one-man-show mess developed entirely in japanese which is why everyone prefers to fork instead of collaborating), but they’ve been getting really good.

    just avoid flagship instances (> 1k active users) for the time being. scaling is still something not many of them have solved just yet






  • One of the reasons I use containers instead of installing things directly is that i can completely uninstall a service by deleting a single directory (that contains a compose.yml and any necessary volumes) and running a docker/podman system prune -a

    or that i can back up everything by backing up a single “containers” dir, which i could have on a subvolume and snapshot if i wanted to

    systemd/quadlet on the other hand makes me throw files in /etc (which is where you’re supposed to put them, but ends up resulting in them being tangled together with base system configuration often partially managed by the package manager)

    The Solution™ to this is configuration management like ansible or whatnot, which needlessly overcomplicates things for the use cases i need (though they’re still useful for getting a base system “container ready” wrt ssh hardening and such)

    tldr: i want my base system to be separated from my services, and systemd integration is the exact wrong tool for this job


  • In Logseq, everything is a nested list. This feels like a limitation, but I’ve been preferring it. The decision is made for you: you’re going to jot this information down as a list. So then you just start writing it.

    Oh - this sounds interesting.

    Whenever I needed to jot down any notes I’ve been finding myself just writing plain .txt files with bullet points, and trying tools like Obsidian or TiddlyWiki I always ended up being overwhelmed with the amount of stuff I could do (and with all the customization options) that I never got around to actually writing things down. I’m definitely gonna look into how Logseq works.

    (Although I have to say, their website does look a bit “too hype-y” for my liking. IDK how to explain it, just a gut feeling. Still, at least it’s FOSS so it can’t be too bad)







  • A long-running web thing like Lemmy doesn’t need the processing benefits of native compilation, and can avoid memory vulnerabilities with a garbage collector. Most things it does are IO bound (receive data from other servers, send data to other servers, occasionally render some HTML, interact with a database…) so you’re really not benefiting from anything specific to Rust, but you are losing a significant amount of developer effort into things like working with the borrow checker or the infamously long compilation times that could instead go into implementing functionality.

    You could make something just as performant as Lemmy is today with Python or JS (JS would particularly work well given the prevalance of JITs).


  • Eh, I’m wary of kbin in it’s current state mainly due to how little instances there are. That’s generally not a good sign for any federated software. (Maybe deployment is too complicated? Maybe it guzzles server resources like no tomorrow?)

    Both instances I’ve signed up to have already shut down, and from what I’ve heard the mod tooling is somehow even worse than Lemmy’s. It definitely needs more dev work before it’ll really fill that role.


  • I’d been eyeing azorius.net lately considering it’s much smaller/younger than Lemmy and already federates (and might make an interesting foundation to build something out of before it grows too large, hint hint to anyone who actually knows Go) but I don’t have the Go experience to actually go through its code.

    I’ve been experimenting with ActivityPub on my own time and I am kinda starting to understand why all AP projects end up being large messes. It’s spaghetti code all the way across the fedi.