House was started in part to have a backup in case reddit bans Monero or otherwise goes to shit (looks like it will) but also from my horrible experience fighting ai-bot-comments that look just about human at first glance but add zero value.

Because of the latter, monero.house was only federating with very few other lemmy instances and puts a lot of emphasis on verifying that every single user is really human.

By now I have learned a lot more about how Lemmy works and cleared up the concerns I was having about ressource usage when federating (it is apparently close to zero) as well as concerns regarding moderation.

With that being said:

monero.house

now has open federation.

I’ll evalute how this affects our little Monero Lemmy instance over some time but for now it seems like a very positive change. Due to the increase in content brought from federation, there is now finally a reason to check house more than once per day 😅

For people who dont care about anything but Monero, the “local” tab should still be largely the same experience as before, with the only difference being that people from other instances can now comment on posts made here.

The sign-up process will also stay the same so you’ll always know you are most likely talking to a real person when they dont have another @-symbol+ domain behind their username.

Should this for some reason not work out, we can always silo the instance again but I’m optimistic about this change.

  • BasedDebianUsr@monero.house
    1·
    1 year ago

    @[email protected]

    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/[email protected] - user can’t be loaded https://monero.house/c/[email protected] - 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.