@freamon Agreed, it's a silver lining post, for sure.
But generally I find people say "you see, this is why the Fediverse/Lemmy/Mastodon etc will never take off" for every blip of bad news or whatever. But in reality, while the news sucks for .ml servers, it highlights the resiliency of the Fediverse - which is a win.
And better to happen in the early days of Lemmy than when/if it got much bigger.
You say that as though there's some kind of crystal ball we can all look into and see all of the obstacles that will need to be cleared and prepare accordingly. That's not how scaling web services works, especially distributed ones that are built on a relatively new protocol.
I mean, the .ml domain belongs to Mali and they have every right to take it back.
lemmy.ml was a sort of prototype made by the devs of the lemmy software. It wasn't really meant for widespread public adoption. So it makes sense that they went with a free domain.
Maybe. I read the idea about it standing for Marxist/Leninist, but there's thousands of TLDs now - if you can get .diamonds and .world, there's probably something that would evoke the same lefty idea (although maybe lemmy pre-dates the new domains, I don't know)
The parent domain was apparently well known to be a common host of phishing domains and scam sites. Free domains tend to attract those types, so that's a good reason from the start not to use that if you want your site to be reliably accessible and findable on search engines.
Yes. Hosting a service in a country other than where a TLD is designated for is bad practice and common knowledge for any web developer
Domains aren't sold, they are leased for a period of time. In this case the lease was for ten years and is lapsing now.
A domain takedown was never able to shut a server down, not even with centralized servers. Most big services are accessible via multiple domains of different countries, and this would just disable one of them. But for the Fediverse that means that they also "disabled" an entire instance with all its users.
This actually shows us that relying on domains can be a problem for the Fediverse! Imo we need to upgrade the federation protocol to be able to handle these things, like propagating a domain change or migrating accounts to other instances.
Because you need a way to be reachable over HTTPS for other instances to be able to securely send you updates (new posts/comments/votes etc.), so you need a trusted certificate. While HTTPS does not strictly require a domain name^1^ it vastly simplifies the process.
^1^: It's possible to get a trusted certificate for an IP address, but not nearly as easy as getting one for a domain. And it's probably also more expensive than just getting a domain and using Let's Encrypt to get a certificate.
Because you need a way to be reachable over HTTPS
Feels like this is the core key to be changed. Something like Debian's packaging system for example, which doesn't even need the Debian domain to be HTTPS.
Debian packages are signed individually, and usually people also don't see downloading Debian packages as potentially privacy-sensitive, so plain download is acceptable.
For lemmy where user accounts are involved, and in general as a new protocol designed in the age of HTTPS, it makes sense to require HTTPS.
They don't need it per se but there's a reason apt-transport-https is a very popular package.
We should require all servers to have opennic DNS and opennic TLS certificates installed
This is one of the problems with using country TLDs. They look cute, but when you buy it, you may not realize who controls it. Lemm.ee is similarly in a precarious position.
I really wish we could all agree to stop using country TLDs for this
Who owns or controls .world domains?
I think .ee and .ca are fine. lemmy.ca is for Canadians specifically
For .ca specifically: as long as you are a Canadian individual, or have a sufficient connection to Canada, or a Corp with a trademark registered in Canada then you are qualified to own that domain - but as to who is really checking I have no idea... CIRA complainants maybe?
Here's some info about .world domains https://support.google.com/...
@renwillis I'm not so sure this is a "win", since the Fediverse wasn't specifically targeted by any entity involved to begin with. If anything, it's just a straight-up loss to the communities that have to reassemble themselves under a new domain again, many of whom were probably mostly new users to the Fediverse to begin with, and are likely to be turned off by this experience. If anything, this just exposes that the Fediverse is significantly sustained by flimsy, free/cheap platforms that are vulnerable to disappearing without any notice. That doesn't exactly instill faith.
It's a really bad look, to be perfectly honest.
@renwillis The Fediverse is more than just the collective network. It's also the individual communities, some of which no longer exist right now. Those communities are now scrambling to figure out what to do.
Yes, the whole of the Fediverse is just fine. But the overall health of the Fediverse relies heavily on the health of individual communities.
I could also get hot by lightning there times a day but I don't optimize for it. This is a lol and definitely points back to how shitty personal servers may be. I for one hope a .org starts a monitizartion scheme, deals with the privacy issues this community blatantly ignores, and hires some professionals who actually know what they are doing.
If this is a loss, a loss compared to what? Centralised servers? If Lemmy was a centralised server, this would've taken the whole site down. As another commenter mentioned, if the US government decides take Reddit down, the whole service would be lost. But in the Fediverse no single government can stop it.
Another example is when lemmy.world was attacked. All other instances and the custom clients continued to work. If you say this is a bad look, what's a good look in your opinion? All of Lemmy going down at the same time? If centralised services deploy techniques to keep their services stable (horizontal scaling, regional mirrors etc.), Fediverse apps can use all of those techniques plus then some.
I do kinda agree, this isn't great for general adoption but it's a vital learning curve and hopefully smart people in the community will help develop ways to avoid it going forward and tools to fix it when it does happen
Lemmy as a whole not being hurt even if some domains are gone is the entire point of being decentralized. But yeah, it's really bad that communities made there will also be gone as it is now.
We need user and community migration like Mastodon has, and quick.
You can migrate to another instance with all your followers very easily in Mastodon.
I can see Lemmy comms being able to do the same and it's already been opened as an issue on the GitHub
Counterpoint: the generic communities being hosted on Lemmy.ml (an instance with a very strong political identity) simply because it was oldest was a real risk for the growth of Lemmy as a whole and this is a fantastic opportunity to rebuild those core communities on more generic Instances like Lemmy.world.
lmfao, frickin seriously? you're gonna build up an instance where the domain is part of all of your users' identities and you're not even gonna spend the $10/yr to keep that solid? with how much time goes into running a lemmy instance and not getting overrun by bots, that's an absolutely ridiculous assignment of resources
You have to remember that until recently, there was sub 100 daily users, this wasn't a big platform, and it wasn't just lemmy.ml, but a bunch of <10 user instances.
It wasn't worth paying for a small side project until it wasn't and at that point it was too late, plus who would have predicted that the gov of Mali would forcefully take back all of their domains?
Bruh it's 10 dollars PER YEAR.
I've owned a .com domain for over a decade, ever since BEFORE I actually had a job and was living on allowances, and it still doesn't register as an expense to me.
The content I host on that domain has been used by 3 different people tops, which is me and a couple of my friends. It's still worth it.
If I were to build a public-facing service I'd certainly fork over the bare minimum to guarantee that it fucking stays up even if I don't expect thousands of users. It's just a matter of doing things properly. Free domains have always been sketchy as fuck, every scam ever was hosted on a .tk domain at some point.
But as it has been stated multiple times already, the only reason they actually went with ".ml" is because they thought it would be funny for the marxist-leninist association. That's literally it. It's not about money. Anyone with access to a dev machine has 10 dollars a year to spend or they wouldn't be shitposting on the internet.
i mean, good point on the project size, but buying a domain is honestly such a basic thing that it still feels like a weird result on that equation to me. for fmhy.ml, specifically, i understand their choice, since pirate sites do tend to be quite nomadic with their domains, and the fediverse being so domain-specific is a new thing.
still, domains are hella cheap. the $10/yr figure i quoted is for a "serious" one on one of the major tlds, you can get away with much less if you're willing to go for a somewhat more niche but still reputable one. especially one that's longer than two characters.
Even worse, the free .ml domain is not actually yours when you get it for free, but actually owned by the company that previously managed the .ml domain. I suspect Mali government has reclaimed all those free domain registrations now that the contract with the company has been expired. The .ml domains that still up was probably paid domain and Mali government are probably still honoring the contract.
Niue is trying to wrangle control of .nu form Sweden, so I'm a little worried. It's been ongoing for years though.
I think a lot of them were tankies who thought it was cool to have ML in their domain name. They have lemmy.ml and lemmygrad.ml iirc. Honestly I don't know whether to be happy those communities took a hit or sad that I might lose one way of identifying and avoiding auth-left instances.
I might be unaware of some technical issues here but why not just get another domain, point it at the server, then update the database to change all references to lemmy.ml to thenewdomain.tld and then make an announcement on a couple of the bigger instances? Federation will take care of propagating the news far and wide. Then, as users hear the news they can just login using the same details and those of us subscribed to Communities on .ml can just update our subscriptions.
I mean, it's not a perfect solution but it'll work, surely?
ActivityPub uses URLs as IDs for everything. And there's no way to update those IDs, it's possible to update inbox URLs and other things but the main address of the object itself is its URL and thus there's no way to propagate it without essentially making a new one.
It's not impossible to do, but managing to get that to federate to all instances in a sane way is not currently possible.
There's a ridiculous amount of URLs in the database and even fixing all of those won't fully do the job, as post content might still refer to the old URL and whatnot.
It's a messy situation, you're not supposed to lose your domain.
the URL is the id in the database
Who was the idiot that decided to use for a database ID an identifier that almost entirely depends on external (and, for fediverse purposes, usually antagonistic) entities?
The W3C, apparently. It's both the ID and the URL of the object if you want to refresh it. They seem to suggest doing it that way because the URL of a user profile is going to be guaranteed to be unique, and can only be owned by the owner of the domain.
Lemmy assigns it its own internal ID per instance but it's only used internally for joins and stuff.
For example, your person ID is https://feddit.cl/u/nintendiator. If you curl it in ActivityPub format you'll get your user:
~ % curl -H "Accept: application/activity+json" https://feddit.cl/u/nintendiator
{
"@context": [.....]
"type": "Person",
"id": "https://feddit.cl/u/nintendiator",
"preferredUsername": "nintendiator",
"inbox": "https://feddit.cl/u/nintendiator/inbox",
"outbox": "https://feddit.cl/u/nintendiator/outbox",
......
}
They seem to suggest doing it that way because the URL of a user profile is going to be guaranteed to be unique, and can only be owned by the owner of the domain.
Immediate design issue right there: the URL of a user profile is not guaranteed to be unique, and while it can """only""" be owned by the owner of the domain, 1.- it's not owned by the user of the profile and 2.- the ownership by the domain owner is revocable by a third party.
Design-wise, it feels to me like they decided that land / house deeds could be certified by municipal traffic signage.
Who was the idiot
The W3C, also known as the people who develop the web standards. It's a reasonable expectation as you have to draw a line in the sand somewhere. Distributed identity is not a solved problem, so domains are the best solution we have right now.
What would you suggest they use as the identifier with which allows other entities uniquely identity you? There are no alternatives until you introduce a ton of cryptography, which is what DID hopes to address, but that's still going to be bad UX.
The W3C, also known as the people who develop the web standards
Figures. The same people who added DRM to the web standards.
Now, I don't know what other alternatives could have been used, but I know that URL was among the obvious ones to not use. Something that uniquely identifies you has to be non-transitive and non-revocable by a third party, of which URLs are neither (domain names are revocable, URLs don't have addressing persistence let alone when you add query strings into the mix, etc). Among the few things that I can think are non-transitive and non-thirdparty-revocable are the good ol' ssh-keygen keys, easy to generate and all that but I've never found a good mechanism or design to query about them.
That seems like an ActivityPub problem, not a problem with the admin who lost the domain. Perhaps somebody should fix dumbass design flaws to the protocol.
Federations won't survive with obvious flaws like that. It needs resilienacy.
You'll have to go complain directly to the W3C for that. The situation is Lemmy may fix it with some custom protocol extensions, but then it'll still break every other piece of software that follows the spec like Mastodon, Kbin and others.
It's like adding a 6xx status to HTTP. You technically can, but expect every standard compliant clients to be confused and bail on it.
You can't just change domains with emails either and have everything seemlessly migrate over. Not losing a domain is not a completely unreasonable assumption to make.
Thankfully the users and communities aren't lost, it's just that people outside of fmhy will have to resubscribe to the communities on the new domain.
The problem is with the federation. Other instances will try to federate with the old domain and won't recognize the new domain. Simply changing your domain will not update federation in other instances. AFAIK work is still underway to allow migrating to a new domain and allow other instance to recognize the domain change.
Time to create BGPML... a federation protocol router for .ml like situations. ;)
It's my understanding that this isn't possible. Migrating domains in Lemmy is not supported though it is possible with some very hacky solutions like you're describing. But the old domain needs to be retained indefinitely as a pointer to the new domain or it will break federation with other instances. If they lose control of the domain or can't keep it basically forever then federation will break. They can potentially migrate users and posts, but it is effectively like resetting and starting over as a new instance.
Right, but if Mali do reclaim all the .ml domains out there then there's little option? Yes, federation will break for .ml and yes it'll be like starting over on a fresh instance but only in terms of federation - all the users, communities, posts and comments will still exist, just under a new domain. Once the new domain starts federating people will catch on, especially if the news is posted on the larger instances.
Don't get me wrong, I'm not saying its not a problem, I'm just not sure its a total disaster either.
Ok so I guess the old registrar were a bunch of twats, so the gov kicked them out and in the process potentially benefits from the US mil email thing.
All while doing the typical government thing of messing things up for everybody because they don't know how anything works.
Am I right?
I don't think the email thing is connected to this. That just happened at roughly the same time.
@SeeJayEmm I hope so, that's a big miss on Lemmy right now.
Need to be able to migrate accounts & communities ASAP.
Oof best of luck to you guys on .ml instances, might be worth looking at buying a domain as a backup to migrate to. Don’t wanna be caught off guard like this especially if they are trying to recoup all their urls. I went with a .boo domain to be unique for my instance but there are loads of TLDs out there
FYI I made a little tool for migrating / backing up your Lemmy subscriptions, blocks, profile settings, etc.
Nothing to be done for fmhy now that it's gone, but for the future, it might help to have a backup.
Explain yourself.
I didn't realise you could do that, but then again I have no idea how country specific domains work
Depends on the country. Some are imho better run than com/net/org.
Disclosure: my company is a country registrar.
yeah and some countries with popular tld's (.fm,.tv) like the revenue they generate and have no interest in disturbing that situation. That said, there's always a risk, especially since things can change, governments change etc.
Yes, governence is key. That should ideally have it's users as stakeholders and be for public benefit and not for profit. Oh and be efficient. There's no technical reason why domains should cost more than $5.
There has to be a government connection since the DNS infrastructure in a developed country has to protected against bad actors will necessarily be linked, but not controlled, by national cybersecurity.
Oh and it should be a politically stable country. Problematical for the US?
You can only federate via tor or i2p if both sides support those protocols, because for federation to work between two nodes both nodes need to be able to initiate connections to the other. That means one-way bridges like tor exit nodes are not sufficient.
I'd guess most Fediverse servers don't support either of those protocols, so any new server trying to federate solely through them would have an extremely limited view of the Fediverse.
Though I suppose theoretically nothing is really preventing a motivated group of server admins from setting up a parallel "dark Fediverse" containing only onion sites.
Good explanation, thanks. I figured it would have been the interface between in the onion and outside of it. That's too bad. It's been forever since I used tor but... would someone be able to set up an exit node specifically as a federation point with the outside world? Sort of working as a reverse proxy for a site or sites on the inside?
Cryptography solved this a long time ago. No need for NFTs or anything "crypto".
How can you solve Zooko's Trilemma without "anything crypto"?
".onion addresses and bitcoin addresses are secure and decentralized but not human-meaningful;"
All "crypto as in blockchains" requires trust and buy-in to that blockchain, and someone to put it on the blockchain. It being internally secure/trustworthy does not intrinsically mean it's globally secure/trustworthy.
Cryptography is not limited to blockchains.
Sure, for the general case. In practice, we can look at Ethereum's blockchain which has all the "buy-in" and "trust" enough to the point that it's used to hold billions worth of value and is secured by the its validator network.
@renwillis @fediverse
Yes, and another lesson: TLD have meanings...
You want another beer?
thanks for using Leebra!
go to feed...
That's a very positive spin on quite a shitty situation (especially if lemmy.ml goes kaputt)
save