@fwc@prettygood You _can_ revert that one commit, but do you really want to set up yourself for debugging hell, when they eventually start to depend on new functionality not preset in 12?
That said, I would still be running version 10, if Pleroma didn't drop support for it.
@prettygood@fwc The deprecation policy just states that they remove support for software not supported upstream.
Depending on how stupid Synapse is (never tried it), I would just dump the whole DB as a backup, test the upgrade on a different system, and if all goes well, go through the upgrade process on the main system, and reindex the whole DB after the upgrade. It's always possible to rollback a version with DB backups.
@fwc@prettygood The DB version usually doesn't matter to the software connecting to it, unless it depends on some new functionality which should have been noted somewhere.
The commit that removes the support has nothing of value in the message.
@nyanide@meso You don't really attract attention from people that might want to take advantage of that clause I think. It's not like they scrape domains registered with them for "bad" content.
What caught me of guard wasn't that they had the hate speech clause. It was that hate speech wasn't defined anywhere in their terms. That's what set the alarms for me. If the listed example, or clearly defined, I wouldn't mind it as much.
@nyanide@meso Yeah, the ryona.agency thing is understandable considering they also don't want to manage their own crypto platform. I don't even know if Frantech accepts crypto without some KYC from the crypto platform. I've never tried to pay them via crypto.
And the nameless company thing... I'm not doxing myself today. :DD It was a frustrating email chain, but they worked it out. I think they are still using them to this day even.
@nyanide@meso The most notable one was cum.salon which used to be on Porkbun and got seized by them (doxing). getgle.org also had some problems with them. They called the mascot CP or something I think. Quite ironic considering their track record with actual CP/loli. A nameless company which I worked for had few problems with their support after some trolls decided it would be funny to send abuse emails to them.
Other than that, they are usually fine, but their TOS irks me the wrong way. The hate speech clause was very broad when I last checked it months ago (they might have changed it) and since they are sometimes very trigger happy with it, I don't like it.
ryona.agency almost didn't get renewed because Visa/MasterCard cards from the Russia aren't obviously allowed and their crypto options suck, but that's a different thing.
@meso Oh, that's fucking stupid. Anyway, Namecheap is probably the only good registrar left. Epik has a laughably shitty web UI that barely works, got purchased and immediately stared complaining about hate speech on Twitter and who knows how good their security really is. Njalla outright just seizes your domain whenever they want to, because it's ran by the pirate bay owners who really like antifa. And Cuckflare is well... Cuckflare.
@meso Porkbun has a history of seizing domains whenever they like to based on their hate speech clause somewhere buried in their TOS. They basically pull the same shit Hetzner does.
@feld@dvl@SlicerDicer A dead battery that fails immediately after getting put under a load probably doesn't hold voltage and might have higher internal resistance. That's how I would check it. Alternatively putting a small load like a few 12 volt halogen bulbs and watching the voltage might also do the trick. A dead battery should drop voltage quicker than others.
@snacks@meso It's also looks like the dates and time are lies. They don't represent reality. Ignore the newest post, I've fetched that one through IEx manually.
Try running pleroma_ctl remote or whatever is the right command to get into IEx and run this command Pleroma.Object.Fetcher.fetch_object_from_id("https://transfem.social/notes/a2yvk641e0s800mg") It should spew out tons of debug output and end with {:ok, %Pleroma.Object{...}}.
If you are blocked and they have signed fetch enabled (probably do), you should get something like {:fetch, {:error, :forbidden}}. At least that's what Mastodon gives out.
If you can force fetch the objects, their federation is just broken in true Sharkey fashion.
@meso@snacks Or, it could be that the last request was 9 months ago, which doesn't really check out. <time>m should be minutes, but unmodified misskey has "min" to denote minutes.
What's weird is that there are apparently zero users anybody from Netzsphaere follows and nobody from TFS follows a Netzsphaere user. That's certainly strange.
@meso@snacks I don't really know. The last request was 9 minutes ago (as can be seen in the screenshot). But also the latest change was 9 minutes ago, so that might be the time of block.
@Suiseiseki@snacks Basically all pisskey forks removed that API from the public. Sharkey doesn't show the "blocked" instances as a filter in the /instance-info route and Iceshrimp removed the federation tab completely (probably only for unauth access). There's basically no way to tell without looking at the logs which might have some error usually related to signed fetch (I know Mastodong does that, put I have no idea about *key).