Some websites block lemmy.ml links, for example Facebook as you can see in the screenshot below.

I dont know if this is because of the .ml domain (which is free and might be used by spammers), or because they are scared of Lemmy. Anyway, this doesnt mean that it is impossible to share content from lemmy.ml on Facebook or other sites, thanks to federation there is a relatively easy workaround:

1. Find another Lemmy instance, ideally one that is relevant to your audience
2. Copy the lemmy.ml link, and paste it into the search field of your chosen instance
3. You should get a search result for the post, comment, community or user, click on it
4. Copy the link and share!

There are a few caveats though: In the case of a post, comments and votes will be missing. You can fetch comments in the same way through the search. The other instance will also not receive any new posts/comments/votes made in the community, unless a user from the remote instance is following the lemmy.ml community.

The easiest way to avoid these problems is for you to make an account on the other instance and follow the community from it. Then every post/comment/vote will be delivered to the other instance, and the community should look identical on both instances.

Our server went down last night, after we received some messages from our provider that someone had uploaded illegal pornographic photos.

They stated that they had contacted us before ( they didn't ) which would give us opportunity to remove them before the site going down.

The user and community where these pictures were located, we'd banned about a month ago, and it wouldn't be possible to view them from lemmy itself, but we have yet to code purging dangling pictrs images automatically with user and community deletion, obviously now a priority for us.

We were able to trace things down and delete them, and bring the site up this morning.

Again sry for the site being down. If you find any pornographic materials on lemmy ( against our site rules ), let us know so we can remove them ASAP and keep lemmy running.

Since our last release this month, we've had ~60 commits to Lemmy.

Lemmy Server

Major Changes

• Add option to disable strict allowlist ( #1486) documentation
• Add option to limit community creation to admins only (#1587)
• Many search improvements:
  • Don't search for communities or users when the id is included.
  • Add creator id to search.

General

• Adding a user setting to show / hide scores. Fixes #1503
• Add option to hide read posts. Fixes #1561
• Mark accounts as bot, and hide bot posts/comments
• Adding a short site description, to be used for joinlemmy instance list
• Adding matrix id validation. Fixes #1520
• Adding users active monthly for community sort. Fixes #1527
• Don't allow zero-space char in display name. Fixes #1317
• Adding more rust captcha features. Fixes #1248
• Fixing slur filter regex. Fixes #1593

API

• Added ChangePassword as a separate endpoint from SaveUserSettings
• No other breaking changes, but many fields that were previously required are now optional.
• A full list of the API changes can be seen on this diff of lemmy-js-client: 0.10.0 -> 0.11.0 .

Federation

• Implement federated bans fixes #1298
• Remote mods can update/delete/undelete communities.

Lemmy UI

• Updating translations.
• Add UI version to UI via docker. Fixes #263
• Add Korean language
• Add check for unused languages in update_translations.sh
• Validate matrix id on the front end. Fixes #245
• Communities page sorts by monthly active users. Fixes #244
• Correctly render HTML in popup notifications
• Fix html notif bug. Fixes #254
• Fixing issue with debounce. Fixes #236

Upgrade notes

Servers

If you'd like to make a DB backup before upgrading, follow this guide.

To upgrade your instance to v0.11.0, simply follow the instructions in the documentation:

• Upgrade with manual Docker installation
• Upgrade with Ansible installation

Clients / Apps

• A full list of the API changes can be seen on this diff of lemmy-js-client: 0.10.0 -> 0.11.0 .

Recently there have been some discussions about the political stances of the Lemmy developers and site admins. To clear up some misconceptions: Lemmy is run by a team of people with different ideologies, including anti-capitalist, communist, anarchist, and others. While @dessalines and I are communists, we take decisions collectively, and don't demand that anyone adopt our views or convert to our ideologies. We wouldn't devote so much time to building a federated site otherwise.

What's important to us is that you follow the site rules and Code of Conduct. Meaning primarily, no-bigotry, and being respectful towards others. As long as that is the case, we can get along perfectly fine.

In general we are open for constructive feedback, so please contact any member of the admin team if you have an idea how to improve Lemmy.

Slur Filter

We also noticed a consistent criticism of the built-in slur filter in Lemmy. Not so much on lemmy.ml itself, but whenever Lemmy is recommended elsewhere, a few usual suspects keep bringing it up. To these people we say the following: we are using the slur filter as a tool to keep a friendly atmosphere, and prevent racists, sexists and other bigots from using Lemmy. Its existence alone has lead many of them to not make an account, or run an instance: a clear net positive.

You can see for yourself the words which are blocked (content warning, link here). Note that it doesn't include any simple swear words, but only slurs which are used to insult and attack other people. If you want to use any of these words, then please stay on one of the many platforms that permit them. Lemmy is not for you, and we don't want you here.

We are fully aware that the slur filter is not perfect. It is made for American English, and can give false positives in other languages or dialects. We are totally willing to fix such problems on a case by case basis, simply open an issue in our repo with a description of the problem.

A community for the modern day library of alexandria:

!libgen@lemmy.ml

Site mirror.

Lemmy v0.9.0 Release (2021-01-25)

Changes

Since our last release in October of last year, and we've had ~450 commits.

The biggest changes, as we'll outline below, are a re-work of Lemmy's database structure, a v2 of Lemmy's API, and activitypub compliance fixes. The new re-worked DB is much faster, easier to maintain, and now supports hierarchical rather than flat objects in the new API.

We've also seen the first release of Lemmur, an android / iOS (soon) / windows / linux client, as well as Lemmer, a native iOS client. Much thanks to @krawieck, @shilangyu, and @uuttff8 for making these great clients. If you can, please contribute to their patreon to help fund lemmur development.

LemmyNet projects

Lemmy Server

• Moved views from SQL to Diesel. This was a spinal replacement for much of lemmy.
  • Removed all the old fast_tables and triggers, and created new aggregates tables.
• Added a v2 of the API to support the hierarchical objects created from the above changes.
• Moved continuous integration to drone, now includes formatting, clippy, and cargo build checks, unit testing, and federation testing. Drone also deploys both amd64 and arm64 images to dockerhub.
• Split out documentation into git submodule.
• Shortened slur filter to avoid false positives.
• Added query performance testing and comparisons. Added indexes to make sure every query is < 30 ms.
• Added compilation time testing.

Federation

This release includes some bug fixes for federation, and some changes to get us closer to compliance with the ActivityPub standard.

• Community bans now federating.
• Local posts sometimes got marked as remote.
• Creator of post/comment was not notified about new child comments.
• Community deletion now federated.

None of these are breaking changes, so federation between 0.9.0 and 0.8.11 will work without problems.

Lemmy javascript / typescript client

• Updated the lemmy-js-client to use the new v2 API. Our API docs now reference this project's files, to show what the http / websocket forms and responses should look like.
• Drone now handles publishing its npm packages.

Lemmy-UI

• Updated it to use the v2 API via lemmy-js-client, required changing nearly every component.
• Added a live comment count.
• Added drone deploying, and builds for ARM.
• Fixed community link wrapping.
• Community Titles are now used instead of names.
• Various other bug fixes.

Lemmy Docs

• We moved documentation into a separate git repository, and support translation for the docs now!
• Moved our code of conduct into the documentation.

Upgrading

If you'd like to make a DB backup before upgrading, follow this guide.

• Upgrade with manual Docker installation
• Upgrade with Ansible installation

Known issues

Some older self-comments are being marked as unread in your inbox, click Mark all as read to resolve this.

Instructions for running your own lemmy instance.

For the moment, lemmy.ml is using an explicit allowlist for instances we federate with. If you currently run an instance, and would like to be added to join.lemmy.ml:

• Let us know either on !lemmy_instances, or commenting here.
• We'll add you to our allowlist.
• Add this block to your server's lemmy.hjson config (for open federation):

federation: {
  enabled: true
  tls_enabled: true
  # allowed_instances: lemmy.ml,other_instance.tld,... uncomment this to use an allowlist
}

• Type [!announcements@lemmy.ml](/c/announcements@lemmy.ml) into your server's search box, and subscribe to it to connect the two instances.

After almost a year of hard work implementing ActivityPub support on Lemmy, it is finally done! Anything that works here on dev.lemmy.ml, also works over federation between different instances (with one notable exception, community mods have to be on the same instance as the community for now).

Before we consider federation ready for production, some more testing is needed. And that's where you come in: go to our test instances enterprise.lemmy.ml, ds9.lemmy.ml and voyager.lemmy.ml, and try things like:

• post, comment and vote
• delete and restore posts/comments
• send private messages
• create communities, remove/restore posts and ban/unban users
• setup your own lemmy instance, and federate with enterprise.lemmy.ml or ds9.lemmy.ml

If you notice any bugs, please report them on Github, as comments on this post, or in our Dev Chat on Matrix. Please keep in mind that our code of conduct also applies to the test instances.

The more you test, the sooner we will feel confident to enable federation on dev.lemmy.ml. Happy testing!

Lemmy v0.8.0 Release (2020-10-16)

:partying face:

Changes

We've been working at warp speed since our v0.7.0 release in June, adding over 870 commits since then. :sweat:

Here are some of the bigger changes:

LemmyNet projects

• Created LemmyNet, where all lemmy-related projects live.
• Split out the frontend into a separete repository, lemmy-ui
• Created a lemmy-js-client, for any js / typescript developers.
• Split out i18n lemmy-translations, that any app or site developers can import and use. Lemmy currently supports ~30 languages!

Lemmy Server

Federation

• The first federation public beta release, woohoo :fireworks:
• All Lemmy functionality now works over ActivityPub (except turning remote users into mods/admins)
• Instance allowlist and blocklist
• Documentation for admins and devs on how federation works
• Upgraded to newest versions of @asonix activitypub libraries
• Full local federation setup for manual testing
• Automated testing for nearly every federation action
• Many additional security checks
• Lots and lots of refactoring
• Asynchronous sending of outgoing activities

User Interface

• Separated the UI from the server code, in lemmy-ui.
• The UI can now read with javascript disabled!
• It's now a fully isomorphic application using inferno-isomorphic. This means that page loads are now much faster, as the server does the work.
• The UI now also supports open-graph and twitter cards! Linking to lemmy posts (from whatever platform you use) looks pretty now:
• Improved the search page ( more features incoming ).
• The default view is now Local, instead of All, since all would show all federated posts.
• User settings are now shared across browsers ( a page refresh will pick up changes ).
• A much leaner mobile view.

Backend

• Re-organized the rust codebase into separate workspaces for backend and frontend.
• Removed materialized views, making the database a lot faster.
• New post sorts Active (previously called hot), and Hot. Active shows posts with recent comments, hot shows highly ranked posts.
• New sort for Local ( meaning from local communities).
• Customizeable site, user, and community icons and banners.
• Added user preferred names / display names, bios, and cakedays.
• Visual / Audio captchas through the lemmy API.
• Lots of API field verifications.
• Upgraded to pictrs-v2 ( thanks to @asonix )
• Wayyy too many bugfixes to count.

Contributors

We'd also like to thank both the NLnet foundation for their support in allowing us to work full-time on Lemmy ( as well as their support for other important open-source projects ), those who sponsor us, and those who help translate Lemmy. Every little bit does help. We remain committed to never allowing advertisements, monetizing, or venture-capital in Lemmy; software should be communal, and should benefit humanity, not a small group of company owners.

Upgrading

• with manual Docker installation
• with Ansible installation

Testing Federation

Federation is finally ready in Lemmy, pending possible bugs or other issues. So for now we suggest to enable federation only on test servers, or try it on our own test servers ( enterprise, ds9, voyager ).

If everything goes well, after a few weeks we will enable federation on dev.lemmy.ml, at first with a limited number of trusted instances. We will also likely change the domain to https://lemmy.ml . Keep in mind that changing domains after turning on federation will break things.

To enable on your instance, edit your lemmy.hjson federation section to enabled: true, and restart.

Connecting to another server

The server https://ds9.lemmy.ml has open federation, so after either adding it to the allowed_instances list in your config.hjson, or if you have open federation, you don't need to add it explicitly.

To federate / connect with a server, type in [!community_name@server.tld](/c/community_name@server.tld), in your server's search box like so.

To connect with the main community on ds9, the search is [!main@ds9.lemmy.ml](/c/main@ds9.lemmy.ml).

You can then click the community, and you will see a local version of the community, which you can subscribe to. New posts and comments from [!main@ds9.lemmy.ml](/c/main@ds9.lemmy.ml) will now show up on your front page, or /c/All

Credit to @eiknat@dev.lemmy.ml , and masterstur for their help with this effort.

Our postgres CPU usage has gone wayyyy down.

Let's start with the biggest news first: Lemmy is receiving funding from the NLnet foundation! The funding is for a total amount of 45.000 €, which will allow /u/dessalines and me (/u/nutomic ) to work on Lemmy full-time for at least half a year.

We have created various milestones for the work we are planning to do. Most of them are about getting ActivityPub federation ready for production. In addition, we will work on:

• better accessibility
• private communities and instances
• reworking search
• creating a joinlemmy.ml type site
• the option to block other users or communities

The details of the milestones will be posted on our github issue tracker soon.

We're very excited about this opportunity, and can't wait to finish federation.

In other news, we have just released Lemmy v0.7.0. Most importantly, this update switches to Pict-rs for image hosting, due to various performance-related issues with Pictshare. Pict-rs was coded from scratch in Rust by the amazing @asonix, who also created the ActivityPub library for Rust. We can't thank him enough for all the work he is doing for Lemmy!

We'd also like to thank the following people for their contributions:

• @iav for their work in building arm compatible rust docker images and builds.
• @ernestwisniewski and @bytesnake for code contributions.
• Many others for contributing translations via the Lemmy weblate.
• Our Patreon and Liberapay supporters who help us devote more time to Lemmy (We're still very far from these being able to sustain two developers)
• Everyone else who contributes to Lemmy, be it by coding, hosting instances or just using it and spreading the word!

Other than that, since v0.6.0 in January we've closed over 100 issues, fixed tons of bugs and added many new features.

You can find the full changelog and upgrade instructions here.

Edit: Here are the milestones for the funding

Just a public service announcement.

Here's what we have so far for the governing documents, also pasted below. Feedback / additions / changes would be much appreciated.

Lemmy Council

• A group of lemmy developers and users that use a well-defined democratic process to steer the project in a positive direction, keep it aligned to community goals, and resolve conflicts.

Voting / Decision-Making

Process

• Anything is open for discussion
• Voting done through matrix chat reacts (thumbs up/thumbs down)
• Require a simple majority for votes. (Maybe 2/3rds for more debated decisions).
• Once a decision is reached democratically, the dicision is binding and all group members have to follow it
• All members of the Lemmy council have equal voting power.
• Voting must stay open for at least 2 days.

What gets voted on

• Membership (joining, removing)
• Coding direction
  • Priorities / Emphasis
  • Controversial features (For example, an unpopular feature should be removed)
• Communication mediums
• Conflict resolution
• dev.lemmy.ml (domain and server)
• lemmy.ml and subdomains (excluding communism.lemmy.ml)
• git repo including mirrors (on github, gitea, etc)
• Any official accounts of the Lemmy project, for example the Mastodon account or the Liberapay account
• Changes to these rules

Joining

• We use the following process: anyone who is active around Lemmy can recommend any other active person to join the council. This has to be approved by a majority of the council.
• Active users are defined as those who contribute to Lemmy in some way for at least an hour per week on average, doing things like reporting bugs, discussing rules and features, translating, promoting, developing, or doing other things that aim to improve Lemmy as a whole. -> people should have joined at least a month ago.
• The member list is public.
• Note: we would like to have a process where community members can elect candidates for the council, but this is not realistic because a single user could easily create multiple accounts and cheat the vote.
• Limit growth to one new member per month at most.

Removing members

• Inactive members should be removed from the council after a few months of inactivity, and after receiving a notification about this.
• Members that dont follow binding council decisions should be removed.
• Any member can be removed in a vote.

Goals

• We encourage the membership of groups such as LGBT, religious or ethnic minorities, abuse victims, etc etc, and strive to create a safe space for them to express their opinions. We also support measures to increase participation by the previously mentioned groups.
• The following are banned, and will always be harshly punished: fascism, abuse, racism, sexism, etc etc,

Communication

• A private Matrix chat for all council members.
• (Once private communities are done) A private community on dev.lemmy.ml for issues.

Member List / Contact Info

General Contact @LemmyDev Mastodon

• Dessalines Matrix
• Nutomic Matrix, Mastodon

You can see it on the sidebar on the main page.

Let us know what you think about them.

An open chat. Recent comments on the right —>

The list of cross-posts shows both when you're creating a post, and on the posts themselves.

↓↓↓