@oliviavespera@spacey.space why does a secondary relay need explicit permission from the source instance to have their content relayed?
If the source content is public then there's no discussion to be had, there are no grey areas, the post is public.
It sounds like you're trying to add in layers of privacy to a visibility scheme ("public") that does not have any.
@stefano That’s foul play. If it’s easily doable, maybe put up an, um, “special” blog, specifically for this domain? One that it would probably not like being read aloud? Because I assume that the nonconsensual harvesting is done automatically.
@luca Hmm, sounds like you know more than me. I thought there was a more gradual transition to the Mastodon server.But yeah, seeing as they did eventually disappear without a trace, I don't feel super trustworthy of them, for sure.
@evan @deadsuperhero Will help however I can! One area of focus I’d assist would be helping with working group on feed account standardization we mentioned in the article….
@dermoth I've learned something new again, thanksBut I have no idea if they really make them biggerI think maybe a little, but is that really important?OK, I'm a woman, so I know men are totally different in that regard@monsieuricon
@PortaFed@julian Why wouldnt the whole export object be signed? If an object is missing, the merkle root wouldnt match and you wouldnt be able to do partial validation anyway. I could have missed something on the strategy there
Side note, I made one such workaround, in the form of a browser plugin. If you find yourself using the ol' "copy the link and put it in the search box on your home server" trick a lot, maybe check this out? https://stefanbohacek.com/project/mastodon-tools-browser-extension/#mastodon
