The nice thing about Lemmy is that you can always host your own instance, even if it’s only for your own individual use. You can basically use your own instance as a proxy - other instances will not see how or from where you are connecting to your instance.
Large instances are being attacked almost constantly at this point in smaller and bigger ways. Almost all measures we implement to combat these attacks come with some trade-offs for the rest of the userbase.
It would be awesome to have a laid-back Europe community on lemm.ee, let me know if I can support you in any way with that!
What exactly is the issue with our admins? If you feel you’ve received some unjustified moderation, feel free to contact me and I can have a look.
0.19.2 was a simple upgrade, did not even require downtime, so I’m not surprised it wasn’t noticed :P
Based on the description, I am thinking this was related to some general issues we were having after the 0.19 upgrade (which have been solved now). Thanks for the info!
lemm.ee started having a weird bug for logging in
Hey, can you share some more about this login bug? I’m not aware of any login issues currently. Could it be related to an app you were using not supporting 0.19 yet?
I think the only answer here is that we need Japan to create “Hikaru no Lemmy”, where an ancient spirit of a dead Lemmy poster possesses a young boy called Hikaru, who proceeds to amaze the world with some top tier Lemmy posts 😛
Or more seriously, I’m a huge fan of this infographic and share it with people whenever I get asked about Lemmy: https://i.imgur.com/b2QuYAR.png
(and, last I checked, a substantial contributor to the lemmy source code too).
I think not a substantial contributor yet, but I hope to become one eventually 😃
The problem at hand is not about the usability (UI/UX, performance, etc.) of Discord but rather it’s private, closed source for-profit existence being used as a “support” channel for a free and open (source, platform, communication) environment.
I agree with you in principle, but on a pragmatic level, it’s very hard to disconnect UI/UX/performance from everything else. I think it’s OK to acknowledge that Discord has a weakness when it comes to not being OSS, but a strength when it comes to UX, and I also think it’s OK to take advantage of that strength for users that want to do so.
Just to be fully clear, I am never planning to make Discord the main communication channel for lemm.ee announcements, nor to make users feel like it’s in any way necessary for them to use Discord just for lemm.ee communications. I am also active on Matrix constantly, and read most of what happens in the Lemmy Matrix channels. Any user that wishes to reach me over Matrix can do so.
I think Discord is great, as long as you account for its shortcomings:
I love how snappy it is (I never have to wait minutes for messages to load, as I do in Matrix), and also how there are a ton of Lemmy users who have Discord open in the background anyway. While I wouldn’t ever propose moving something like the main Lemmy communication channels to Discord, I do think it’s much easier to have IMs with regular Lemmy users on Discord than it is to do so on Matrix (as in my experience, most regular users do not have a Matrix client installed).
By the way, lemm.ee also has a Discord server. It’s only treated as a secondary channel, all announcements are posted in our meta community on Lemmy itself, and just linked to from Discord, but it’s still nice to have IMO.
I think latency should be pretty decent thanks to our global CDN, but I think in the end you should just try it out and compare it to some other instances to get the best picture.
Our frontend is globally distributed (so if you’re in the US, you get it from a US server), but the backend server and user data are hosted in the EU.
According to my cake day, it was just over 1 month ago now
A bit more than that😅
As of Lemmy 0.18.1, cached copies on other instances do not disappear if the original instance has died.
In theory, it might even be possible to actually clone a cached copy into a new local community. This would require some database hacking, so not recommended unless you’re familiar with Lemmy code and SQL.
Hey, admin of lemm.ee here. I have no behind the scenes knowledge of what happened to vlemmy, but I have heard (in this thread and elsewhere) that some communities have been suddenly left without a home. I hope it’s OK for me to direct a message to such people here.
If you’re looking for a new home for your community, and don’t want to do it on lemmy.world for any reason, I would be happy to welcome you at lemm.ee! If you’re interested and want to know more about how lemm.ee is run, you can check out our administration and federation policy.
We recently upgraded our servers, so should be no problems in accepting some new users. In general, lemm.ee is not going anywhere - we have even already paid for some of our infrastructure up front for a year.
Let me know if you have any questions!
You don’t need a new a account for this, just make sure you have “Show NSFW” enabled in your profile.
Awesome, thank you for confirming!
Repeating the other comment just so you get a notification, sorry if you already saw it above:
I have purged my CDN, could I ask you to check if it’s still 404 with your original config?
Just to add some more context, there was an attacker recently who created accounts on several Lemmy instances and used those accounts to spread CSAM. On lemm.ee, this attacker created 4 accounts over a 24h period, but was not able to upload any CSAM to our servers due to our stricter upload rules (we require 4 week old accounts to upload any images at all), and all of the 4 accounts were removed very shortly after creation (most of them within an hour of signing up). The attacker gave up trying to use lemm.ee very quickly, and moved on to other instances.
I just wanted to share this context to illustrate that while indeed the different measures we implement to protect the instance can have a negative impact on legitimate users, I really believe that overall, they have a net positive effect. In addition to Cloudflare DDoS protection and image upload restrictions, we also have a separate content-based alerting layer on top of Lemmy, which allows our admins to quickly notice when something suspicious is going on. As another example, this alerting has allowed us to extremely efficiently deal with a current ongoing spam attack on the Fediverse, and I bet many lemm.ee users aren’t even aware of this attack due to the quick content removal. We will continue to improve our defenses, and hopefully try to limit the impact on real users as much as possible, but some trade-offs are necessary here in order to protect the overall userbase.