terribleplan

Pretty sure it needs to be https://$user:$pat@github.com/username/repo.git#branch.

1. You host it yourself
2. You can get a cool domain name
3. It's pretty low maintenance

I would still go with one that isn't one of the biggest. My general advice is to find one that fits the vibe you're going for, communities you're interested in (e.g. some are focused on art or cybersecurity, etc), or is somehow tied to your locality. It shouldn't matter that much, though some servers will be a little more (or less) strict with things like federation, content warnings, alt text, etc. Usually the server will have some info telling you some of this, and their admin should be linked and likely has a post or two pinned to their profile explaining some of this as well.

I am partial to kind.social, though have opted to run my own instead of joining up anywhere.

It depends on what specific thing you want to add geoblocking to, but often something like the MaxMind GeoIP database, which then can feed into a firewall to pre-emptively geo-block at a connection level, or as part of e.g. nginx geolocating the IP a of the connecting IP then making the blocking decision at request time.

There's a project that works with Traefik's forward-auth middleware to do this, which is probably how I would go about it if I wanted it at an HTTP level.

No, these issues are pretty much by-design. In ActivityPub IDs are inherently tied to the domain on which they were created. Based on the nature of federation it is safe to assume someone somewhere will still go looking for that thing via the outdated URL.

If you're taking that approach make sure you shut down the stack before you copy the data over so everything gets copied over consistently (e.g. the DB isn't in the middle of a write), and yes it should pretty much be that easy.

Whoo, can't wait for this season of "Wait, I thought we made progress last episode/chapter!?"

I am a bit behind on the manga, but it has been really hard to be motivated to read it. It feels like any minuscule piece of progress is followed by immediate regression. I was very much in the mindset of "Fuck you, I'll see you next week" for a while, haha.

I'll comment my thoughts after I get around to watching the episode a bit later today.

Things don’t get backfilled, so until a new action happens on an old post/comment/etc they won’t show up on your instance. New things should make their way in eventually though.

Taking the link of a specific post/comment from the community instance and searching for it from your instance should populate it on your instance, just like you probably had to do to get this community to show up so you could subscribe/post at all.

There are backfill tools/scripts, but unless you really want old posts I wouldn't use them. It unnecessarily increases the load on already struggling popular/overloaded instances like lemmy.world.

If you find a decent alternative let me know. I have been looking for a while and not found anything that supports the full feature set I want (including Twilio).

Agreed, I recommended filtering to only http(s) links in the github issue, I just made this x-post. I don't see a strong reason to let people link to weird things like file: and data:, or deeplink to installed apps on your computer/phone. Filtering the scheme to just http(s) is how Nutomic seems to have fixed it in the backend from what I can tell (I am not a rust dev).

May the Lord have mercy on us all.

The EFF is neither right nor left wing, they advocate for privacy and freedom. Free speech includes speech you may not like, and it certainly includes things I do not like. Luckily one of the freedoms generally included in "free speech" is the freedom to ignore, shun, call out, shame, etc. those who say things I don't like if I so choose (like what you are seemingly trying to do with this post, in fact).