- cross-posted to:
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- cross-posted to:
- [email protected]
- [email protected]
- [email protected]
- [email protected]
An update:
- fmhy.ml is gone, due to the ongoing fiasco with mali government taking all their .ml domains back
- As such, lemmy.fmhy.ml is also gone, we are currently exploring ways to refederate (or somehow restart federation entirely) without breaking anything substantial
- We have backups, so don’t worry about data loss (you can view them on other instances anyway)
Currently, we have fmhy.net and are exploring options to somehow migrate, thank you for your patience.
You must log in or register to comment.
Man this is all so interesting to see so many unique situations testing the Fediverse to see how it holds up.
let’s hope they’re interesting because it’s novel and the problems were there with other solutions just solved ages ago rather than the alternative: “so many unique situations” because there are a litany of “oops didn’t think of that” moments that will continue to crop up
IMO the real takeaway is that a big instance disappeared overnight and yet here we all are on the fediverse talking about it.
WIll this also affect all other .ml domains? Or is this some anti-piracy thing? (I don’t know fmhy, but from the name I guess it’s about piracy.)
It seems to be Mali just wanting their domains back, in which case it’s uncertain times for all .ml domains.
rip lemmy.ml
Good thing join-lemmy is safely tucked away in a .org domain.
This is extremely bad timing for Lemmy (if it ends up happening), but also a good example of how federation makes the entire social media landscape more robust. Had this happened to a centralized service it would be devastating.
Not really. Most centralized services are accessible via multiple domains, e.g. for different countries. This would just disable one of them, but users could still use another to log into their accounts. For the Fediverse it “disables” an entire instance, locks out users and cuts it off from federation.
Lets not put a positive spin on a situation that exposes a weakness of the current system. The federation protocol needs to be able to handle these things gracefully, like propagating domain changes and migrating accounts between instances!
I’m now wondering what happens if the Mali government (or someone else) begins using those domains with their own lemmy instance, potentially with malicious content.
Would the instances they’ve federated with begin ingesting and serving that content automatically? Or would that be blocked due to key mismatch?
I think they need the private key for the https certificate to do that
Afaik it is all connected to the domain name, so they could definitely start to impersonate any .ml instance. Other instances could detect that the signing key for federation messages changed, but that’s about it. Their admins would probably have to block/defederate them manually.
If it was always going to happen, now isn’t really a bad time. Sure, a month ago would have been better, but people still haven’t been here that long. If I wind up needing to migrate, and lose my current account, oh well. No big loss. I imagine others feel similar.
I was frustrated with the outage yesterday and created a new account on a different instance so I could still browse. Couple hours later I had all my subscriptions filled out and the experience is almost identical to my first account.
lemmy.ml is still up as of right now. Possibly they contracted a subscription to the domain name to keep it up. They had to do something to retain it otherwise the site would be unreachable. If lemmy.ml does have to change names it will be a hassle since I’ve got a good number of community subscriptions there.
This wouldn’t happen to an instance with a regularly subscribed domain name. Problem is the .ml domains were free and the associated country decided to claim them back. The risk of using a free top level domain is something that should have been considered. I don’t think it’s worth the risk versus the cost savings considering how difficult it is to migrate a Lemmy instance.
It’s just the domain, though. That’s not a big deal to change.
The instance is known by its domain name in the federation network. If that domain name changes, it’s like starting a new instance from scratch.
Sounds like a complicated project to migrate communities and posts and users to a new instance without breaking something.
Federation connections are by domain name, so … it is a big deal
Right. This will basically make nearly every /c live in .world as all of the .ml /c’s go defunct. That, or Beehaw, which is walled off from everyone else.
(Side note… my work’s firewalls block everything *.ml – and that’s the only thing that saved me from creating my account there)
From that point of view, yes. That’d mess things up, you’re right. But from my understanding, they won’t lose any data, accounts will remain, as well as subscriptions that lemmy.ml users have. Or am I wrong?
The problem is, if they don’t have access to their original
.mldomain, their accounts are still tied to it. That means if they try to interact, such as subscribing to a community, when the data for that action tries to be sent back (such as updates) it’ll go to the.mldomain, which they wouldn’t receive.Lemmy doesn’t have a built in way to just change the domain name, or really any of the ActivityPub services AFAIK. You’d have to either really do some hacky stuff to get around it (which could result in unknown issues down the line) or reset everything.
Oh, it’s more complex than I expected. Thanks for explaining. I was wrong.
Most of the hacky ways around it involve retaining ownership of the old domain and leaving it up indefinitely as a pointer to the new location. If your domain is taken from you though there is not much you can do.
Seriously dumb to have used this TLD considering there are a ton of choices these days.
Currently, activitypub identity is tied to domain name. Mastodon support migration as long as the old domain is still up during the migration process, but AFAIK Lemmy doesn’t even have a process to migrate an instance to a new domain yet.
Someone should tell Lemmy devs and send them a crate of coffee because it’ll be a race to implement domain migration before all .ml domains got shut down.
Think about all the links to lemmy.ml
Shall I make an account in another instance?
Never hurts. Could be a good opportunity to look around the threadiverse and see if you find anything interesting.
However, as it only affects the domain, I expect the Lemmy developers will manage to migrate user data to the new domain should lemmy.ml go down. So your account won’t just disappear, but it might go down for a while. It might also affect communities hosted on .ml domains, as followers from other instances will not have the correct path any more.
Yeah, they are actively working on functionality to migrate user accounts and other data between instances, so that they can use that functionality to migrate everything on an instance to another instance.
Since migrating data affects all the replicated data on other instances as well, I guess when they migrate lemmy.ml somewhere else, all of Lemmy will be down for a day or two, being just overloaded with all the migration stuff.
Thanks for the info.
Nope. Domains don’t store data. They can change domain and keep all the data.
Unfortunately, no.
Currently, activitypub identity is tied to domain name. While mastodon support migration as long as the old domain is still up during the migration process, AFAIK Lemmy doesn’t even have a process to migrate an instance to a new domain yet.
So basically, if you switch your instance domain, you’ll mess up all your federation network, unless Lemmy devs implement a solution soon.
Calckey.social will be transferring all data to new firefish.social, first in the Fediverse.
I understand it as the Mali government is taking back all the domains after a subletting contract ran out. A lot of sensitive emails that should go to .mil (US military) has been typo-sent to .ml-addresses instead. Here’s some more reading.
(I am very tired here and might have misunderstood everything, please correct me if I am wrong)
Perhaps the military should have a system in place to not allow emails to be sent outside of very specific TLDs if it’s that sensitive? And perhaps have an automated contact book, instead of relying on someone typing out the to: address manually to be able to make that mistake in the first place?
Seems like some very basic security measures for something so serious.
This says that they block outgoing mail to .ml domains from its network.
https://domainincite.com/28897-freenom-is-losing-another-cctld-after-collecting-military-emails
Edit: wrong link
For most situations, there is a global address list that members can use. There are instances where emails need to be sent outside of the .mil domain though, such as to other government agencies that use a .gov, or to contractors on commercial domains, as well as to partner nations that will be on their own countries’ domains.
Internally they do block that but the problem are people outside the network sending something to a .mil address and mistyping.
Yeah that’s super easy to integrate. I used to work in cyber security for a bank and even I was only allowed to send to internal domains initially. I had to file for exceptions for contractors and vendors and stuff.
Lemmy has had such a crazy month and a half. Insane growth, XSS injections, DDOS attacks, admin takeover, domain name seizures. What a wild ride
My boy Lemmy is growing up!
and still better than using official Reddit app (and still better than Reddit overall) lol
And we’re still here, going strong. Long live the Fediverse.
Welcome to the real world
That’s how every service starts. Let’s keep going
Facts. And such drama does make Lemmy more appealing in a way
Posting here for visibility as I guess most people on Lemmy are not on Firefish/Mastodon
glad to see them not go down the vlemmy path
What happened to vlemmy?
Nobody really knows for sure. It just sort of disappeared one day with no warning.
Is this going to be an unsolved mystery of the Internet? A spooky Fediverse legend?
Yes, that’s reassuring. Also, nice to see their main website, I never actually noticed it existed
Damn, lemmy.zip, eh? If that instance is public, I don’t see that being a good thing.
Tons of businesses, people, etc, are all banning .zip and .mov TLDs for security purposes. I’ve personally banned all those domains from my network as well.
Bold move.
What’s the issue with those TLDs?
See https://youtu.be/GCVJsz7EODA and https://youtu.be/V82lHNsSPww
There are a few problems, but I believe the biggest issue is that .zip and .mov are valid and common file extensions, and it’s common for people to write something like ‘example dot zip’ or ‘attachment dot mov’ in emails, tweets, etc. Things like email clients have features where they automatically convert text that looks like a web address into clickable links. So now, retroactively, all those emails etc suddenly have a link, where they used to just have text, and the domains that are equivalent to those previously benign file names are being purchased by nefarious actors to exploit people unaware of the issue.
Here is an alternative Piped link(s): https://piped.video/GCVJsz7EODA
https://piped.video/V82lHNsSPww
Piped is a privacy-respecting open-source alternative frontend to YouTube.
I’m open-source, check me out at GitHub.
Yeah, you have a point. I may go block those TLDs tonight.
But there’s only an issue if the software you’re using auto linkifies the domain. They often don’t and won’t. This seems like a hypothetical problem that probably doesn’t exist for most major software. I certainly know no email software is gonna auto linkify this.
If you’re curious, you can see if whatever software you’re viewing this post in auto linkifies (neither are for me): hshshssu.zip iwuf8aowk.mov
(And if we’re manually linkifying, then you don’t need to use the new TLD. Eg, not-a-virus.zip.)
At 1:30 in that second video, he shows that YouTube already converts dot zip domains, even in old comments that predate the domain’s existence. At 3:19, he shows/mentions Twitter, Reddit, Facebook, and LinkedIn. I would consider those major platforms. And keep in mind, it only takes one person downloading one file to cause major damage - the LMG hack was due to someone downloading and trying to open a fake PDF that was sent via email: https://youtu.be/yGXaAWbzl5A.
So yes, not everything does or will auto convert the links, but I think you are underestimating the potential for issues here.
Actually really huge security threats. It’s a very good idea to block them. I especially did because my girlfriend works for the government and does some secret stuff that can’t really get out, and she deals with a ton of real .zip files. I think everyone regardless of who they are should make sure to block them.
i don’t doubt there have been a lot of cases of those tlds used for scams but i haven’t been negatively effected by this instances domain name.
feel free to read the discussion about it here though
I can’t open that link because I block .zip domains lol
First I join Vlemmy.net and then FMHY.ML… I am afraid whatever instance I join next will collapse 😭
I’m sorry but for the good of all instances I’m afraid you will need to become a lurker 😔
Are you me? Same instances, same order…
…same fear.
.ee is owned by Estonia. Just pray Estonia wouldn’t do the same shenanigan and cause your instance to go down.
tbf Estonia is a stable EU country and Sunaurus (the admin of lemm.ee) is from Estonia so it’s not that strange
I also joined vlemmy.net and it came down between fmhy.ml and sh.itjust.works. Guess I got lucky!
what happened with vlemmy?
The instance up and disappeared right after it’s admin said they were going g to defederate with another instance. There was no warning it was just gone the next day.
There is lots of speculation around it, but I think the admin got scared of the implication that their servers still held content from the other instance that was illegal in their country.
oh thanks.
Frick, my website uses .ml and it’s gone.
Are you using the free domain deal, or are you paying for your .ml domain? I suspect they only revoking those unpaid .ml domains.
Freebie. I actually bought a new domain this time.
You might still buy your old .ml domain once Mali government open up registration again, assuming domain squatters doesn’t grab it first.
I only used that domain because it’s free. Now I’m buying an actual domain, I’m not going back to that one.
Crap, sorry to hear that
Lost mine too, had an .ml domain for testing servers. Was baffled why the DNS won’t resolve, then I see this.
They are probably paying for the domain
have fmhy not paying for theirs?
No, that is the crux of the matter. They used freedom, which offered .ml for free.
I’d like to think FMHY was true to their name and didn’t pay for the domain.
No idea… Sorry
I posted this on another thread about this, but I’ll repost it here:
I have made a tool that can backup / copy your account settings, subscriptions, and blocks to a new account: https://github.com/CMahaff/lasim
There are others out there as well if you look.
Obviously the loss of .ml communities would still be catastrophic to Lemmy, but at least your new account won’t start from ground-zero, and you can be less effected by downtime by having 2 accounts with the same subscriptions.
Fantastic tool; thank you. I’ve been keeping 2 accounts—just in case—and this simplifies it significantly.
Super useful, thanks! 👍
What about lemmy.ml? Can govt just take their domain?
I think in theory yes, since the .ml tld is now managed by the Mali government instead of some guy that had an agreement with them.
Re-federation is probably possible. BUT! You’re going to always have problems with older content. Case in point my federation error messages is at 2300. About half are failed requests on fmhy.ml.
So for re-federation what’s needed:
1: Remote instances should unsubscribe all users from any fmhy groups. They’re dead now. They can only announce that and hope they do. I reckon when their errors start ramping up (as I saw yesterday) they will be looking into why. Probably to help de-federate from the old URL
2: The fmhy instance should unsubscribe all users from all remote groups but keep a note of the groups while identifying as fmhy.ml. Then once on a configuration for the new domain re-subscribe to each one. The first step should hopefully stop them trying (and failing) to federate new events to the old URL. The second step should trigger federation with the new one.
3: They could be able to keep the DB. But I am not sure in what places the old domain might be stored in the DB and what would need fixing there. Also not sure if they’d need to regenerate keys. Not sure if they’ll see the key was attached to the old domain and refuse to talk to the instance.Now what’s going to be a problem? Well ALL the existing content out there has references to users on the old domain. It’s VERY hard to fix that. Like every instance would need to fix their database. Not worth it. But, whenever someone likes/unlikes or comments or whatever a post made from fmhy.ml then there’s a good chance a remote instance will queue up a retrieval of:
1: User info about the poster/commentor/liker
2: Missing comments/posts for a like/comment eventAnd those will fail and error log. I don’t think there’s a way around that aside from editing the whole database on every instance. Again, IMO not worth it.
Would be a nice federation feature if, provided you could identify with the correct private key, announce a domain change which would automatically trigger the above in federated instances, or at the very least some kind of internal redirect for outgoing messages.
If I’m running lemmy.world, I wouldn’t unsubscribe my people. I’d wait for that instance to move to a new domain and just find/replace in the database.
Not every instance needs to migrate fmhy. Some can just leave that stuff broken. If the biggest half dozen instances migrate manually, fmhy would be able to keep most of their subscribers.
I do wonder how often instances will keep looking for fmhy without intervention. Seems like tooling to migrate or discontinue an instance wouldn’t be too difficult to build. At least it wouldn’t if they didn’t have a million other things on their plate.
We could use a few less third party clients and more work on Lemmy itself. Unless you’re going to bring over your userbase like RiF and Apollo can.
Yes, although you might need to fudge keys if they’re properly enforced. Looking at kbin I can see requests are at least signed with the private key. Not sure if the public key is stored somewhere in database, or is pulled from the instance using DNS as a security guarantor (I guess) every time.
I don’t have any subscriptions to them, but I have those 1000+ errors just from posts their users were involved in.
Afaik mastodon has a way for instances to migrate to a new domain, but the old domain must be up during the migration process. Lemmy on the other hand don’t even have any domain migration procedure yet. People will probably go nuts about this on their GitHub issues portal.
Possibly. I think mastadon has been around a bit longer though? Not sure why the old domain must be up. Unless they don’t store public keys of known instances and they rely on DNS for the security.
e.g. Instance A signs a request, Instance B queries Instance A via DNS lookup (as is normal) and checks public key confirms signature and allows it.
I got curious so I start digging into how mastodon do it. It’s more like a hack, really. Mastodon uses WebFinger to resolve user account, so when you change domain, you can leave the old domain up so your federated servers can still resolve your users and realized the domain has been changed and update their federation data. But it turns out you can’t exactly retire the old domain either because it’s still tied to user account internally. So if you lose control of your old domain, you’re probably as screwed as fmhy.ml.
Yeah, which is why I think storing remote user and instance public keys might be better. Then that can be used to authenticate the migration request (it’d probably need to be an extension to the activitypub standard).
The biggest problem I see is that an instance doesn’t know about all the instances that have data pointing to them. So how does it communicate the changes to everyone? The mastadon way is probably the sensible way to do it, despite not supporting the loss of control of domain scenario.
Is Mali gov just removing all DNS records without warning?
No respect for existing contracts, or at least some heads up a couple of months earlier.Governments just love doing stuff whenever they can, because what are you gonna do? This is a country under a military junta, there is no legal process to get back the domain.
They just handed off the management of .ml domains to a third party on a ten-year contract, and the contract is now ending.
So I guess Mali is honouring its contracts, and I doubt the third party provided anyone with contracts going beyond the ten year period they could guarantee for. I doubt the third party provided contracts at all to be honest.
Freenom (the third party in question) has been pretty shady for years. I got burned with their free .tk names a few times back in the day.
FYI discussion on lemmy.ml about it
Makes me wonder what’s going to happen to lemmy.ml if the Mali government is taking back their domains.
All of my posts on other instances are gone now :/
