Apologies - I've been having all manner of problems with mbin processing inbound federation messages. I don't have a fix, or even know what the problem is yet, but trying to keep it working.
Thanks Jerry, just wanted to report it since it seems a little different than the usual federation problems. The server does have the messages, they just don't show up in the view.
So far, we are the only ones having the problem. It is almost certainly because we have many more accounts/activity than others. The current problem may be a rabbitmq bug
Okay, I had to actually go to the instance as the modlog here did not show anything, but apparently my post was removed... But only on their side? It did not show "removed by moderator" on my end:
reason: Threativore automatic post removal: image spam
Not sure how that works or why. I used an external imgur album link, an additional imgur image link in the body, along with some various thread & modlog links.
At least I now also see the pure extend of the mod abuse and terrorist simping on Lemmy as I filtered through my account.
The modlog function in lemmy/mbin can be a bit confusing. I don't think the moderation actions of one instance propagate to the modlog of another instance. I think that is only really problematic in cases where the moderation action was taken on the home instance of a magazine/community.
I've seen issues with that too, where it does not show a lot of moderator actions on mbin but on the actual community modlog of the Lemmy instance. In this case it seems to be some sort of instance wide automod / spam protection though, but I don't know what exactly triggered it.
Sorry, I'm not sure - I've had a stack of work to do so haven't been using Fedia much in the past month or so :( This is the first image post I've made since your recent fixes!
It's real in the sense that the established policy is to retire ccTLDs within five years of a country code ceasing to exist. But there are multiple provisos there:
we don't know with any certainty that the IO country code will be disestablished; it doesn't necessarily follow that Mauritius regaining control of the British Indian Ocean Territory will mean the end of the IO country code (and associated .io ccTLD), for a variety of historical and administrative reasons
we don't know with any certainty that IANA will unequivocally shut down the domain, vs. converting it to a generic top level domain like many other existing special-interest and novelty gTLDs (e.g. .cloud, .gay, .info, .tech)
Obviously it's worth keeping an eye on what IANA does with this situation, but personally I suspect one or the other of the above will happen. It's probably in the interests of Mauritius to retain the domain as a source of income, but if they don't then somebody else will likely want to take ownership, and there's plenty of moneyed interests in retaining .io since a number of large business customers (the largest likely being Alphabet/Google) are already using it.
le sigh...
Afaik jerry has a fedia.social TLD that leads to an iceshrimp instance which potentially could be a replacement if .io is indeed endangered.
In the worst case scenario, fedia.io will be around for at least 5 more years (that is apparently the standard subset timeline). I have many more domain names if the worst comes, but there is a lot of expectation that the .io may somehow be saved due to the incredible amount of infrastructure built around it (GitHub.io, dockerhub.io, and of course fedia.io among many others)
fedia.io
Newest