BakedCatboy

I think you can use Immich external libraries for this, also to be extra safe you can just mount your external images folder as read only by adding :ro to the docker volume mount so that the container won't be able to modify anything as a precaution.

The !mutual_aid@hexbear.net community seems similar to what you're asking for. I'm not sure if there are more similar comms on other instances but that's just the one I know of.

I think saying "don't blame me because I voted for trump" when voting for Trump is exactly why they should be blamed.

Yeah I thought odometer fraud was like a serious thing, I wonder if it applies here.

*Always has bean

The other servers do cache the content for some time yes, but if your server is based in a country not friendly to your posts then you are vulnerable to takedowns as you say and you could be inconvenienced by having the admins of your server delete your account or something.

The benefit I'm saying we have in the fediverse is that you can pick a server in a politically safe area (ie outside Turkey in this case), so they are less likely to comply, especially if they are small or don't care about being blocked by that country (that's usually the only thing they can do unless you have an office or staff there that can be arrested - less likely to be the case if your server is run by some dude in another country).

I'm saying that if your home server (mastodon.social in your example) is outside of Turkey, then there is less reason for them to comply in the first place because they only risk the mastodon.social server being blocked in Turkey. That one is a bad example because they're one of the largest and they might have a bunch of users in Turkey, so if you want to be extra safe, you'd want to pick a server that isn't so big so that they are less likely to care about complying with some other county that they might not have any users from.

If the server you use is based inside the country that has a problem with your content, then you'd be screwed - though all the other servers will still mirror and cache your content for a bit even if you get taken down.

The resiliency lies in the fact that you can choose to register in a country that is politically friendly towards your posts or if your home country is friendly but you want to avoid being taken down, you can self host a single user instance and refuse any requests from other countries.

Edit: Now that I think about it, there's also the fact that as long as the account itself isn't limited by their home server, the content in question would be accessible through the federated copies, so if the home server isn't within Turkey / jurisdiction and doesn't take down the account, the country trying to take down the content would need to send takedown requests or request to geofence the content to each individual server on the entire fediverse - since the home server would be freely federating it to every server with users who follow the content, otherwise they would need to block every fediverse server and every new one every day that more pop up.

The difference is that if your home server is outside of Turkey then you can tell them to kick rocks. Bluesky probably complies because they don't want to be blocked from Turkey. In a truly decentralized system like activitypub, only the server hosting the account / content in question risks being blocked, which means almost nothing the closer you get to a single account instance. Meanwhile every other server not in Turkey would not notice a difference.

Edit: this was under the assumption that they took it down completely, but it looks like they only geofenced it. Regardless, if they are pressured enough they would be capable of completing hiding an account worldwide, which isn't possible with activitypub without the legal alignment of every instance's country since bluesky on the other hand has sole control of the only relay.

I use a .dev and it just works with letsencrypt. I don't do anything special with wildcards, I just let traefik request a cert for every subdomain I use and it works. I use the tls challenge which works on port 443, so I don't think HSTS or port 80 matters, but I still forwarded port 80 it so I can serve an http->https redirect since stuff like curl and probably other tools might not know about HSTS.

I think we'll have to agree to disagree then, I don't think that is at all the obvious interpretation and I don't think everyone needs to clarify where they live when talking about it to "avoid the issue".

Imo if people making assumptions about others living in the US annoys you then you should find it more annoying when someone assumes where you live AND assumes you intended to be presumptuous about it.

Is it wrong to want to talk about the place you live in without telling people where you live? Should everyone be required to state the place they live in any time they talk about it? I don't really see what the problem is with speaking about your place of residence without revealing where you live. I don't get how not mentioning where you live means you assume everyone knows. Maybe you not knowing is intentional.

While I think it's annoying when people assume others live in the US, I think it's even more annoying to both assume people who don't mention where they live must live in the US and also assume they intended you to know that they live in the US.