Skip Navigation

Meta (

  • 2024-07-18 downtime

    Hey folks!

    Unfortunately, roughly 2 hours ago, went offline. The cause was our load balancer: it suddenly decided that all of our servers had become unhealthy, despite all health checks responding successfully when I requested them directly. In such cases, the load balancer stops serving all requests, effectively meaning that is unreachable for all users. I am still not sure what exactly caused the issue, but I will try to investigate more over the weekend.

    For now, we have partially recovered, and I am continuing to work on remaining issues. Hopefully we will be back to 100% very soon. Sorry for the inconvenience!

  • Hey what’s the little eye icon doodad at the top of the feed?

    It toggles between an open eye icon and and crossed out eye. What’s it do?

    Edit: turns out it hides hidden posts.

  • slowness

    Is anyone else experiencing slow refreshes and even slow up/down-votes on this instance? It does not seem to be constant, but I've noticed this for the past couple of days.

  • Trying to use PayPal to do a Ko-fi donation...

    After being helped several times with my various community issues by our kind site-runner, I would like to make a useful donation at this time. Oy, but there seems to be a problem:

    Now, I use an add-on in Chrome called "uMatrix," which is a script-blocker. This add-on forces me to hand-enable whatever necessary java-scripts there might be on sites, but it's not perfect. Okay, fine, so in Ko-fi's case, I wound up having to turn the tool completely OFF in order to get to the final payment-step, for anyone reading who had issues with such.

    Now, to the final step: My donation / pay options are evidently these: iDEAL, Bancontact, Przelewy24 and EPS.

    New problem: I have utterly no idea what those are. Is there a way then to donate via PayPal, perhaps?

    EDIT: Sorry, I guess this should have gone in "Support." Please do move as necessary.

  • hexbear visible again?

    Hexbear disappeared for a while. I guess they're federating with us again? What changed to make them want to do that again?

  • Is there ever going to be a way to post images from this instance?

    I always get the “file size too large” or whatever the error is when trying to post images as comments. I’ve asked and was told that it’s’s limitation on posts/comments.

  • Why defederation is extremely rare on

    Hey folks!

    For anybody stumbling on this post from outside I am the head admin of, a general purpose Lemmy instance, which recently turned 1 year old. I am writing this post to elaborate on how we approach defederation on

    Anybody who has been on Lemmy for a while has most likely seen several public defederation drama posts (most recently regarding, but there have been many many others previously). As an admin, I have probably seen far more than what is visible publicly, as I regularly receive private messages on the topic, ranging from polite questions about federation, to outright demands that I immediately defederate, and even to threats and personal attacks over the fact that I have not defederated some particular instance. It is definitely a topic that will keep coming up for as long as Lemmy exists, which is why I feel it would be useful to condense my current thoughts about it in a single place.

    Note that while I strongly believe everything this post contains, it is definitely a subjective topic, and there is no single right answer here. Other instances have completely different approaches to federation compared to, and that’s of course totally fine. The beauty of Lemmy is that everybody can choose their home instance, and in fact, everybody is free to spin up their own instance and run it however they feel is best. For an absurd example, if you want to create an instance which defederates any instance with an “L” in their name, then nobody can stop you!

    Quick intro to the federation policy

    Very shortly after creating, I wrote down a federation policy, which basically boils down to “we treat defederation as an absolute last resort, and we do not use it as a generic way to curate content for users”. This policy can always be found in the sidebar of the front page.

    In practice, this has meant that we have had extremely few defederations, and that we mostly solve problems with other means. I am very happy with the results, as it means that has become a great entry point into the Lemmy network, with very few artifical limitations on who our users are allowed to interact with.

    The benefits of federation

    I hope that this part of the post is very uncontroversial, but I firmly believe that federation is the absolute strongest feature of Lemmy. While we all know that the concept of federation can cause confusion for new users, this is usually overcome extremely quickly (for example, using the common e-mail providers analogy to explain Lemmy instances). To me, it’s completely clear that the benefits of federation far outweigh the downsides.

    For example, by splitting the Lemmy network between thousands of independent nodes, we ensure that:

    1. Any single entity is not a single point of failure for the whole network. Even if the biggest instance goes down tomorrow, their content will still be accessible through all the other federated instances.
    2. The maximum impact of admins is limited to their own instance. As a admin, I can ban a remote user from posting on, but I can’t completely ban them from the entire network.
    3. Private user data (such as ip addresses, e-mails, etc) are never shared between instances. No single malicious instance can harvest user data for the entire network, and extremely privacy sensitive users can always spin up their own instance if they don’t want to put their trust in any existing admins.

    One thing which is probably important to note here is that I tend to view Lemmy instances as infrastructure, rather than as communities. I know that there are alternative approaches, as quite a few large instances are in fact run as mega-communities, but that’s not the approach I take with, because I feel like such an approach encourages centralization and negates some of the benefits of federation (if all communities related to one topic condense on a single instance, then that instance does effectively become a single point of failure for a large number of users).

    In general, I feel like it should be a goal to encourage and cultivate decentralizing the network through federation as much as is practical, in order to maximize the above benefits.

    The downsides of dedeferation

    Conversely, defederation has a lot of downsides.

    1. It obviously negates all the benefits of federation mentioned above. Every time two instances defederate, the Lemmy network becomes less redundant, some communities become a bit more centralized, and the danger of malicious admins for those communities becomes much greater.
    2. There is a lot of collateral damage. The most common reason I have personally seen for defederation demands is related to moderation of either a single user, or a handful of users. For example, a user gets into some heated arguments with people from an instance with hundreds of active users, and then links this heated thread to me as proof that the instance should be immediately defederated. However, in this situation, there are hundreds of other users who were not even involved (or even aware of) the thread in question. By defederating, I would be making a decision to cut off every single user from every single one of those hundreds of innocent remote users.
    3. Ironically, defederation actually makes moderation more difficult. It was recently pointed out to me by a user on another instance that they are afraid they can’t effectively moderate communities on, because their instance has defederated several other instances, which means they would not be able to see posts from those instances on communities.
    4. It is extremely easy for malicious actors to abuse. In the year I’ve been on Lemmy, I have already seen two separate cases of users creating accounts on another instance and posting garbage, and then going back to their home instance and demanding their admins defederate over the content they themselves created. Basically, if an instance is known to use defederation as a tool to punish misbehaving users on other instances, then it’s actually quite easy for users to manipulate the situation to a place where admins have no alternative except to defederate.

    It seems to me that a lot of users don’t think of such downsides when demanding defederation, or they just don’t consider them as important enough. In my opinion, these are all significant issues. I do not want to end up in a fragmented Lemmy network, where users are required to have accounts on 5 different instances in order to be able to access all their communities.

    What’s the alternative to defederation? Should Lemmy become some kind of unmoderated free speech abolutism platform?

    I want to be very clear that I do NOT believe in unmoderated social networks. Communities should always be free to set and enforce rules which foster healthy discussions. On top of that, instances should always be free to set and enforce rules for all of their users and communities.

    In the case of, we have some instance-wide rules, and we will enforce them on all users, as well as all remote users participating in communities hosted on For example, we never want to offer a platform for bigotry, so we regularly issue permanent bans for users who want to abuse to spread such hate. In practice, site bans have been extremely effective at getting rid of awful users, whether they are remote or local.

    On top of site bans, Lemmy admins also have the option of removing entire remote communities. There are certainly cases where a community might be allowed on instance A, but not instance B - rather than defederating (and potentially cutting off a lot of innocent unrelated users), instance A can just “defederate” a single community.

    Finally, a lot of issues can be solved through simple communication between instance admins. Often having a discussion with another admin results in pretty clear alignment over whether some user is problematic, and the user will end up being banned on their home instance.

    Being one of the most openly federated large instances with such an approach, we have discovered several things:

    1. If we were to defederate over every rule breaking user or community on the Lemmy network, we would not be federated with any of the large instances at this point
    2. In the vast majority of cases, remote users who have broken rules have ended up banned on their home instance anyway - there is very little additional moderation workload for our admins from being widely federated
    3. If a user truly wants to spread some kind of hate, defederation wouldn’t stop them anyway, as they will just create accounts on any instance which they want to “attack”

    The longer I run, the more sure I become that in the vast majority of cases of abusive users, the best approach is to simply hand out site bans.

    When is defederation the only option?

    Having said all of the above, I still believe that there a few cases when defederation is the best option:

    1. When an instance is abusing the Lemmy network - generating spam, advertising, illegal content, etc - either deliberately, or through inactive admins (this has been the most common reason for to defederate any instance in the past)
    2. When an instance is just causing too much moderation workload. So far, we haven’t experienced this yet on, but I can’t rule out that it could happen in the future.


    I hope this post helps clarify my stance on defederation. Like I said in the beginning, I realize a lot of this is subjective, and there are no right or wrong answers - this is just the way we have been (and will be) doing things on I intend to save this post and link it in the future when people bring up defederation requests. If you feel like I didn’t address something important, please feel free to raise it in the comments!

  • When this post is 3 hours old, will briefly go offline for database maintenance

    Hey folks

    Just a heads up that I will be doing some minor database maintenance shortly. I expect the downtime to last <5 minutes.

    Have a nice day!

    Update: maintenance is complete!

  • Cross post broken?

    When I select the cross post option everything looks as normal. When I select the community I want to cross post to, all information in fields above drop-down is deleted. Tried copying the URL and re-pasting in the url field but the system refuses to generate the title after selecting the "generate title" option that is offered.

    I am operating on a phone via mobile site so my workaround options are limited

  • Thumbnail Preview Links Broken?

    Link previews seem to be broken since upgrade. As you can see this isn't from all instances so is this a federation issue or an upgrade issue?

    For what it's worth I get the same experience in Voyager app on Android as well as web-ui.

    Anyone else experiencing the same?

  • Happy cakeday,!

    Hey, folks!

    Today, we can celebrate the first anniversary of the creation of! I thought it would be cool to write down how was born, as well as collect some stats about our first year. Here goes!

    A quick recap of the beginning of this instance

    As probably many others here, I discovered Lemmy early last summer. I had been aware of the Fediverse previously, and always thought it was an amazing concept, but I had never been super interested in Twitter-style social networks. When I found out that Lemmy combined all the great parts of federation with the best parts of link aggregation, I knew that I had to join immediately.

    As I was trying to find an instance to make my account on, I realized that most instances were struggling to keep up with a massive influx of new users. At the time, there was a big explosion in Lemmy user numbers, and the network wasn’t fully ready for it. I have some experience with building software for scale, so it felt natural to set up a new instance and try to help with spreading out the load. I got to work in the evening of the 8th of June, 2023, and I was actually so excited about everything, that I completely skipped sleep that night. By the morning of the 9th of June, was online.

    From the very beginning, I always intended for to be a welcoming, reliable, and stable gateway into the Lemmy network. I wrote a welcome post on, which most of you have probably seen, as well as a comment on inviting new users to (, as many instances, was extremely overloaded at the time).

    We started growing extremely quickly. Thousands of users joined over the first few months. Even during the biggest waves of new users, we never closed our sign-ups. The first month or two were definitely very stressful in terms of just trying to deal with the load, but overall, I think I managed to deal with it well enough, and has been running more or less smoothly (with a few exceptions) ever since.

    Some stats about the first year

    I promised to collect some statistics about so far. This is what I’ve come up with:


    Overall, has 28,715 registered users. Of course, it’s easy to create an account, and most of these are probably inactive at this point, but it’s still a ridiculous amount.

    Of all the registered users, 7903 have made at least one post or comment.

    7373 users have never made any posts or comments, but have still been voting. This means that out of users who actually interact on, more than half generate content (through their comments and posts) - this is way more than I expected!

    Meanwhile, we also have 13,439 users who have never made a single comment, post or vote. I guess most of these are people who just signed up and never got into Lemmy, but I’m sure there are quite a few hardcore lurkers among this group as well.

    As for communities, our users have created 1430 of them. Most of these have not (yet) taken off, as only 491 of these communities have at least one comment in them. In general I am happy to see some great communities appearing on - my hope is that we can spread awesome communities out quite evenly on the network, so that in the end, no instance becomes a single point of failure for Lemmy.

    Judging by posts and comments made by users, I feel like we’re definitely on the right track: our users have made 20,898 posts in local communities, and 30,847 posts in communities hosted on other instances. The situation is even better for comments, where users have written 42,785 comments in local communities, and a whopping 569,730 comments on remote communities! This means that is not just its own little closed pocket in the Fediverse, but indeed a proper gateway to the Lemmy network, which is exactly what I always hoped it would be.

    Note about comment and post counts: I realize the numbers above don’t match the stats about posts and comments on our front page, I’m guessing something is out of sync there, but the stats I am sharing here are based on actual fresh data, counted directly in our database today.

    Lemmy (and would be quite useless without its users, so a big thanks to all of you for using!


    We have a really awesome volunteer admin team, with admins putting in countless hours of their free time to help weed out bad actors. A lot of the work our admins do is completely invisible to most users. I think the admin team does not really get enough recognition, and in fact in many cases, they actually get some undeserved abuse thrown at them.

    I am personally very grateful for everybody who has stepped up to be a part of the team, and I think all users benefit from their work every day. In the past year, our admins have handled 12,329 reports from users. While most reports aren’t too bad, and don’t require harsh action, there is still a significant amount of these reports which contain the absolute worst content which you can find on Lemmy - hate speech, bigotry, gore, even illegal content. Our admins are constantly going through every single report they receive, to ensure that mods are getting admin-level support where needed, and to ensure that malicious users in general can’t use to spread garbage into the Lemmy network.

    In terms of admin actions, I think the most interesting statistic might be amount of users banned by admins, grouped by their home instance. I will list the top 10 instances here:

    • 581
    • 355
    • 31
    • 29
    • 28
    • 26
    • 22
    • 19
    • 18
    • 16

    As you can see, with the exception of, the vast majority of our instance bans are for our own users. Most of the big instances are actually very good at banning their own abusive users, and once they are banned on their own instance, our admins don’t really need to worry about them, as they have no way to log in at that point. is a bit of a special case - they either don’t give out a lot of bans, or those bans just don’t federate to Lemmy properly, and for some reason, a lot of advertisers sign up on that instance all the time.


    I have received some questions every now and then about how much it costs to run While you can always get a sense for the predicted monthly costs for the current month on, I thought I might include a full breakdown of our costs for the first year here.

    Here are all of our costs for the past year, grouped by service:

    • Postmark: 177.06€
    • Cloudflare: 222.28€
    • DigitalOcean: 1744.27€
    • Hetzner: 510.20€ ( migrated from DigitalOcean to Hetzner several months ago)
    • Backblaze: 3.78€ (we’ve been using Backblaze B2 for a few months now, it’s incredibly cheap)
    • Domain registration: 100.70€ (paid for the next 10 years!)

    We are currently completely funded by users!

    There is a small minority of users who are shouldering the entire cost of for all of us. I am extremely grateful that others find Lemmy useful enough that they have put their own money into ensuring financial stability for

    We currently have 49 active sponsors on GitHub, and 7 active supporters on Ko-Fi. In addition, there have been 62 more sponsors on GitHub over the past year, as well as 49 additional supporters on Ko-Fi. This means that in total, 167 users have supported financially. This has completely exceeded all my expectations, I really think it’s incredible. A huge thanks on behalf of myself (and I think I can speak for all other users here as well) to all the supporters!


    Running has certainly been a rollercoaster in many ways. There are a lot more things which happened during the first year that I could write about here. On the other hand, this post is already quite long, and a lot of the things which happened are probably best forgotten about anyway, so I think I should wrap up here 😅.

    At its core, Lemmy is really an amazing piece of software. It’s helping real humans connect on the internet, without any corporate bullshit. I am very happy to be here with all of you, thank you for joining for its first year, and I hope you’ll join me here again when I write this post in another year from now!

  • A way to reply to a ban

    Hey there! I recently got server banned b/c I was sharing a link in men's communities and I was mistaken for a bot.

    I didn't have a way to respond to the ban. I was just logged out. I didn't see a link or even which mod did the ban so that I could reply to them, but then I couldn't get into my account to reply anyway.

    It'd be nice to maybe get a "if you think this was in error" email or something.

    Although I know that if lemmy was the size of reddit, people would hook that email up to chatgpt, so :/

    Anyway, it'd be a nice feature to have. I doubt I'll need it again, but I was quite confused as to what to do.

  • Update about infrastructure & upcoming cakeday

    Hey all!

    Upcoming cakeday

    Can you believe that is almost 1 year old? In just a couple of weeks (specifically, on the 9th of June), we will be able to celebrate our first instance cakeday.

    I am thinking of compiling some stats about how has been used in its first year, if you have any specific stats in particular you would like to see, feel free to comment below. I will try to accommodate any ideas as I start gathering this info!

    Infrastructure updates

    A few weeks ago, I posted about plans to make some changes to our infrastructure in order to deal with different intermittent networking issues.. It took a bit longer than I hoped (just did not manage to get enough free time between then and now), but I am happy to report that this work has now been completed! Additionally, I have decommissioned our stand-alone pict-rs server.

    With the two changes mentioned above, I believe should now be much more resilient going forwad, and I expect a significantly lower rate of infrastructure-related issues for the rest of the year!

    I'll leave a tehcnical overview about the problem & solution below for those interested, but if these details don't interest you, then you can safely skip the rest of this post.


    For context, has been hosted on Hetzner servers for most of this year (having migrated from DigitalOcean initially), with everything except our database being hosted on the Hetzner Cloud side, and the database itself living on a powerful dedicated Hetzner server. This mix allows a great amount of flexibility for redeploying and horizontally scaling our application servers, while still allowing a really cost-effective way of hosting a quite resource-hungry database.

    In order to facilitate networking between the cloud servers and the dedicated database server (which live in different networks), Hetzner provides a service named "vSwitch". This service basically allows you to connect different servers together in a private network. Unfortunately, I discovered quite quickly that this service is very unreliable. During the short few months that we have been using the vSwitch, we have gone through one extended period of downtime (where the service was just completely broken for several hours), as well as dozens (if not hundreds at this point) intermittent disconnects, where servers randomly lose their connections over the vSwitch. After such a disconnect, the connection never recovers without manual intervetion.

    For most users, the majority of these vSwitch issues have been mostly invisible, as we have redundancy in our servers - if one server loses its connection to the database, other servers will take over the load. Additionally, I have generally been able to respond quite quickly to issues by redeploying the broken servers (or deploying other temporary workarounds). However, in addition to a huge amount of these issues which users hopefully haven't ever noticed, there have also been a few short periods of downtime this year so far, as well as a few cases of federation delays. These more extreme cases were generally caused by multiple servers losing their vSwitch connections at the same time.

    After several attempts to work around these issues, I decided that we need to migrate away from vSwitch.

    As of earlier today, is no longer using Hetzner's vSwitch at all!

    I finally found enough time earlier today to focus on this migration, and I was able to successfully complete it. None of our networking is relying on the vSwitch anymore.

    In the end, I went with quite a simple solution - I configured a host-level firewall (nftables) on our database dedicated server, which will deny all connections by default. Whenever any cloud servers are added/removed, their corresponding public IP addresses are added/removed in the allowlist of our database firewall. It would have been ideal to do this whole logic in Hetzner's own firewall, but that one unfortunately has a limit of only 10 rules per server, which is just not enough for our setup.

    Bonus: our pict-rs server has been decommissioned!

    Pict-rs is the software which Lemmy uses for everything related to media (image storage mostly). Initially, pict-rs required a local filesystem to store both files as well as metadata about files. Since the beginning, has used a dedicated server just for pict-rs, in order to ensure we could easily redeploy the rest of our servers without losing any images.

    Over the past year, pict-rs has gained the ability to store files in object storage, and metadata in a PostgreSQL database. This meant that the server running pict-rs itself no longer contained any of the important data, so it became possible to redeploy without losing any images. Additionally, this meant that it would be possible to run multiple pict-rs servers in parallel.

    While we had already migrated our pict-rs server to use object storage and PostgreSQL several months ago, we still had the single dedicated pict-rs server up until today. I have been planning for a while to decommission this server, and start running pict-rs directly on each one of our Lemmy application servers. Earlier today, I was able to complete this plan. This should hopefully mean that our pict-rs server is less likely to get overloaded, and it also means a tiny reduction in our overall monthly infrastructure bill (due to one less server running).

    With the above changes, I think our infrastructure has become more robust, and hopefully, we will experience less issues with images, federation, and general downtime going forward.


    That's all from me for now. Feel free to leave any thoughts or questions in the comments, and as always, I hope you're having a great day!

  • Notice for all moderators: please check the moderation policy

    Hey folks!

    This is a quick notice about a change to our moderation policy.

    We have had a policy on for administration and federation nearly since the very beginning. This policy has also always included a section about moderator responsibilities. Today, we have made two changes to this policy:

    1. The policy has been renamed to Policy for administration, moderation, federation - this is to make it clear that the policy is also relevant for mods
    2. We have introduced a new responsibility for moderators, they must "Ensure that they only provide accurate and clear reasons for mod actions".

    The reason for the addition is that mod log actions federate out to other instances, and are more or less permanent (due to how Lemmy and federation works right now). This means that users do not really currently have any easy way to clarify or defend themselves against inaccurate accusations in the mod log.

    As always, I am very grateful to all mods for your efforts in building awesome communities on I hope you can understand why this new policy is necessary - I do not want to make your lives more difficult, the goal is to just try and reduce any mod log related misunderstandings in the future.

    Thank you for reading and have a nice day!

  • Whoa...! I was editing one of my community documents, and suddenly the whole community disappeared. Can you help?

    My community is:

    The post I was working on was:

    To be clear-- I, in no, way, shape or form intend to delete my community. I wish the community to remain undeleted, thanks.

    In case it matters:

    > 57 users / day > 150 users / week > 444 users / month > 1.53K users / 6 months > 635 subscribers > 317 Posts > 902 Comments

    EDIT: Google retains the specific URL's of a bunch of our posts, such as the "Moebius" ones.

  • 2024-05-06 downtime

    Hey folks!

    We unfortunately had about half an hour of unplanned downtime today. This was caused by an issue with our hosting provider. The issue is solved for now, and I am planning to make some changes to prevent similar issues in the future. Sorry for the inconvenience!


    Technical details

    Our servers are communicating with our database over Hetzner's "vSwitch" service. Unfortunately, this service seems to be quite flaky - over the past few months, I have had to deal with the connection just dropping without recovering many times. Mostly this has not resulted in any noticeable downtime, as we have redundant servers, so even if one of them stops working, it won't affect users. However, in this instance, all of our API servers lost their connection to our database at the same time, which resulted in actual downtime.

    I have now decided to migrate our setup away from the vSwitch in the near future to hopefully stop these issues for good. Should be possible to do this migration without any downtime, I just need to set aside some time to actually create an alternative solution for us, most likely over the coming weekend. I will update this post once the migration is complete.

    Update: the migration is now complete! You can read more here.

  • Not seeing banner image in my lemmee community

    EDIT: I should have posted this in the Support community - as others are also doing.


    Just noticed tonight that when I visit my FullMoviesOnYouTube community, the banner image is not shown.

    I tried linking directly to it:

    And got this error:

    {"error":"unknown","message":"Request error: error sending request for url ( operation timed out"}

    Any idea what's up? It's definitely been working as of just last week.

  • Federation delays?


    I noticed that a post I created from my sopuli account to a community, federated over here, but then not out any other instances.

    Is dealing with similar federation woes as

  • What makes thumbnails show up in f.e. Jerboa?

    I was using imgur now to upload pictures, but for none of my posts it shows a thumbnail for me in jerboa. It does at least for some of those using, so i assume this may be something specific? Thumbnails seem to be shown for images hosted on or other instances. I just don't get what the difference is.

    What is it that would make thumbnails show up?

  • When this post is 6 hours old, will undergo database maintenance, which will include a few minutes of downtime

    Hey folks

    This is just a quick heads up that I need to perform some maintenance & upgrades on our database server, which unfortunately will require downtime. I don't expect the downtime to last for longer than 2-3 minutes, but just wanted to give a heads up first so you know not to be concerned.

    That's all, hope you have a great week!

    Edit: maintenance complete!

  • Should our asklemm(y/ee) communities remain, or remain unmoderated?

    There's presently [email protected] and [email protected], but both have low activity and appear to be unmoderated. Removing communities is probably reserved as a last resort, and seeking some moderators may be preferable, so I thought I might ask about'em to raise some attention.

    These are the kinds of communities that could get pretty rough if left in their current unattended state, I think.

  • Announcing lemmy-ui-next, an alternative Lemmy frontend built with NextJS!

    Hello, friends!

    TL;DR: I am working on a new Lemmy frontend in nextJS. There is still much work to be done, but you can already have an early look at

    First of all, quick note to users: I am making this announcement post in [email protected], as this is also a notice that I will be hosting an alternative frontend (lemmy-ui-next) for the first time on Going forward, I will post updates about lemmy-ui-next in a separate dedicated community: [email protected]. If you're interested in future updates, please subscribe there!

    What is lemmy-ui-next?

    Lemmy is generally accessed through some kind of frontend UI. By default, Lemmy provides its own web interface (lemmy-ui), which you can find on the front page of most Lemmy instances (including There are also several other independent frontends, for both the web and different mobile platforms, which I'm sure many of you are familiar with.

    Lemmy-ui-next is a brand new alternative frontend, built from the ground up with modern and popular tooling - a framework known as NextJS. Lemmy-ui-next has (or aims to have) the following high-level features:

    • Open source (AGPL)
    • Drop-in replacement for lemmy-ui - same exact URL structure, so all existing links will continue working
    • Very plain & minimalistic UI, strongly inspired by other link aggregator sites (of course including the original lemmy-ui!)
    • Very basic and "typical" NextJS architecture, to encourage open source contributions
    • Fully functional even when JavaScript is disabled (but works better with JS enabled!)
    • Optimized data transfer between your browser and the server (filtering out only relevant data from the Lemmy API, caching, memoization)
    • Strong focus on privacy and security (all authentication with the Lemmy API is done through secure httpOnly cookies, user IP addresses are not leaked to external image hosts, etc)

    What is the current status of lemmy-ui-next?

    I have mentally split the initial work I want to complete into 3 milestones:

    1. Lurk - All read-only features of Lemmy
    2. Participate - Voting/posting/commenting/DMs/reports, etc
    3. Moderate - Handling reports, creating & managing communities, etc

    I am now nearing completion of the first milestone. It's not 100% there yet, but you can already log in, browse, subscribe to communities and even vote. Some things may still look a bit wonky, and some features are still missing, but the core experience is getting there.

    In terms of code contributions, I would ask anybody who is interested in getting involved to contact me first before working on anything. I am not looking for PRs just yet - the code structure is still a bit loose, and I am redefining it as I add more stuff. I would ideally really like to complete the first 3 milestones before opening things up for external contributors.

    Who can use lemmy-ui-next?

    At the moment, it is only hosted on this instance, at I do not yet have any formal instructions for running it on other instances, but generally speaking, it is a simple NextJS app - to deploy it, you just need to do: npm install, npm run build and LEMMY_BACKEND=https://<your lemmy api here> npm run start.

    Why not just improve lemmy-ui instead?

    Lemmy-ui is an extremely important and valuable project. There has been a significant amount of hard effort put into it so far, and nobody can refute that it is the frontend which has really carried Lemmy to this point.

    Unfortunately, there are some architectural problems with lemmy-ui (mostly related to how data is fetched and how sessions are stored in memory), all of which would require quite a significant rewrite to fix. Additionally, I think that the core technical solution used for lemmy-ui is just a bit too obscure, which has been an obstacle to my own contributions, as well as to contributions by others. If a rewrite is on the table anyway, then I believe a different technology is the best way forward.

    Why not work on lemmy-ui-leptos instead?

    Lemmy-ui-leptos is another rewrite of lemmy-ui, which is being lead by Lemmy maintainers. It is based around a Rust web framework called Leptos. I think this is really cool tech, and will be happy to host lemmy-ui-leptos on in the future as well.

    There are a two key reasons why I personally decided to start working on another alternative, though:

    • I have heard from several people on Lemmy that they feel like Leptos is a big barrier to entry in terms of them contributing
    • Even for myself personally, I am very comfortable (and think I can move very fast) when working on something like NextJS, but with Leptos, I think the learning curve would be quite big and I would get much less done with any time I invest into it

    My hope is that by providing a very vanilla alternative, I can provide an outlet for potential open source contributors who would like to work on Lemmy, but aren't prepared to do it with Leptos.

    Does this mean that will change in ways I don't like?

    First, let me be clear: will always host the default Lemmy frontend. This means lemmy-ui for now, and most likely lemmy-ui-leptos in the future.

    I am however considering the possibility of switching things around at some point in the future, so that lemmy-ui-next will be hosted directly on, and lemmy-ui will be accessible on a different subdomain (like This would only happen once I have completed all 3 milestones for lemmy-ui-next. The main reason I am considering this is that I feel like I will always be in the best position to offer technical support to users on the frontend which I am myself maintaining. If you have any thoughts about this potential change, please let me know in the comments below!

    That's about it for now!

    This is something I've been thinking of doing for a while now, and I'm very excited to finally get the ball rolling! If you have a chance, please feel free to check out what looks like so far, and please let me know if you have any thoughts or feedback!

  • Vote fuzzing. Are we seriously doing this here now too??

    You know we all escaped Reddit for greener pastures. But I have increasingly noticed that greener pastures are not to be found in the Fediverse either.

    I undeniably witnessed some vote fuzzing this morning and I feel a bit psychologically violated whenever I notice people or companies or platforms engaging in psychological manipulation.

    It does make me feel livid.


    Update - case closed because:

    ------ Wisdom from [email protected]

    >There is no vote fuzzing in Lemmy. The software doesn’t support it. Period.

    >I’ve been paying attention to the Lemmy mod tools and Lemmy admin Matrix rooms, and it’s been the subject of major discussion over the past week between one or two users who keep bringing it up and, like, everyone else (including the Lemmy devs) who are all like, “no, not now, not ever.”

    >It’s not a thing.

    >SO, what could explain what you’re seeing?

    >Possible explanations include:

    >Vote brigading

    >Alt account abuse

    >A genuine statistical fluke where there are genuine votes that are producing this bizarre pattern, and hopefully it will subside soon along with your reasonably justified paranoia.

    >The solution to all of these possibilities, and possibly others that I did not enumerate here, is to just ignore the problem and move on with your life. Remember: nothing that happens here is really important.

    >I really hope this makes you feel better. Because it should.

  • Hetzner networking issues & minor downtime


    This is just a quick heads up that our host, Hetzner, has been experiencing networking issues today, which has caused some downtime for

    I have a workaround in place for now, so we should (fingers crossed) be recovering at the moment, but I am still waiting on the proper solution from Hetzner. You can track their issue here:

    Also, this is a good opportunity to remind everybody about - you can be sure that I will provide updates on that page as soon as I am aware of & dealing with any issues. I have been posting status updates for the current issue there as well.

    Sorry for the inconvenience and I hope you have an otherwise great day!

    UPDATE: Hetzner claims they have fixed the issue, but the problems have not been resolved for servers yet, so I am keeping my temporary workaround active for now. Will continue troubleshooting this tomorrow.

    UPDATE 2: Hetzner has now fixed their issue, and our network has been restored to its original optimized state.

  • should we join? though this could be the incorrect place for this repost

    cross-posted from:

    > Join Lemmyvision, a Eurovision-like Song Contest for Lemmy communities around the world ! > > Crossposted from > > > TLDR > > - From right now and until April 1st, discuss with your country's community on Lemmy about which song to send and share to the Fediverse. > - On April 1st, voting will begin, where you will rank your favourite songs. Any song not submitted by this date will not be featured. > - On April 8th, results of everyone's favourite songs will be published. > - Join us at [email protected] for any question, this will be the community for updates and results, make sure to subscribe if you'd like to stay in the loop. > > Hey everyone! > > I'm trying to launch Lemmyvision, a Eurovision-like Song Contest for Lemmy communities around the world ! I'd love for people across Lemmy to participate, I hope it will bring people together through our diverse taste of music, so join us if you'd like to discover new music and culture from around the world! > > > What is Lemmyvision? > > - Lemmyvision is inspired from Eureddision (itself a reenactment of the Eurovision song contest) which was held on r/europe some years ago, and based on the participation of national communities / instances and the delicate musical taste of their members (you!). > - Every country is welcome to participate! The contest follows the rule of “national languages only”. The aim is to promote different languages and cultures from around the world, to share more between our online communities across Lemmy, and discover songs from lesser known artists. I hope to make it a regular event, so hopefully this works well for the first edition! > > I'm going to try and share the word across Lemmy, don't hesitate if you want to crosspost to your country's community! > > You can find more information on [email protected], don't hesitate if you have questions or suggestions, or would like to help! > > See you soon! ❤️🧡💛💚💙💜🤎🖤🤍

  • Hexbear?

    So, I thought Hexbear defederated from us a little while back, and we, in turn, defederated from them. Why do I keep seeing occasional (new) Hexbear posts in the "All" feed, lately? Did the defederation get reversed? Is it somehow a bug?

  • Weird feed behavior

    I just joined from I was drawn to bc it federates with all the right instances.

    But my feed is behaving oddly. (I view Lemmy through the Eternity app on Android.)

    • I'm seeing posts from communities I haven't subscribed to, even when I view my "Subscribed" feed
    • I get a weird error when I try to comment on some posts (in [email protected], most recently)

    These issues didn't happen previously. Anyone know how to fix?

  • Ongoing spam attack on the Fediverse

    Hey folks

    Some of you may have noticed comments complaining about spam and lack of moderation within the past day or so. Maybe you've even noticed a few spam posts yourself (hopefully not too much, as we have automations in place on to remove the spam as soon as it is posted).

    I just wanted to write a quick post with some context about the attack, what we are doing about it, and how you can help.


    Allegedly, a group of kids in Japan have created a bot, which signs up on different Fediverse instances and posts spam into different communities. The spam generally consists of Japanese text and/or an image and/or a bunch of random @mentions into different communities. You can check a post on Mastodon with more information here:

    What we are doing about it

    Many instances are actively working to limit this spam-wave, and is no different. Thankfully, we have not had to deal with any bot sign-ups on our instance (potentially as a result of different protections we have implemented for sign-ups), but we still suffer the effects of the spam, even if it's posted from other instances. To help us quickly eliminate most of the spam for users, I am continually tuning our @adminbot to automatically detect and remove content posted in this current spam-wave.

    We cannot remove content from the wider Fediverse if it's not posted there by a user, so our automated removals won't help users on other instances, but we are at least improving the experience for our own users. For an example, you can compare how /c/[email protected] currently looks like on, to how it looks like on this screenshot I took from another smaller instance:


    How you can help

    First and foremost, please continue reporting any spam you find, so that relevant mods and admins can deal with it. I am very grateful to users who help us identify spam through reports, and your reports are precisely what allow me to implement automated content removal for more extreme spam-waves such as this current one.

    Secondly, I am seeking for a few volunteers to grow the admin team. I am purposely burying this at the bottom of the post, to hopefully pre-filter out some candidates who would want to join for the wrong reasons. If you have read until this point in the post, then I assume you are already quite interested in improving the experience on, so if you feel like you could contribute to the admin team, please read on.

    First, I will say a few words about who we are looking for, then I will describe what kind of tasks you would have as an admin, and finally, I will cover some significant downsides of joining the admin team.

    We are looking for folks who more or less match the following profile:

    • You have already been active on the Fediverse for several months (not necessarily on
    • Previous mod experience would be a huge plus
    • You should feel a strong agreement with our basic instance rules and our administration & federation policy
    • You should be prepared to be exposed to some vile content through reports
    • You are OK with using Discord as the main method of admin communication (that is what we have settled on and will continue using for the foreseeable future)

    As volunteers, we don't expect admins to be available 24/7, but as our instance grows, I do think it would be quite important to achieve a state of pretty good timezone coverage with our admin team, so please only consider applying if you are already regularly active on Lemmy.

    As for what tasks admins are responsible are for: it's mostly covered in the administration policy post linked above. But in short, you should be prepared to regularly check the report queue, contact users with friendly messages to de-escalate conflicts, issue bans, remove content, and monitor the activity of @adminbot. Additionally, if you're interested in taking a more hands-on approach to any kind of community-building on, then this would be totally welcome as well, but not strictly considered a core responsibility for admins.

    Please note that the admin team has an absolute zero tolerance policy against any kind of abuse towards minority communities. If you do not share this mindset, then please do not consider applying.

    Finally, let me share some negative aspects about joining the admin team. I think this will probably reduce the amount of any potential candidates, but I still feel it's important to be honest and upfront about this:

    Through the report queue, you will regularly see absolutely vile content which you might otherwise never even notice on Lemmy. Many users come to Lemmy to spread hate, post disturbing images, etc, and in order to clean such content up for other users, mods and admins need to actually be exposed to this content in much larger amounts than regular users.

    Additionally, while Lemmy is constantly being improved by the developers, the moderation tools are still quite rough around the edges. Lemmy is not at 1.0 yet, and that will most likely become even more obvious to you as you work on admin tasks.

    Maybe this is the most important one: no matter what you do, there will always be people unhappy with how you apply our rules. I have seen countless comments complaining about admins specifically. I have been told by complete strangers that they hate me. I have seen many complaints about us moderating too harshly. I have seen complaints about us not moderating enough. I have seen users on Lemmy make up wild stories about our admin team, and share them as facts. There are of course plenty of supportive users, but the negative experiences tend to leave a much more lasting impression.

    If after reading all of the above, you are still motivated to help make a better place through offering your help in the admin team, please contact me on Discord (@sunaurus)!

    That's all from me for now. Thank you very much to anybody who went through this whole wall of text, and I hope you are all having a good weekend!

  • JPG Picture Uploads Are Working

    edit - the original title was "Are Picture Uploads Allowed or Not?"

    I know pic uploads weren't allowed and a file size message would appear.

    I forgot and made a post earlier today with a pic (PNG). There was no error but the pic didn't appear. I updated the post with a link to the picture hosted elsewhere (

    Before this post I created a test post with another picture (JPG) and it uploaded and displayed. (edit - I deleted the post).

    I added the same test picture to this post.

  • TIL there is an auto-expand media setting!!

    When did this happen?! It makes me so happy!

    It's still not quite as good as old reddit with RES was, where you started with everything normal and then clicked a button to expand (or contract) media. Being able to contract everything is almost as useful, particularly if you want to scroll further down. However it's still a great improvement, as well as proof that lemmy just keeps getting better.

  • Could we have Alexandrite and Photon front-ends on

    I've searched but couldn't find any discussion on this topic, so I apologize if it's been answered before.

    Would the admins consider hosting the Alexandrite and Photon front-ends, e.g. at and

  • We have a new status page, including federation status, at!

    Hey folks!

    Just a quick update: we now have a dedicated status page for

    You can find it at It currently contains three sections:

    1. A web status section, which I will update manually to communicate issues about
    2. A financial status section, which I will update monthly to give an overview of how we're doing financially
    3. A federation section, which automatically checks the current federation status, both incoming and outgoing, between and other instances. By default it shows 3 large instances, but you can also search for any specific instance you are interested in.

    This status page is hosted completely separately from our main servers, so if there is any trouble with our servers, you can expect the status page to still be available!

    If you have any issues with this page, or any other thoughts, feel free to comment.

  • Did block the and zerobytes bots?

    I’m subscribed to a couple of communities where those bots post regularly. I noticed a drop in content recently and realized I haven’t seen those bots for the past week. I’m trying to figure out where they got blocked and was wondering if our instance blocked them. Anyone have an idea?

  • Can't stay logged in. No Previous button?

    If I close all tabs that I have opened for a session it always logs me out and I have to relog, which is so annoying, especially after having 2FA enabled. Is this only me or has nobody else reported this issue?

    Also, why is there no "Prev" button after clicking on "Next" at the bottom of a page? I get using the back button, or shortcut but sometimes it's convenient to click it, or even just to know if you've scrolled to another page. OK so apparently this is an intentional Lemmy change that removed it. Hard disagree, but oh well.

  • Thanks for the quick, painless, and silent update to 0.19.2!

    After the tumultuous 0.19.0/0.19.1 update over the holidays, the 0.19.2 update was so quick and smooth, i didn't even notice!

    Thanks so much to @sunaurus (and other admins) for all the hard work!

  • When this post is 48 hours old, will be going down for a database upgrade (Edit: upgrade complete!)

    Hey folks

    This is a heads up that I will be performing some maintenance and hardware upgrades on our database this Saturday.

    We are currently experiencing several spikes throughout the day which cause our database to become overloaded - this results in degraded performance for many users. The spikes are happening due to a combination of continued growth of the database, some expensive periodic scheduled tasks which Lemmy runs, and fluctuating traffic patterns. Some of this can be optimized on the code level in the future, but it seems that the best way to deal with it right now is to add some additional resources to our database server.

    I am intending to switch to slightly different hardware in this upgrade, and will be unable to make this switch without downtime, so unfortunately will be unavailable for the duration.

    As our database has grown quite a bit, cloning it will most likely take a few hours, so I expect the downtime to last 2-3 hours. Sorry for the inconvenience, I am hopeful that it will be worth it and that this upgrade will significantly reduce some of our recent long page load times!


    Edit: upgrade complete!

    I have now migrated the database from the original DigitalOcean managed database service to a dedicated server on Hetzner.

    As part of this migration, I have also moved all of our Lemmy servers from the DigitalOcean cloud to Hetzner's Cloud. I always want the servers to be as close as possible to the database, in order to keep latencies low. At the same time, I am very interested in having the ability to dynamically spin up and down servers as needed, so a cloud-type solution is really ideal for that. Fortunately, Hetzner allows connecting cloud servers to their dedicated servers through a private network, so we are able to take advantage of a powerful dedicated server for the database, while retaining the flexibility of the cloud approach for the rest of our servers. I'm really happy with the solution now.

    In terms of results, I am already seeing far better page load times and far less resource use on the new hardware, so I think the migration has been a success. I will keep monitoring things and tuning as necessary.

  • Image uploads, federation delays, and performance

    Happy new year!

    Hi folks! I hope everybody had a good holiday period and I wish you all the best for 2024. I have some quick updates to share about

    Image uploads

    Image uploads are now enabled for all users 4 weeks after account creation. The upload size limit is currently set to 500kb.

    The 4 week account age requirement is in place to discourage spam and abuse. It is of course not a fool-proof solution, but let's give it a go and see what the results are.

    Please note that is not intended to be a image hosting service! Feel free to upload avatars and banners for your profile and communities, but please be aware that we reserve the right to modify the upload limits going forward, as well as delete old images if storage costs become too high.

    For image posts and comments, it would still be preferable for you to use an external image hosting service.

    Federation delays

    Over the holidays, our outgoing federation workers began experiencing some significant delays. I have been working on this problem for the past few days, and after updating to 0.19.1, applying some additional patches to the code, and changing our infrastructure a bit, I believe the issue has been resolved.

    The good news is that now that we are on 0.19, problems such as this do not cause Lemmy to completely drop federated activities, as we now retain a persistent queue of federation activities for all linked instances. This means that after the issue was resolved, our federation workers started going through the backlog of likes, comments, and posts which you had made over the past several days, and sending these out to other instances. Essentially, all of your activities did end up reaching their target servers, just with some additional delay.

    One quick side-note here, while we are now federating your activities in real-time again to most big instances, there is still a bit of a backlog left on the -> federation (it is a few days behind). I expect this to also catch up by tomorrow.


    The new persistent federation queue is still quite a new feature in Lemmy, so it's a bit rough around the edges - after resolving the federation issues, our federation workers started going through the queue at extreme speed, which caused intense additional load on our database. This was one of the reasons for some performance degradation many of you noticed over the past few days.

    Additionally, since updating to 0.19, there have been regular performance issues for many users. I have managed to solve a few of these by making some changes in our infrastructure, but I am also aware of a few more issues which I will continue to monitor and hopefully improve in the near future. Sorry for the inconvenience, I hope that the changes I have made so far will help make it a bit smoother already!

    That's all from me for now, as always, feel free to comment if you have any thoughts, and have a nice day!

  • Did the instance get updated to 0.19.1?

    "read" posts are now hidden, footer says BE: 0.19.1. I didn't see any admin communication here nor any comments on the admin profiles. Is there another place to look for communication?

  • Problem with federation! Comments from seem to not federate

    Any news on why this is happening with this instance ? it might be harder to check if upvotes and downvotes federate to the outside lemmyverse .

    other instances seem to federate better.

    Don't the instance owners use it ?

  • Lemmy version 0.19.1 - Plans to upgrade?

    Recently, since the current Lemmy versions for this instance (0.19.0 for UI, 0.19.1-rc.1 for backend) may not be up-to-date with the final release of version 0.19.1, would an upgrade to the final version of 0.19.1 help with any issues the instance is suffering from lately?

    I'm not sure if this will resolve the federation issues the instance is currently having, but hopefully this helps.

1 Active user