@MasTorDon forcing https redirects on onions with invalid certs is bad UX. even if onions technically are trustworthy without any further authentication, it's bad to tell users to click through cert warnings
@MasTorDon also your instance's name violates tor project's trademark guidelines: https://2019.www.torproject.org/docs/trademark-faq.html.en
@MasTorDon (sorry for the number of replies)
i just went onto the v3 onion; the website links still direct to the v2 onion. i think this is something you should bring up in the mastodon bug tracker, because absolute links inside a website isnt really good practice. pleroma suffers a similar issue with the media proxy, and i believe the devs are trying to find a way to address it (if they havent already)
i just went onto the v3 onion; the website links still direct to the v2 onion. i think this is something you should bring up in the mastodon bug tracker, because absolute links inside a website isnt really good practice. pleroma suffers a similar issue with the media proxy, and i believe the devs are trying to find a way to address it (if they havent already)
@MasTorDon imo if you wanna use v3, use v3, because your instance will ALWAYS federate over v2 onion because it's the canonical name of your instance. so consider that too
@opal I don't think it's a bug as I've read images are always served from the main domain
@jonah i did not see the second one good find. Maybe next week I'll fork it but I'll be busy for two weeks after next week so i didn't wanna start it yet but it shouldn't take that long with that out of the way.
that isnt true, see the dozens of hidden service seizures for proof. tor simply makes it more difficult, but by itself it isnt a bulletproof solution