ShittyKopper [they/them]
  • 2 Posts
  • 25 Comments
Joined 1Y ago
cake
Cake day: Jun 09, 2023

help-circle
rss

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


if this were to happen trust me when i say pluton’s role in enforcing it will be little to none.



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


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?


If it’s on the play store and if you have it (but don’t have the play store itself) Aurora Store can download paid apps given a Google login that owns those apps (but it’s technically against the TOS and could get you banned)




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.



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.


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


You’d have to be significantly more careful with backups, as it’s really easy to effectively “burn” a domain from federating over AP ever again (at least to instances that federated with it before), but otherwise it should be reasonably automatic as federation gets implemented piece by piece.


How do you handle semi-private services?
For completely private services, the obvious answer is a VPN. But what about the ones that need to be "partially" public? Whether just read only, or with restrictions to publicly registered accounts. For example, If I wanted to open up a git host where I allow public registrations so they can send issues/patches but can't create repos (kinda impossible with pull requests but you get my point) Is there any specific *thing* you can do, or do you just disable registrations completely except for something "out-of-band" (ask me on XYZ to create an account for you, git send-email, mirrors to public services, etc...) Of course, individual software may have access control features built in, but as a whole, is there anything reasonably generic?
fedilink

What’s your “base” stack of choice?
How do you set up a server? Do you do any automation or do you just open up an SSH session and YOLO? Any containers? Is docker-compose enough for you or are you one of those unicorns who had no issues whatsoever with rootless Podman? Do you use any premade scripts or do you hand craft it all? What distro are you building on top of? I'm currently in process of "building" my own server and I'm kinda wondering how "far" most people are going, where do y'all take any shortcuts, and what do you spend effort getting just right.
fedilink