if this were to happen trust me when i say pluton’s role in enforcing it will be little to none.
if this were to happen trust me when i say pluton’s role in enforcing it will be little to none.
as far as i can tell this particular image is fake. and as far as i know pluton does not work like that.
DNS blocking is the most unreliable way of blocking youtube ads you can imagine.
you could write a script to OCR your entire screen and click skip ad and it’d be more reliable than DNS blocking
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
no if you look at a billboard you’re observing an ad. don’t do that.
afaik some people are worried about the “legal enforceability” of the unlicense, which is funny given the point of it is to be an explicit “go do what you want” license.
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
there are people that do this kinda thing for mastodon (see masto.host as an example), so it’s only a matter of time before lemmy hosters of this nature will pop up.
instances need to be constantly online under the same domain to receive new posts. you can’t really host an instance from your home without some kind of tunnel or ddns setup, and you surely can’t host one from a potentially metered mobile connection.
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.
welcome to blahaj. our image uploads and the lemmy frontend constantly breaks but everyone’s really chill and really gay.
funny thing is afaik google is the one who’s registering .zip TLDs
or at least they were until they sold google domains to squarespace
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)
it can be pretty useful for really specific cases, but i’m not exactly sure if this is one of them
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.
fair enough. the files i upload tend to be pretty small (<25-30 MBs) so i haven’t needed to think about details like dash. there are a few projects like https://github.com/ShaneIsrael/fireshare and https://github.com/Hubro/clipface i could find with a quick search but none of them try to do anything adaptive (unless you go for a full blown solution such as peertube which doesn’t seem to be what you’re looking for)
epic megapost