From my understanding this site was originally a phising site, was reused for Lemmy, but many dns providers and what not haven’t removed the domain from their blacklist. This is seeming to break open federation e.g
If we can’t reliably interact with other instances and them to us, it kind’ve defeats the point of having an open fediverse we can all use. I think there’s 3 ways to fix this: You could get every Lemmy instance to change their dns/isp (unfeasible). Or you could continue to get providers to change their blacklist. I’m guessing you already tried that though (maybe they think your still the guy with the phishing site). Then the less pleasant option would be to actually change the domain. Unfortunately the instance would have to start afresh since you can’t use the same domain. But I think that would be the best way to go about this. Say this instance booms in users (which it’s bound to relatively soon with the exodus) and the dns situation stays relatively the same. What then? Making the decision to change the domain would hurt even more people than it would to now. Not sure how accurate this instance list is, but says we’re averaging 20 users a month.
Or as you said in the post, we could revert the change and disable federation here if things didn’t work out. But to me this doesn’t seem like the reason to make that change.
Also, remember I’ve never managed any sites before, this is just my take.
@admin@monero.house
From my understanding this site was originally a phising site, was reused for Lemmy, but many dns providers and what not haven’t removed the domain from their blacklist. This is seeming to break open federation e.g
https://monero.house/u/SeaStar@lemmy.world - user can’t be loaded https://monero.house/c/ich_iel@feddit.de - community can’t be loaded
If we can’t reliably interact with other instances and them to us, it kind’ve defeats the point of having an open fediverse we can all use. I think there’s 3 ways to fix this: You could get every Lemmy instance to change their dns/isp (unfeasible). Or you could continue to get providers to change their blacklist. I’m guessing you already tried that though (maybe they think your still the guy with the phishing site). Then the less pleasant option would be to actually change the domain. Unfortunately the instance would have to start afresh since you can’t use the same domain. But I think that would be the best way to go about this. Say this instance booms in users (which it’s bound to relatively soon with the exodus) and the dns situation stays relatively the same. What then? Making the decision to change the domain would hurt even more people than it would to now. Not sure how accurate this instance list is, but says we’re averaging 20 users a month.
Or as you said in the post, we could revert the change and disable federation here if things didn’t work out. But to me this doesn’t seem like the reason to make that change.
Also, remember I’ve never managed any sites before, this is just my take.