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)
Do you have any insight into why it's so much more memory-hungry than the docs indicate? Is that a problem on its own, or just normal and accepted behavior for Mbin?
I don’t know yet - it’s definitely not expected, so my guess is an unintentional bug in mbin somewhere. I am hoping to find a way run a profiler or something similar to see what it’s doing.
Thanks. It’s a strange problem that only happens when trying to post directly to a community/magazine that resides on another instance. So this works fine because this community it hosted locally. I think I understand when but hoping to get some clarification.
Are we still having trouble? A thread I posted 45 minutes ago hasn't shown up on the instance I posted it to yet. The "Open original URL" menu on the post goes to the Fedia page instead of LemmyWorld. It seems like a comment I posted 2 hours ago is also not appearing on the original instance, either.
Thank you for all your hard work. I am experiencing the same problem, and was just browsing Fedia Discussions to see if anyone else had reported it. Again, thanks!
While you're working on a more permanent fix, is there a preferred way we should let you know about hiccups like this? Or is pinging you in a thread in this magazine sufficient?
Note that even once I get this fixed, there will inevitably be another problem crop up. Posting here is fine, but an email to jerry@infosec.exchange or a ping to @jerry (my mastodon account) would probably be faster (note, when federation breaks here, messages to @jerry wouldn't get through from fedia.io...
@jerry How long should a message take to propagate? I made a few posts over the last couple of days and they seem to have propagated correctly, but I just made a post on a thread from mander.xyz about 30 minutes ago and it hasn't yet appeared on the host instance.
Edit: Never mind, I was just too impatient. They're there now.
I am not 100% sure. Fedia.io is running on a beast of a server, and so long as it’s working correctly, it should be able to deliver it instantly. But that doesn’t mean that the receiving servers are able to consume and render them that fast.
Not entirely. It looks like the rabbit issue was only impacting one of the queues (“deliver”), though I would have expected that to impact things like microblog too. All I can say with clarity is that the instance was operating in a very unhealthy state.
The queue appears like it’ll take several hours to flush, but it’s working.
fedia.io
Hot