That’s fine too, the short of it is it’s entirely up to you.
Admin @ lemdit.com - Roam free!
That’s fine too, the short of it is it’s entirely up to you.
There are no requirements, and they wouldn’t be enforceable even if somebody tried. The admin of instance1 has no way of knowing that you already have an account on instance2. Your identifiable details (IP address, e-mail address) are private to the instance that you sign up with and it would be a violation of privacy (and inherently scummy) for those to be shared between instances - they’re not.
You can be anonymous on the fediverse, just like the Internet in general used to be before Facebook.
That’s entirely up to you, it can be the same username if you want. Speaking as an instance admin, there is no problem with users creating multiple accounts across instances, even if they’re the same username.
Spam would be creating as many usernames as you can on any given instance (e.g. trying to register 100 users on lemmy.world because reasons) - there’s obviously a problem with that. Creating you@instance1, you@instance2 and you@instanceN is perfectly fine.
Not at all, it’s perfectly fine to have accounts on multiple instances.
I’ve tried refreshing lemmy.world and Cloudflare blocked me:
I’m officially a bot now I guess.
Edit: But more on the topic, they have been plagued by DDoS attacks recently so my guess is it’s more of the same.
Edit edit:
It’s probably related to the redirect.
I think they’re stuck in a vicious circle, their server costs scale with size but new users are way more likely to donate. Users that have already donated feel like they’ve done their bit for a while, and that’s if they’re still around and engaged in a few weeks. Very few people want to donate monthly, subscription style.
My personal controversial view is people should put more faith in well-run self-hosted instances. It’s a much more sustainable way to run a Fediverse server and self-hosted doesn’t have to mean amateur hour. Just because an instance is cloud hosted doesn’t mean it’s well configured or secure either.
I have way more resources at my disposal than the vast majority of cloud hosted instances, for a tiny fraction of the cost. lemm.ee for example is very well run but has to put up with a 100kb image size limit because of cost-driven space constrains.
Self hosting is also closer to the spirit of what decentralization is supposed to mean - your server ultimately belongs to your host.
It took about the same for me.
The DB migration at the end of this upgrade is significant, I was surprised how long it took when I upgraded my instance. Lots of room for things to go wrong considering the size of their DB.
In practice UPC will probably have some kind of fair use policy buried in its terms of service - your best bet is to go through those terms and see what you find. Fair use typically means they will start throttling you beyond a certain point. Most ISPs keep this reasonably vague (e.g. if your usage is in excess of what they deem to be reasonable, but no actual data amounts defined).
Not all ISPs have a fair use policy though, and typically you’re better off on large ISPs where your usage doesn’t really stand out that much.
It’s not a mass exodus. There was a sizeable influx of people from Reddit to Lemmy/kbin, sure, but that’s measured in the (low) hundreds of thousands. Reddit has hundreds of millions of active users.
The reality is it’s not even close to a mass exodus, not yet.
lemmy.world was briefly back to normal and there had been a post saying that everything was fine now - it’s not.
The site has just started doing the same thing again.
Please do not try using lemmy.world for the time being.
Yes, it just means that there are 9 people from vlemmy that have subbed to that community. This bit is a bit confusing, for example if nobody had subbed to it yet from vlemmy then it would show 0 subs.
Hey, you should be able to search for it, this may help you: https://lemdit.com/post/18035
I am able to find it from vlemmy:
Note that it won’t show up in the search results if you are not logged in.
This is a Lemmy-ui bug, not related to CDN/cache.
I had submitted a bug report for it some time ago but it’s not that urgent in the great scheme of things so they didn’t get around to it yet: https://github.com/LemmyNet/lemmy-ui/issues/1865
(the report speaks about this happening after you log in, but it’s the same thing).