as far as i can tell this particular image is fake. and as far as i know pluton does not work like that.
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)
Oh no it’ll federate alright.
The thing about ATProto is that unlike AP they don’t seem to expect each instance to have it’s own community with it’s own rules and vibes. They seem to be using federation just as a way to “scale up”.
If they can get any non-bluesky-the-company folk to create instances then that’s just scaling they don’t have to pay for and a convenient legal scapegoat for the inevitable consequences of their lax moderation. Why wouldn’t they federate?
and for those that don’t like CC licenses applied to code, 0BSD is also an option
it depends on the implementation. lemmy does have something similar but it’s not as aggressive as email and in the peak reddit migration times it wasn’t uncommon to have un-federated replies and posts from all the instances being overloaded.
also that queue is stored in memory so if the server dies or gets updated or otherwise restarts it won’t bother with old stuff
images are the real issue. text is extremely small and most instances should be able to handle even the largest text and link based communities.
in fact they can’t participate on lemmy if they couldn’t because the text of a post (and all the comments) gets copied to all instances subscribed to a community
and of course moderation can be a concern as well, but if you’re not ready to moderate you shouldn’t host anything other than a single user instance anyway.
there’s more to “the general public” besides 2 instances. beehaw defederated from .world and sijw because the mod tooling to handle a huge influx of people isn’t ready, and it still isn’t ready. (and the rest of their defederations are an off the shelf mastodon blocklist import which all instances should do imo and a few explicitly unmoderated instances. oh and porn i think)
beehaw federates just fine with the instance i’m on, for example.
if they wanted to defederate completely, lemmy does support allowlist federation, and i’m pretty sure their admins know about it.
posts and comments are hosted on the instances their authors come from. if the instance hosting a community gets yanked away without sending proper deletion requests to the network, all those posts end up hidden but accessible with their “canonical” link (which you can find from the rainbow star looking button on each post)
for example, the canonical link to OP’s post is https://sh.itjust.works/post/2882678, and if db0 goes down without asking shitjustworks to remove this post (i.e. if it gets seized) that post will stay there until the sijw admins or OP themselves takes it down
(and if an instance does get seized other piracy-friendly instances can immediately defederate from that instance to “reject” any future removal requests wink wink nudge nudge)
the allowed instances list acts as an allowlist, meaning you’d be defederating yourself from the rest of the fediverse (and only federating with the instances you allow).
if that’s what you were going for ofc it’s your right and i sure won’t stop you from doing that, but i feel like you’ve misunderstood what it is.
if you have a hard time choosing between Gitea and Forgejo I recommend picking Gitea for now, as they haven’t done anything bad just yet, but if they do Forgejo supports migration from Gitea.
iirc there isn’t an official way of migrating the other way so if Forgejo fucks up you may end up out of luck
it’s partly because everything has public/private certificates, but also partly because there isn’t much synchronization going on after the initial “push”. if you shut an instance down and modify the database directly without informing other instances (say, you remove an account) then other instances will not be able to tell and will drift out of date, essentially making that specific thing unusable for any instance that has previously interacted with it. if you expand that out to, say, wiping and re-creating an entire database, then you end up with so much uncertainty that you may as well start over from a fresh domain
well I just checked and while “sync contacts” did not turn itself on, “allow contacts to add me” did. there’s definitely something going on