Lemmy

12524 readers
1 users here now

Everything about Lemmy; bugs, gripes, praises, and advocacy.

For discussion about the lemmy.ml instance, go to !meta@lemmy.ml.

founded 5 years ago
MODERATORS
126
 
 

In my profile settings, I can choose my languages. A couple gripes with the web interface of this setting:

  • I have to hold down the Ctrl key to select multiple languages. While this was clear to me since I use this keyboard shortcut a lot in other contexts, this would definitely be confusing or unclear for most users.
  • This setting should be split into two. As of now, it determines what content you see, with all other content completely hidden...AND it determines what languages will appear in the language selector when making a post or comment. There should be separate settings for which languages are displayed and which appear in the language selector for a new post (because I don't want any content to be hidden, but I want to be able to easily select English for any new comment). Or at least a setting for a default language for new comments.
127
 
 

Thank you for your work on this platform, @nutomic@lemmy.ml

128
 
 

Trying to do it more now

129
 
 

Is it possible to migrate my account or should I just link it in the new one? I’m worried about the .zip in lemmy.zip and would like to bite the bullet and change over to another instance.

130
60
submitted 1 year ago* (last edited 8 months ago) by morrowind@lemmy.ml to c/lemmy@lemmy.ml
 
 
131
 
 

Title ... I posted about this previously here (https://lemmy.ml/post/10395138).

The community "tenforward" on lemmy.world seems to have ceased federating around 5 days ago (which could be in line with the 19.2 update on lemmy.ml?).

No posts are coming through onto lemmy.ml (and yes I subscribed well before this).

Here's the lemmy.ml mirror: https://lemmy.ml/c/tenforward@lemmy.world?dataType=Post&sort=New

... and the lemmy.world "home": https://lemmy.world/c/tenforward?dataType=Post&page=1&sort=New

For comparison, here is the lemm.ee mirror, which is also on 19.2 and seems to be receiving posts just fine: https://lemm.ee/c/tenforward@lemmy.world?dataType=Post&sort=New

If it's relevant, comments are federating back to lemmy.world. I tried commenting on one of the (older) posts from lemmy.ml and it federated over to lemmy.world fine (here's the lemmy.world mirror of the comment: https://lemmy.world/comment/6699443). I haven't tried posts because they might be annoying.

Seems to be weird but drastic bug. Could be a weird edge case that was arbitrarily triggered by the looks of it?

EDIT (further information)

As a point of comparison, here's a random community on lemmy.world I found (which I think is new as I sorted by New in the community search) which is federating fine with lemmy.ml: https://lemmy.ml/c/noshitsherlock@lemmy.world

Additionally, regarding the test comment I mentioned above, subsequent replies have since flowed through to lemmy.ml just fine: https://lemmy.ml/comment/7387000

... and mirrored accurately on lemmy.world too: https://lemmy.world/comment/6699443

132
207
submitted 1 year ago* (last edited 1 year ago) by fievel@lemm.ee to c/lemmy@lemmy.ml
 
 

Number of (active) Lemmy users seems to stabilize and I think this is a great thing. Indeed we got a lot of users when reddit shutdown its API (I was among them despite being a long time oss user), many have left, but the community seems now to stabilize to ~ ½ of the big grow in june '23. I think this is very nice for lemmy, we can be proud of this project.

The stats come from: https://fedidb.org/software/lemmy

133
 
 

I think spotted an example of federation failing between lemmy.ml, even after the update to 19.2, and Lemmy.world, which is still on 18.5.

If you look at the TenForward community on lemmy.ml (https://lemmy.ml/c/tenforward@lemmy.world?dataType=Post&sort=New) and compare to its lemmy.world version (which is its home) (https://lemmy.world/c/tenforward) … you’ll see lemmy.ml is behind about 2 days.

Haven’t seen any other examples like this, even from lemmy.world though I haven’t gone looking for them either.

134
 
 

cross-posted from: https://lemmy.ml/post/10364367

What is Lemmy?

Lemmy is a self-hosted social link aggregation and discussion platform. It is completely free and open, and not controlled by any company. This means that there is no advertising, tracking, or secret algorithms. Content is organized into communities, so it is easy to subscribe to topics that you are interested in, and ignore others. Voting is used to bring the most interesting items to the top.

Major Changes

  • Outgoing federation bug fixes.
  • Lemmy can now receive reports sent from Mastodon and Kbin.
  • Added the ability for admins to view votes, to prevent downvote trolling. Demo. #4088
  • Various bug fixes and minor enhancements.

Upgrade instructions

Follow the upgrade instructions for ansible or docker.

If you need help with the upgrade, you can ask in our support forum or on the Matrix Chat.

Thanks to everyone

We'd like to thank our many contributors and users of Lemmy for coding, translating, testing, and helping find and fix bugs. We're glad many people find it useful and enjoyable enough to contribute.

Support development

We (@dessalines and @nutomic) have been working full-time on Lemmy for over three years. This is largely thanks to support from NLnet foundation, as well as donations from individual users.

If you like using Lemmy, and want to make sure that we will always be available to work full time building it, consider donating to support its development. A recurring donation is the best way to ensure that open-source software like Lemmy can stay independent and alive.

135
 
 

I'm curious, if I'm subscribed to a community on an instance, why doesn't Lemmy "unlock" all of the communities on said instance. I've found that despite being subscribed to a few on an instance, my instance seems ignorant of other stuff happening on the instance.

136
 
 

Didn't actually know where to post it otherwise. Spelling is almost correct...

137
138
 
 

Finished up a recap site for lemmy similar to the recaps other sites like spotify, etc. have been doing!

Shows things like how many posts youve made, how many comments, your top posts of the year, the top communities you participate in, etc.

Theres a little role it assigns you and an image at the bottom that can be easily shared into the thread

139
 
 

I always think of small communities id like to be a part of, but can never find any. Reddit had (has) the same issue, leading people to create subreddits around the idea of helping others find communities to fit their interests. Idk thought it would be cool but I don't have the capabilities to do it myself.

140
 
 

Been moving from Reddit to Lemmy slowly so far and now I wanted to bring some of the communities I moderated there to here, as a huge car enthusiast I wanted to not only bring car related subs to communities here on lemmy.world, I also wanted to mod the "cars" community from the instance on lemmy.world already but I realized the moderator there has been inactive for several months now.

It looks like that community is a lost case and this is concerning, how many more communities are stuck like this? This should have been really affecting Lemmy badly thus far and it seems many power mods came in and claimed multiple community names when the blackout happened without actually committing to the platform.

I really hope the developers find a solution to this, so that those like me who actually wants to commit and moderate can do so.

141
 
 

I've found the following work-around works pretty well. If you host an instance that's currently on 0.19.0 or 0.19.1, consider implementing this.

There are two bugs that this helps with:

Work-around:
Create cronjobs that restart the Lemmy container every 6 hours (but not at midnight). The following example is used for a Debian system running Lemmy in Docker.

Type crontab -e into the terminal Add something like the following:

~~0 1 * * * docker container restart lemmy-lemmy-1
0 7 * * * docker container restart lemmy-lemmy-1
0 13 * * * docker container restart lemmy-lemmy-1
0 19 * * * docker container restart lemmy-lemmy-1~~

3 1-23/6 * * * docker container restart lemmy-postgres-1 && sleep 60 && docker container restart lemmy-lemmy-1

By restarting the container every 6 hours, outbound federation continues to work. There may still be some delays, but everything gets cleared up regularly.

By telling it what time to restart (0100, 0700, 1300, and 1900 as opposed to "every 6 hours"), it avoids restarting at midnight. This avoids the second bug.

My instance has been doing this for enough days where I'm confident that it's working. You can check your federation status here. Note that it's normal for there to be 0 up-to-date instances and a lot of lagging instances. As long as they sometimes turn "up to date", then everything is getting caught up.

142
 
 

"Copie Publique" grant program for FLOSS: €3000 grant to support Lemmy

French worker-owned company @codelutin invest 3333 € to support the #threadiverse development. 3000 € will go to Lemmy while 333 € will go to #kbin.

@copiepublique is a french alliance of companies who pledged to support FLOSS via profit-sharing. If you are a french company, join the alliance! ✊

@lemmy

143
 
 

cross-posted from: https://lemmy.ml/post/9559890

What is Lemmy?

Lemmy is a self-hosted social link aggregation and discussion platform. It is completely free and open, and not controlled by any company. This means that there is no advertising, tracking, or secret algorithms. Content is organized into communities, so it is easy to subscribe to topics that you are interested in, and ignore others. Voting is used to bring the most interesting items to the top.

Major Changes

0.19.0 has a critical bug where sending outgoing activities can stop working. The bug is fixed in this version. It also fixes the "hide read posts" user setting, fixes a problem with invalid comment paths, and another fix for private message reports.

Upgrade instructions

Follow the upgrade instructions for ansible or docker. The upgrade should take less than 30 minutes.

If you need help with the upgrade, you can ask in our support forum or on the Matrix Chat.

Thanks to everyone

We'd like to thank our many contributors and users of Lemmy for coding, translating, testing, and helping find and fix bugs. We're glad many people find it useful and enjoyable enough to contribute.

Support development

We (@dessalines and @nutomic) have been working full-time on Lemmy for over three years. This is largely thanks to support from NLnet foundation, as well as donations from individual users.

This month we are running a funding drive with the goal of increasing recurring donations from currently €4.000 to at least €12.000. With this amount @dessalines and @nutomic can each receive a yearly salary of €50.000 which is in line with median developer salaries. It will also allow one additional developer to work fulltime on Lemmy and speed up development.

Read more details in the funding drive announcement.

144
 
 

With debate raging in the Fedi about Threads' federation, I was having a discussion with another user about the recently implemented instance blocks. They pointed out that, blocking an instance simply hides their content from your feed but doesn't prevent your posts from being sent to them. Firstly, is this correct? Is this how instance blocks are implemented in Lemmy? If not, has this been discussed before? I couldn't find such a discussion in Github issues...

It seems that many people have concerns about Meta's use of their data, and would like to opt out of sharing their content with Threads. Is there any way to do this in Lemmy right now, or any plan to implement such a feature?

145
 
 

cross-posted from: https://lemmy.ml/post/9347983

Make sure you subscribe to !announcements@lemmy.ml

What is Lemmy?

Lemmy is a self-hosted social link aggregation and discussion platform. It is completely free and open, and not controlled by any company. This means that there is no advertising, tracking, or secret algorithms. Content is organized into communities, so it is easy to subscribe to topics that you are interested in, and ignore others. Voting is used to bring the most interesting items to the top.

Major Changes

This release is very large with almost 400 commits since 0.18.5. As such we can only give a general overview of the major changes in this post, and without going into detail. For more information, read the full changelog and linked issues at the bottom of this post.

Improved Post Ranking

There is a new scaled sort which takes into account the number of active users in a community, and boosts posts from less-active communities to the top. Additionally there is a new controversial sort which brings posts and comments to the top that have similar amounts of upvotes and downvotes. Lemmy's sorts are detailed here.

Instance Blocks for Users

Users can now block instances. Similar to community blocks, it means that any posts from communities which are hosted on that instance are hidden. However the block doesn't affect users from the blocked instance, their posts and comments can still be seen normally in other communities.

Two-Factor-Auth Rework

Previously 2FA was enabled in a single step which made it easy to lock yourself out. This is now fixed by using a two-step process, where the secret is generated first, and then 2FA is enabled by entering a valid 2FA token. It also fixes the problem where 2FA can be disabled without passing any 2FA token. As part of this change, 2FA is disabled for all users. This allows users who are locked out to get into their account again.

New Federation Queue

Outgoing federation actions are processed through a new persistent queue. This means that actions don't get lost if Lemmy is restarted. It is also much more performant, with separate senders for each target instance. This avoids problems when instances are unreachable. Additionally it supports horizontal scaling across different servers. The endpoint /api/v3/federated_instances contains details about federation state of each remote instance.

Remote Follow

Another new feature is support for remote follow. When browsing another instance where you don't have an account, you can click the subscribe button and enter the domain of your home instance in the popup dialog. It will automatically redirect you to your home instance where it fetches the community and presents a subscribe button. Here is a video showing how it works.

Authentication via Header or Cookie

Previous Lemmy versions used to send authentication tokens as part of the parameters. This was a leftover from websocket, which doesn't have any separate fields for this purpose. Now that we are using HTTP, authentication can finally be passed via jwt cookie or via header Authorization: Bearer . The old authentication method is not supported anymore to simplify maintenance. A major benefit of this change is that Lemmy can now send cache-control headers depending on authentication state. API responses with login have cache-control: private, those without have cache-control: public, max-age=60. This means that responses can be cached in Nginx which reduces server load.

Moderation

Reports are now resolved automatically when the associated post/comment is marked as deleted. This reduces the amount of work for moderators. There is a new log for image uploads which stores uploader. For now it is used to delete all user uploads when an account is purged. Later the list can be used for other purposes and made available through the API.

Cursor based pagination

0.19 adds support for cursor based pagination on the /api/v3/post/list endpoint. This is more efficient for the database. Instead of a query parameter ?page=3, listing responses now include a field "next_page": "Pa46c" which needs to be passed as ?page_cursor=Pa46c. The existing pagination method is still supported for backwards compatibility, but will be removed in the next version.

User data export/import

Users can now export their data (community follows, blocklists, profile settings), and import it again on another instance. This can be used for account migrations and also as a form of backup. The export format is designed to remain unchanged for a long time. You can make regular exports, and if the instance becomes unavailable, register a new account and import the data. This way you can continue using Lemmy seamlessly.

Time zone handling

Lemmy didn't have any support for timezones, which led to bugs when federating with other platforms. This is now fixed by using UTC timezone for all timestamps.

ARM64 Support

Thanks to help from @raskyld and @kroese, there are now offical Lemmy releases for ARM64 available.

Activity now includes voters

Upgrade instructions

Follow the upgrade instructions for ansible or docker. The upgrade should take less than 30 minutes.

If you need help with the upgrade, you can ask in our support forum or on the Matrix Chat.

Pict-rs 0.5 is also close to releasing. The upgrade takes a while due to a database migration, so read the migration guide to speed it up. Note that Lemmy 0.19 still works perfectly with pict-rs 0.4.

Thanks to everyone

We'd like to thank our many contributors and users of Lemmy for coding, translating, testing, and helping find and fix bugs. We're glad many people find it useful and enjoyable enough to contribute.

Support development

We (@dessalines and @nutomic) have been working full-time on Lemmy for over three years. This is largely thanks to support from NLnet foundation, as well as donations from individual users.

This month we are running a funding drive with the goal of increasing recurring donations from currently €4.000 to at least €12.000. With this amount @dessalines and @nutomic can each receive a yearly salary of €50.000 which is in line with median developer salaries. It will also allow one additional developer to work fulltime on Lemmy and speed up development.

Read more details in the funding drive announcement.

146
 
 

cross-posted from: https://lemmy.ml/post/9347983

What is Lemmy?

Lemmy is a self-hosted social link aggregation and discussion platform. It is completely free and open, and not controlled by any company. This means that there is no advertising, tracking, or secret algorithms. Content is organized into communities, so it is easy to subscribe to topics that you are interested in, and ignore others. Voting is used to bring the most interesting items to the top.

Major Changes

This release is very large with almost 400 commits since 0.18.5. As such we can only give a general overview of the major changes in this post, and without going into detail. For more information, read the full changelog and linked issues at the bottom of this post.

Improved Post Ranking

There is a new scaled sort which takes into account the number of active users in a community, and boosts posts from less-active communities to the top. Additionally there is a new controversial sort which brings posts and comments to the top that have similar amounts of upvotes and downvotes. Lemmy's sorts are detailed here.

Instance Blocks for Users

Users can now block instances. Similar to community blocks, it means that any posts from communities which are hosted on that instance are hidden. However the block doesn't affect users from the blocked instance, their posts and comments can still be seen normally in other communities.

Two-Factor-Auth Rework

Previously 2FA was enabled in a single step which made it easy to lock yourself out. This is now fixed by using a two-step process, where the secret is generated first, and then 2FA is enabled by entering a valid 2FA token. It also fixes the problem where 2FA can be disabled without passing any 2FA token. As part of this change, 2FA is disabled for all users. This allows users who are locked out to get into their account again.

New Federation Queue

Outgoing federation actions are processed through a new persistent queue. This means that actions don't get lost if Lemmy is restarted. It is also much more performant, with separate senders for each target instance. This avoids problems when instances are unreachable. Additionally it supports horizontal scaling across different servers. The endpoint /api/v3/federated_instances contains details about federation state of each remote instance.

Remote Follow

Another new feature is support for remote follow. When browsing another instance where you don't have an account, you can click the subscribe button and enter the domain of your home instance in the popup dialog. It will automatically redirect you to your home instance where it fetches the community and presents a subscribe button. Here is a video showing how it works.

Authentication via Header or Cookie

Previous Lemmy versions used to send authentication tokens as part of the parameters. This was a leftover from websocket, which doesn't have any separate fields for this purpose. Now that we are using HTTP, authentication can finally be passed via jwt cookie or via header Authorization: Bearer <jwt>. The old authentication method is not supported anymore to simplify maintenance. A major benefit of this change is that Lemmy can now send cache-control headers depending on authentication state. API responses with login have cache-control: private, those without have cache-control: public, max-age=60. This means that responses can be cached in Nginx which reduces server load.

Moderation

Reports are now resolved automatically when the associated post/comment is marked as deleted. This reduces the amount of work for moderators. There is a new log for image uploads which stores uploader. For now it is used to delete all user uploads when an account is purged. Later the list can be used for other purposes and made available through the API.

Cursor based pagination

0.19 adds support for cursor based pagination on the /api/v3/post/list endpoint. This is more efficient for the database. Instead of a query parameter ?page=3, listing responses now include a field "next_page": "Pa46c" which needs to be passed as ?page_cursor=Pa46c. The existing pagination method is still supported for backwards compatibility, but will be removed in the next version.

User data export/import

Users can now export their data (community follows, blocklists, profile settings), and import it again on another instance. This can be used for account migrations and also as a form of backup. The export format is designed to remain unchanged for a long time. You can make regular exports, and if the instance becomes unavailable, register a new account and import the data. This way you can continue using Lemmy seamlessly.

Time zone handling

Lemmy didn't have any support for timezones, which led to bugs when federating with other platforms. This is now fixed by using UTC timezone for all timestamps.

ARM64 Support

Thanks to help from @raskyld and @kroese, there are now offical Lemmy releases for ARM64 available.

Activity now includes voters

Upgrade instructions

Follow the upgrade instructions for ansible or docker. The upgrade should take less than 30 minutes.

If you need help with the upgrade, you can ask in our support forum or on the Matrix Chat.

Pict-rs 0.5 is also close to releasing. The upgrade takes a while due to a database migration, so read the migration guide to speed it up. Note that Lemmy 0.19 still works perfectly with pict-rs 0.4.

Thanks to everyone

We'd like to thank our many contributors and users of Lemmy for coding, translating, testing, and helping find and fix bugs. We're glad many people find it useful and enjoyable enough to contribute.

Support development

We (@dessalines and @nutomic) have been working full-time on Lemmy for over three years. This is largely thanks to support from NLnet foundation, as well as donations from individual users.

This month we are running a funding drive with the goal of increasing recurring donations from currently €4.000 to at least €12.000. With this amount @dessalines and @nutomic can each receive a yearly salary of €50.000 which is in line with median developer salaries. It will also allow one additional developer to work fulltime on Lemmy and speed up development.

Read more details in the funding drive announcement.

147
 
 

On Reddit, when a comment is removed or deleted, it still shows up in the comment count. You will see an interesting post with comments, but when you open it you'll see that it's actually empty. This is probably done for shadowban reasons, like the vote fuzzing in the other post?

On Lemmy the count gets updated. I like that

148
 
 

So I’m developing a mobile client using React Native, where I’m utilizing Lemmy’s messaging functionality as well. This makes it extremely crucial to have notification support (including push notifications).

How are you guys dealing with this problem? This is what I think an elegant solution could look like. We would need to achieve two things:

  1. Bring back websockets only for notifications by directly changing lemmy server side code.
  2. Find where the email notification code is at, and simply implement expo notifications there.

Whaddya think?

149
 
 

When making a post on Lemmy, it automatically does searches for similar existing posts. On Reddit you often have the issue of people asking the same questions over and over, this feature should definitely help reduce that!

150
 
 

We can follow lemmy accounts from Mastodon but I was wondering if we can do it the other way round?

I tried searching the username of some Masodon accounts into the search bar on Lemmy and nothing came up but when I search up the username of any Lemmy account, they do show up.

So, I'm guessing it's not yet possible?

view more: ‹ prev next ›