0

Want to support but dont have a credit card

preview

Hey is there any possibility to support you without using cerdit card as I dont have one. Due to happy circumstances I have a little more disposable income and y’all are doing great stuff I can do normal wire transfer from Germany or PP

Hey is there any possibility to support you without using cerdit card as I dont have one. Due to happy circumstances I have a little more disposable income and y’all are doing great stuff I can do normal wire transfer from Germany or PP

0

Can't update profile picture

preview

When I try to upload a picture for my profile picture I get a generic 400 error. When I try to do it through the web interface I get an even more generic “error.[object Object]” message.

When I try to upload a picture for my profile picture I get a generic 400 error. When I try to do it through the web interface I get an even more generic “error.[object Object]” message.

0

How do I reset my password?

preview

When I go to reset my password, it asks me to put my email in, then sends me a password reset email. But when I click the link it always brings me to the “pick your interface” landing page, which then forwards me to the front page every time rather than a password reset page.

When I go to reset my password, it asks me to put my email in, then sends me a password reset email. But when I click the link it always brings me to the “pick your interface” landing page, which then forwards me to the front page every time rather than a password reset page.

0

Unable to login to piefed.blahaj.zone

preview

Since this morning (2026-10-24 Stockholm/Europe), I haven’t been able to login to piefed.blahaj.zone . I have tried from my home network, from mobile network, with and without VPN, with and without the eMudhra certificates enabled (considering the recent shenanigans).

The login page in the picture shows up every now and then, but it takes a ridiculously long time (15 or so minutes?).

Is something going on?

Since this morning (2026-10-24 Stockholm/Europe), I haven’t been able to login to piefed.blahaj.zone . I have tried from my home network, from mobile network, with and without VPN, with and without the eMudhra certificates enabled (considering the recent shenanigans).

The login page in the picture shows up every now and then, but it takes a ridiculously long time (15 or so minutes?).

Is something going on?

0

Can't upload media

preview

I’m trying to upload a 140KB jpg for a post but keep getting the error

{“data”:{“files”:null,“msg”:“No space left on device (os error 28)”},“state”:“success”}

I’m trying to upload a 140KB jpg for a post but keep getting the error

{“data”:{“files”:null,“msg”:“No space left on device (os error 28)”},“state”:“success”}

0

The Blahaj Moderation Team is Not as Inclusive as They Claim to Be

preview

A lot of events have transpired on the matrix space. Plural beings, the unpronouned, and trauma suvivors have all felt unsafe in that space.

The mods are negligent and rarely interact with the community, and tend to mod and do desicions from “high seats” without context or discussion.

All descisions seem to also be hushy hush and made in secret

More details on Chattin’, the main room of the matrix space. If our accounts get suspeneded, contact @reilyh:matrix.org


Please read our pronouns before addressing us

A lot of events have transpired on the matrix space. Plural beings, the unpronouned, and trauma suvivors have all felt unsafe in that space.

The mods are negligent and rarely interact with the community, and tend to mod and do desicions from “high seats” without context or discussion.

All descisions seem to also be hushy hush and made in secret

More details on Chattin’, the main room of the matrix space. If our accounts get suspeneded, contact @reilyh:matrix.org


Please read our pronouns before addressing us

0

Image comments on Lemmy blahaj but not piefed? Works on other piefeds

preview

When i try to paste an image into a piefed comment on blorp, i get a http 400 error (bad request)

I can post the same image into a lemmy comment and it works fine.

Is this a intended behavior, a problem with piefed, or a problem with blorp?

One wrinkle, i can usually copy entire articles, including images, and paste these as comments in piefed. Turns out i was misremembering and this still fails. Actually it did work once with the Wikipedia fediverse article, but failed the lego 404 article.

I will post some test comments below from piefed blahaj, Lemmy blahaj, and retrofed (piefed).

Please let me know if you have any insights or anything else to try.

NEW INFO: testing on Summt vs Blorp reveals: quota exceeded.

When i try to paste an image into a piefed comment on blorp, i get a http 400 error (bad request)

I can post the same image into a lemmy comment and it works fine.

Is this a intended behavior, a problem with piefed, or a problem with blorp?

One wrinkle, i can usually copy entire articles, including images, and paste these as comments in piefed. Turns out i was misremembering and this still fails. Actually it did work once with the Wikipedia fediverse article, but failed the lego 404 article.

I will post some test comments below from piefed blahaj, Lemmy blahaj, and retrofed (piefed).

Please let me know if you have any insights or anything else to try.

NEW INFO: testing on Summt vs Blorp reveals: quota exceeded.

0

Federation trouble? Help requested. Blocking

preview

Hello, I’m not seeing OP’s responses on a thread, but i can see them in an alt piefed.blahaj.zone account.

But i realized it was because i have blocked OP previously.

So my question is, if I have blocked them, why can i read their post? Is there something wrong with my account?

I suppose the first troubleshooting step is to find a desktop computer and see if using a different client other than Blorp is any different?

Anyone have insight into what is going on? Thank you

Hello, I’m not seeing OP’s responses on a thread, but i can see them in an alt piefed.blahaj.zone account.

But i realized it was because i have blocked OP previously.

So my question is, if I have blocked them, why can i read their post? Is there something wrong with my account?

I suppose the first troubleshooting step is to find a desktop computer and see if using a different client other than Blorp is any different?

Anyone have insight into what is going on? Thank you

0

Login on Desktop

preview

When I visit lemmy.blåhaj.zone I am asked to select an interface, but clicking ‘once’ or ‘always’ for any interface has zero effect. It is as if the buttons have stopped working.

Is there a workaround or fix?

I tried unsuccessfully with and without adblocker. Any ideas what might be interfering?

When I visit lemmy.blåhaj.zone I am asked to select an interface, but clicking ‘once’ or ‘always’ for any interface has zero effect. It is as if the buttons have stopped working.

Is there a workaround or fix?

I tried unsuccessfully with and without adblocker. Any ideas what might be interfering?

0

Server issue, double posting and phantom error messages

preview

Is this the place to report server issues or is somewhere else better?

I just now tried to post a comment on transjoy, it gave an error message. I retried and it worked. However, the comment posted twice. I can only assume the first error message was given in error.

I assume the same thing happened to someone else this morning. A double post on transjoy with an apperant error on the first attempt.

I’m having a similar issue when loading comment threads, error first attempt, works the second time. I think they might be related. Tested when logged in on jerboa and alexandrite. I get the following errors upon loading a comment thread:

Lemmy Error: couldn't_mark_post_as_read (status 400)

Lemmy Error: Couldn't find post (status 400) 

Then it works on the second attempt. I’ve not been able to reproduce the issue when logged out.

First attempt at posting: “couldn’t_like_post”

Edit: second time success

Edit 2: no errors during edits

Edit 3: first attempt did post despite error message. I deleted the initial post and then got an error posting this edit.

Is this the place to report server issues or is somewhere else better?

I just now tried to post a comment on transjoy, it gave an error message. I retried and it worked. However, the comment posted twice. I can only assume the first error message was given in error.

I assume the same thing happened to someone else this morning. A double post on transjoy with an apperant error on the first attempt.

I’m having a similar issue when loading comment threads, error first attempt, works the second time. I think they might be related. Tested when logged in on jerboa and alexandrite. I get the following errors upon loading a comment thread:

Lemmy Error: couldn't_mark_post_as_read (status 400)

Lemmy Error: Couldn't find post (status 400) 

Then it works on the second attempt. I’ve not been able to reproduce the issue when logged out.

First attempt at posting: “couldn’t_like_post”

Edit: second time success

Edit 2: no errors during edits

Edit 3: first attempt did post despite error message. I deleted the initial post and then got an error posting this edit.

0

Lemmy Release v0.19.20 - Reduced Memory Usage

preview

cross-posted from: lemmy.ml/post/50346212

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.

Changes

This release significantly reduces memory usage for the Lemmy backend. Metrics on production instances show a reduction up to 10 times. Here you can see the statistics from a few different instances. Read on for a technical explanation below. Note that the change only affects x86, there is no difference on ARM (e.g. Raspberry Pi), see here for details.

lemmy.ml (overall RAM usage including OS, Docker, PostgreSQL etc):

leminal.space (backend container only)

lemmy.world (backend API containers)

lemmy.world (backend federation and scheduled tasks)

How was such a major improvement possible? Memory usage in languages like Rust or C is managed by a so-called memory allocator. It requests large chunks of RAM from the operating system, and provides smaller chunks when needed in the program. For example, every string (such as post titles or markdown text) require chunks of memory to store them. When processing the data is completed, the memory should be freed and released, or reused.

Until version 0.19.19 Lemmy used the mimalloc memory allocator, which is supposedly better than the default glibc allocator. Yet a recent blog post points out that mimalloc does not play well with the tokio async runtime. It suggests to use jemalloc instead. Changing memory allocators is very simple in Rust, it only requires a single line of code. So we tried that, deployed the change on lemmy.ml and it immediately proved effective.

Upgrade instructions

There are no breaking changes with this release.

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 five 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, and helps us grow our little developer co-op to support more full-time developers.

cross-posted from: lemmy.ml/post/50346212

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.

Changes

This release significantly reduces memory usage for the Lemmy backend. Metrics on production instances show a reduction up to 10 times. Here you can see the statistics from a few different instances. Read on for a technical explanation below. Note that the change only affects x86, there is no difference on ARM (e.g. Raspberry Pi), see here for details.

lemmy.ml (overall RAM usage including OS, Docker, PostgreSQL etc):

leminal.space (backend container only)

lemmy.world (backend API containers)

lemmy.world (backend federation and scheduled tasks)

How was such a major improvement possible? Memory usage in languages like Rust or C is managed by a so-called memory allocator. It requests large chunks of RAM from the operating system, and provides smaller chunks when needed in the program. For example, every string (such as post titles or markdown text) require chunks of memory to store them. When processing the data is completed, the memory should be freed and released, or reused.

Until version 0.19.19 Lemmy used the mimalloc memory allocator, which is supposedly better than the default glibc allocator. Yet a recent blog post points out that mimalloc does not play well with the tokio async runtime. It suggests to use jemalloc instead. Changing memory allocators is very simple in Rust, it only requires a single line of code. So we tried that, deployed the change on lemmy.ml and it immediately proved effective.

Upgrade instructions

There are no breaking changes with this release.

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 five 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, and helps us grow our little developer co-op to support more full-time developers.

0

The Tesseract lemmy front end has been removed from blahaj.zone

preview

In light of the dev silently blacklisting blahaj.zone, many of its users and several other instances, we have removed tesseract from the available lemmy front ends we offer.

In light of the dev silently blacklisting blahaj.zone, many of its users and several other instances, we have removed tesseract from the available lemmy front ends we offer.

0

Logging in on desktop: questions

preview

So I’m on my account and have no issues whilst logged in, but when I want to log in on desktop, I can’t change my password in case I forgot it. I use Voyager on mobile, which doesn’t let me change my password either ( @aeharding@vger.social ?).

I can’t add an email address either, since on Voyager that doesn’t seem possible. What do I do?

So I’m on my account and have no issues whilst logged in, but when I want to log in on desktop, I can’t change my password in case I forgot it. I use Voyager on mobile, which doesn’t let me change my password either ( @aeharding@vger.social ?).

I can’t add an email address either, since on Voyager that doesn’t seem possible. What do I do?

0

Federation issues?

preview

I was browsing 196 recently and I noticed that stuff between slrpnk and blahaj weren’t federating between the 2 properly.

From slrpnk (another lemmy instance) there looks like there hasn’t been a post in 196 since yesterday but checking from blahaj it’s as alive as always.

I then checked from lemmy.world, beehaw, sopuli.xyz, and lemmy.zip to see if it was just an issue with slrpnk but it appears to be widespread as all of those other instances have the same issue.

Hopefully me making a post here isn’t an issue (and that it federates properly) but I figured reporting a bug wouldn’t be an issue.

I was browsing 196 recently and I noticed that stuff between slrpnk and blahaj weren’t federating between the 2 properly.

From slrpnk (another lemmy instance) there looks like there hasn’t been a post in 196 since yesterday but checking from blahaj it’s as alive as always.

I then checked from lemmy.world, beehaw, sopuli.xyz, and lemmy.zip to see if it was just an issue with slrpnk but it appears to be widespread as all of those other instances have the same issue.

Hopefully me making a post here isn’t an issue (and that it federates properly) but I figured reporting a bug wouldn’t be an issue.

0

Shout out to the people who hacked blahaj and reminded me to subscribe to their KoFi

preview

Sorry if this isn’t allowed/in the wrong place, but I wanted it to have a little visibility in case others found themselves in a position to chip in. Recovering from a breach is painful and soaks up resources that could be used elsewhere.

I mostly lurk and read Blahaj from a different instance, but when I saw the hacked announcement it reminded me what a great resource and community is here and I figured now would be a good time as any to let the Admins know I appreciate their efforts!

Link to their kofi: ko-fi.com/blahajzone (but to be security conscious, you shouldn’t click that, you should really go get the link from their sidebar :) ).

Sorry if this isn’t allowed/in the wrong place, but I wanted it to have a little visibility in case others found themselves in a position to chip in. Recovering from a breach is painful and soaks up resources that could be used elsewhere.

I mostly lurk and read Blahaj from a different instance, but when I saw the hacked announcement it reminded me what a great resource and community is here and I figured now would be a good time as any to let the Admins know I appreciate their efforts!

Link to their kofi: ko-fi.com/blahajzone (but to be security conscious, you shouldn’t click that, you should really go get the link from their sidebar :) ).

0

Does Blåhaj use Cloudflare? If so, should we also shift to another?

preview

cross-posted from: lemmy.ca/post/66634564

Cloudflare: Why I left lemmy.world to join another instance

Sad to see. We should all know cloudlfare decrypts our data before it reaches the service it protects. A perfect surveillance man-in-the-middle.

I was happy to find a home in the fediverse that uses Anubis instead.

anubis.techaro.lol

cross-posted from: lemmy.ca/post/66634564

Cloudflare: Why I left lemmy.world to join another instance

Sad to see. We should all know cloudlfare decrypts our data before it reaches the service it protects. A perfect surveillance man-in-the-middle.

I was happy to find a home in the fediverse that uses Anubis instead.

anubis.techaro.lol

0

Lemmy Release v0.19.19

preview

This version again includes a couple of security fixes. Thanks to the people who found and reported them!

The first one in particular requires manual action from instance admins. Lemmy’s default Nginx config uses $proxy_add_x_forwarded_for to set the X-Forwarded-For header, which does not override existing values. So clients can spoof the IP and bypass rate limits. The solution is to use $remote_addr instead. If you use Ansible this will be changed automatically during the upgrade, otherwise you will need to do it manually. If you dont use Nginx, ensure that any X-Forwarded-For headers sent by the client are overwritten.

The remaining security vulnerabilities are in the Lemmy code itself, and will be fixed simply by upgrading.

Security:

This version again includes a couple of security fixes. Thanks to the people who found and reported them!

The first one in particular requires manual action from instance admins. Lemmy’s default Nginx config uses $proxy_add_x_forwarded_for to set the X-Forwarded-For header, which does not override existing values. So clients can spoof the IP and bypass rate limits. The solution is to use $remote_addr instead. If you use Ansible this will be changed automatically during the upgrade, otherwise you will need to do it manually. If you dont use Nginx, ensure that any X-Forwarded-For headers sent by the client are overwritten.

The remaining security vulnerabilities are in the Lemmy code itself, and will be fixed simply by upgrading.

Security:

0

Blahaj zone hacked

preview

Firstly, apologies to everyone for the extended downtime. Unfortunately, it was for a pretty bad reason. We were hacked.

The bad news is that it was a comprehensive attack, and the attackers had privileged access to our database system, across all of our services (except for writefreely, which doesn’t use postgres). From what we can tell, the attacker did not do anything with that access, so we don’t believe any user data was accessed, but we can’t be certain of that. For lemmy, the impact of this should be minimal. If you registered with a real email address, they may have that. User passwords are encrypted in the database, so if you were using a secure, non trivial password, it should be safe, but you should still change it. You should also reset your 2 factor authentication if you had it enabled, as the seeds for these are not encrypted.

Our understanding is that the attacker used a peertube exploit, then a postgres exploit and then a kernel exploit to systematically gain access to different layers of our database server. A side effect of the hack was that it filled up our database servers hard drive, and caused it to fail over to our backup, which we believe mitigated some of the potential fall out.

We have had to reset activitypub keypairs for every account and community on lemmy, so there may be some federation hicoughs for a day or so, until remote servers have dropped any cached copies of our users public keys. This is uncharted territory though, so hopefully it’s as smooth as we think it will be, but we can’t be sure!

As stated earlier, our writefreely instance is still up and running as it wasn’t impacted by this attack. Vernissage (our pixelfed replacement) has been brought back online, as has our matrix server.

We will be bringing up Sharkey, and then Piefed hopefully later today, but we have to rotate keypairs on those services too, which is also uncharted territory, so the timelines are hopes, not guarantees. At this point in time, we don’t plan on bringing pixelfed back online, as it was slated for shutdown in August in any case. If people still need access to pixelfed to export data, we can spin it up briefly if needed, so please reach out if this is you. We also won’t be bringing peertube back up at this point. It was not heavily utilised, and it was the source of the attack, so Kaity is a bit gun shy about spinning it back up on shared database infrastructure. If there is a strong desire to bring peertube back, we can consider doing that on isolated hardware, but at the current utilisation level, it doesn’t seem worth the cost/effort to run it isolated.

in any case, you can read a fuller explanation of the attack by Kaity here pen.blahaj.zone/supakaity/weve-been-hacked

Edit - Piefed is back now!

Firstly, apologies to everyone for the extended downtime. Unfortunately, it was for a pretty bad reason. We were hacked.

The bad news is that it was a comprehensive attack, and the attackers had privileged access to our database system, across all of our services (except for writefreely, which doesn’t use postgres). From what we can tell, the attacker did not do anything with that access, so we don’t believe any user data was accessed, but we can’t be certain of that. For lemmy, the impact of this should be minimal. If you registered with a real email address, they may have that. User passwords are encrypted in the database, so if you were using a secure, non trivial password, it should be safe, but you should still change it. You should also reset your 2 factor authentication if you had it enabled, as the seeds for these are not encrypted.

Our understanding is that the attacker used a peertube exploit, then a postgres exploit and then a kernel exploit to systematically gain access to different layers of our database server. A side effect of the hack was that it filled up our database servers hard drive, and caused it to fail over to our backup, which we believe mitigated some of the potential fall out.

We have had to reset activitypub keypairs for every account and community on lemmy, so there may be some federation hicoughs for a day or so, until remote servers have dropped any cached copies of our users public keys. This is uncharted territory though, so hopefully it’s as smooth as we think it will be, but we can’t be sure!

As stated earlier, our writefreely instance is still up and running as it wasn’t impacted by this attack. Vernissage (our pixelfed replacement) has been brought back online, as has our matrix server.

We will be bringing up Sharkey, and then Piefed hopefully later today, but we have to rotate keypairs on those services too, which is also uncharted territory, so the timelines are hopes, not guarantees. At this point in time, we don’t plan on bringing pixelfed back online, as it was slated for shutdown in August in any case. If people still need access to pixelfed to export data, we can spin it up briefly if needed, so please reach out if this is you. We also won’t be bringing peertube back up at this point. It was not heavily utilised, and it was the source of the attack, so Kaity is a bit gun shy about spinning it back up on shared database infrastructure. If there is a strong desire to bring peertube back, we can consider doing that on isolated hardware, but at the current utilisation level, it doesn’t seem worth the cost/effort to run it isolated.

in any case, you can read a fuller explanation of the attack by Kaity here pen.blahaj.zone/supakaity/weve-been-hacked

Edit - Piefed is back now!

0

[update: it's fixed now! thank you!] i can't update my settings in the default lemmy UI, and can't change my profile pic anywhere

preview

pressing “save” in my settings page does nothing, not even show a popup telling me something failed. it’s been that way for a few months at least, since april of this year i think.

i’ve tried modifying and saving my profile in other clients, and it seems to work there! i can change my bio and username without issues.

however, something i can’t do, in any client, is change my profile picture, which is unfortunate since mine has been broken* for some time. in the default lemmy ui, as i said, pressing the save button does nothing. however, i’ve also tried to change my profile picture in tesseract and blorp, and both complain about an invalid url when trying to save the profile pic. both can save other settings tho, and image upload works fine, as the images i try to set appear in my uploads tab. using the js console, i can see that changing the profile pic does a PUT https://lemmy.blahaj.zone/api/v3/user/save_user_settings request, which fails (error 400). trying to change the banner image has the same problem. this happens no matter the browser or device i try this on.

is this also a problem for other people?

* (i’ve since removed my profile pic in blorp, which is why i’ve got the default lemmy profile pic now instead of a broken image icon)

(i’m sorry if this kind of post is not allowed, if not i’ll delete no worries 😅)

pressing “save” in my settings page does nothing, not even show a popup telling me something failed. it’s been that way for a few months at least, since april of this year i think.

i’ve tried modifying and saving my profile in other clients, and it seems to work there! i can change my bio and username without issues.

however, something i can’t do, in any client, is change my profile picture, which is unfortunate since mine has been broken* for some time. in the default lemmy ui, as i said, pressing the save button does nothing. however, i’ve also tried to change my profile picture in tesseract and blorp, and both complain about an invalid url when trying to save the profile pic. both can save other settings tho, and image upload works fine, as the images i try to set appear in my uploads tab. using the js console, i can see that changing the profile pic does a PUT https://lemmy.blahaj.zone/api/v3/user/save_user_settings request, which fails (error 400). trying to change the banner image has the same problem. this happens no matter the browser or device i try this on.

is this also a problem for other people?

* (i’ve since removed my profile pic in blorp, which is why i’ve got the default lemmy profile pic now instead of a broken image icon)

(i’m sorry if this kind of post is not allowed, if not i’ll delete no worries 😅)

0

New Blahaj Photo Sharing instance

preview

We’ve just spun up a brand new photo sharing instance, based on Vernissage. It’s similar to pixelfed, but more focused on photography (as opposed to general image and short video sharing).

Signups are open. Currently, it mandates an email address, but you can stick whatever you like in there, and it will be automatically verified. Signups do require approval, but you can also generate invites that (I believe) bypass the requirement for approval.

Anyway, you can check it out at photos.blahaj.zone

As a consequence, we will be taking down our pixelfed instance. We’ll leave it up until the end of August to give people a chance to migrate, but honestly, it had really low activity in any case, so it shouldn’t have too much of an impact on people.

Vernissage may also end up having low activity, but even if it does, I like it so much more than pixelfed, that we’ll keep it running even if it’s just me using it :)

We’ve just spun up a brand new photo sharing instance, based on Vernissage. It’s similar to pixelfed, but more focused on photography (as opposed to general image and short video sharing).

Signups are open. Currently, it mandates an email address, but you can stick whatever you like in there, and it will be automatically verified. Signups do require approval, but you can also generate invites that (I believe) bypass the requirement for approval.

Anyway, you can check it out at photos.blahaj.zone

As a consequence, we will be taking down our pixelfed instance. We’ll leave it up until the end of August to give people a chance to migrate, but honestly, it had really low activity in any case, so it shouldn’t have too much of an impact on people.

Vernissage may also end up having low activity, but even if it does, I like it so much more than pixelfed, that we’ll keep it running even if it’s just me using it :)

0

Update: Now resolved - Blahaj Piefed Down for security maintenance

preview

Edit - Piefed has been updated and returned to service

Thanks to someone posting a piefed security exploit without a disclosure period, we’ve had to pull blahaj piefed down without warning until a fix is implemented. This could take around 24 hours or so.

Edit - Piefed has been updated and returned to service

Thanks to someone posting a piefed security exploit without a disclosure period, we’ve had to pull blahaj piefed down without warning until a fix is implemented. This could take around 24 hours or so.

0

Now Fixed - Blahaj.zone latency across all services

preview

Edit - We’re back!

We’ve had an issue with our databases. One of our fast database servers ran out of space, and then the second fast server ran out of space whilst replicating to the first.

As a result, we have fallen over to our backup database server, which runs on spinny disks rather than SSDs. Spinny disks means that it’s got plenty of space to spare, but it’s not fast. The backup DB server is currently replicating to our two main servers to get things back up and running again, but whilst that’s happening, all of our services are running slow.

The good news is, we’ll be back up and running as if nothing happened because our backup server saved the day. The bad news is, it may take another 24 hours or so, because the backup server is reliable but not fast!

Edit - We’re back!

We’ve had an issue with our databases. One of our fast database servers ran out of space, and then the second fast server ran out of space whilst replicating to the first.

As a result, we have fallen over to our backup database server, which runs on spinny disks rather than SSDs. Spinny disks means that it’s got plenty of space to spare, but it’s not fast. The backup DB server is currently replicating to our two main servers to get things back up and running again, but whilst that’s happening, all of our services are running slow.

The good news is, we’ll be back up and running as if nothing happened because our backup server saved the day. The bad news is, it may take another 24 hours or so, because the backup server is reliable but not fast!

0

Blåhaj often down

preview

According to lestat.org, the Blåhaj instance is down notably more often. What is happening or causing this?

Is it server costs? If so, I’m willing to contribute, but how should I do so? And if not, what would it be? Host issues? Targeted attacks, perhaps?

According to lestat.org, the Blåhaj instance is down notably more often. What is happening or causing this?

Is it server costs? If so, I’m willing to contribute, but how should I do so? And if not, what would it be? Host issues? Targeted attacks, perhaps?

0

Is anyone else experiencing federation issues with sh.itjust.works?

preview

Over the last several days, I’ve noticed significant delays with votes, comments, and notifications from that instance. The longest delay I’ve noticed was 2 days. Is this a known issue? Is anyone else experiencing this?

Over the last several days, I’ve noticed significant delays with votes, comments, and notifications from that instance. The longest delay I’ve noticed was 2 days. Is this a known issue? Is anyone else experiencing this?

0

Should we join the pledge to boycott lemmy.world?

preview

Context

TL;DR This is a pledge to defederate from lemmy.world if they end up defederating from any of the instances in the Fediverse Anarchist Flotilla (FAF), which consists of lemmy.dbzer0.com, anarchist.nexus, and quokk.au. Just want to see if the admins are aware of this situation, and see what others think.

Context

TL;DR This is a pledge to defederate from lemmy.world if they end up defederating from any of the instances in the Fediverse Anarchist Flotilla (FAF), which consists of lemmy.dbzer0.com, anarchist.nexus, and quokk.au. Just want to see if the admins are aware of this situation, and see what others think.

0

Lemmy Release v0.19.18 - 2 security fixes

preview

With this version user badges are always shown next to usernames. There are also various bug fixes, and again security fixes

  • Display UserBadges for Bot, Banned and Deleted users in all PersonListings by @MrKaplan-lw in #4035
  • Increase timeouts for db pool by @nutomic in #6441
  • Add private IP check for webmention by @nutomic in #6444
  • Proper fix for nested comment fetch by @nutomic in #6451

Security

  • Lemmy allows an authenticated low-privileged user to create a link post through POST /api/v3/post. When a post is created in a public community, the backend asynchronously sends a Webmention to the attacker-controlled link target. The submitted URL is checked for syntax and scheme, but the audited code path does not reject loopback, private, or link-local destinations before the Webmention request is issued. This lets a normal user trigger server-side HTTP requests toward internal services. github.com/LemmyNet/lemmy/…/GHSA-3jvj-v6w2-h948
  • Lemmy fetches metadata for user-supplied post URLs and, under the default StoreLinkPreviews image mode, downloads the preview image through local pict-rs. While the top-level page URL is checked against internal IP ranges, the extracted og:image URL is not subject to the same restriction. As a result, an authenticated low-privileged user can submit an attacker-controlled public page whose Open Graph image points to an internal image endpoint. Lemmy will fetch that internal image server-side and store a local thumbnail that can then be served back to users. github.com/LemmyNet/lemmy/…/GHSA-h6hf-9846-xwrq

With this version user badges are always shown next to usernames. There are also various bug fixes, and again security fixes

  • Display UserBadges for Bot, Banned and Deleted users in all PersonListings by @MrKaplan-lw in #4035
  • Increase timeouts for db pool by @nutomic in #6441
  • Add private IP check for webmention by @nutomic in #6444
  • Proper fix for nested comment fetch by @nutomic in #6451

Security

  • Lemmy allows an authenticated low-privileged user to create a link post through POST /api/v3/post. When a post is created in a public community, the backend asynchronously sends a Webmention to the attacker-controlled link target. The submitted URL is checked for syntax and scheme, but the audited code path does not reject loopback, private, or link-local destinations before the Webmention request is issued. This lets a normal user trigger server-side HTTP requests toward internal services. github.com/LemmyNet/lemmy/…/GHSA-3jvj-v6w2-h948
  • Lemmy fetches metadata for user-supplied post URLs and, under the default StoreLinkPreviews image mode, downloads the preview image through local pict-rs. While the top-level page URL is checked against internal IP ranges, the extracted og:image URL is not subject to the same restriction. As a result, an authenticated low-privileged user can submit an attacker-controlled public page whose Open Graph image points to an internal image endpoint. Lemmy will fetch that internal image server-side and store a local thumbnail that can then be served back to users. github.com/LemmyNet/lemmy/…/GHSA-h6hf-9846-xwrq
0

lemmy.org has been defederated

preview

We’ve seen a lot of spam come from lemmy.org and we have therefore defederated from their instance. For the moment they have open registrations which only require filling out a simple captcha to create an account which many people abuse.

The admin is active but rarely takes moderation actions, but I’ve sent a DM to them with our concerns. We’ll see how permanent this is.

We’ve seen a lot of spam come from lemmy.org and we have therefore defederated from their instance. For the moment they have open registrations which only require filling out a simple captcha to create an account which many people abuse.

The admin is active but rarely takes moderation actions, but I’ve sent a DM to them with our concerns. We’ll see how permanent this is.

0

Does anyone want to mod this community?

preview

I made an advice community for Swedish-speakers, and I happened to find one for Russian speakers. I’d mod, but I don’t speak Russian.

It’s called !advice_russian@lemmy.blahaj.zone

The moderator appears to have been banned

I made an advice community for Swedish-speakers, and I happened to find one for Russian speakers. I’d mod, but I don’t speak Russian.

It’s called !advice_russian@lemmy.blahaj.zone

The moderator appears to have been banned

0

Image posts created from lem.lemmy.blahaj.zone look weird only on lem.lemmy.blahaj.zone

preview

image to make my point. If I make an image post from blahaj (using the lem.lemmy.blahaj.zone app) it shows up as a link to an external source on the official app^[lem.lemmy.blahaj.zone/post/41085392], alexandrite^[alx.lemmy.blahaj.zone/…/41085392] and blorp^[…blahaj.zone/…/https%3A%2F%2Flemmy.blahaj.zone%2F…], i. e. it doesn’t embed. It looks normal everywhere else, i. e. from federated instances using the official web app^[lemmy.ml/post/45728815], and from the other web apps hosted locally^[phtn.lemmy.blahaj.zone/post/…/41085392] ^[mlmym.lemmy.blahaj.zone/post/41085392] ^[tes.lemmy.blahaj.zone/post/…/41085392].

Also alt text gets swallowed. It apparently doesn’t federate, I can see it when I click on edit, the box is prefilled with “I am beanis cupcake and I will eat you” but this alt-text doesnt show up when looking at this post from a federated instance. It does show up on local frontends that implement this functionality.

Thank you for your attention to this matter.

image to make my point. If I make an image post from blahaj (using the lem.lemmy.blahaj.zone app) it shows up as a link to an external source on the official app^[lem.lemmy.blahaj.zone/post/41085392], alexandrite^[alx.lemmy.blahaj.zone/…/41085392] and blorp^[…blahaj.zone/…/https%3A%2F%2Flemmy.blahaj.zone%2F…], i. e. it doesn’t embed. It looks normal everywhere else, i. e. from federated instances using the official web app^[lemmy.ml/post/45728815], and from the other web apps hosted locally^[phtn.lemmy.blahaj.zone/post/…/41085392] ^[mlmym.lemmy.blahaj.zone/post/41085392] ^[tes.lemmy.blahaj.zone/post/…/41085392].

Also alt text gets swallowed. It apparently doesn’t federate, I can see it when I click on edit, the box is prefilled with “I am beanis cupcake and I will eat you” but this alt-text doesnt show up when looking at this post from a federated instance. It does show up on local frontends that implement this functionality.

Thank you for your attention to this matter.

0

Lemmy Release v0.19.17 fixes Arabic user/community names and internal host access security advisory

preview

Changes

This release addresses another security advisory related to internal host access. You can now bypass these checks for federation, in order to federate with instances over the local network by setting environment variable DANGER_FEDERATION_ALLOW_LOCAL_IP=1. There are also some bug fixes, and lemmy-ui now logs file requests.

  • Improve IP checks by @nutomic in #6411
  • Allow to bypass federation IP checks with env var DANGER_FEDERATION_ALLOW_LOCAL_IP by @nutomic in #158
  • Fix Arabic user/community names by @nutomic in #3968
  • Fix removing post.url by @nutomic in #3984
  • Add lemmy-ui request logs by @MrKaplan-lw in #3933

Changes

This release addresses another security advisory related to internal host access. You can now bypass these checks for federation, in order to federate with instances over the local network by setting environment variable DANGER_FEDERATION_ALLOW_LOCAL_IP=1. There are also some bug fixes, and lemmy-ui now logs file requests.

  • Improve IP checks by @nutomic in #6411
  • Allow to bypass federation IP checks with env var DANGER_FEDERATION_ALLOW_LOCAL_IP by @nutomic in #158
  • Fix Arabic user/community names by @nutomic in #3968
  • Fix removing post.url by @nutomic in #3984
  • Add lemmy-ui request logs by @MrKaplan-lw in #3933
0

Tor Exit List Service

preview

Can blahaj commit to either blocking all of the ips on the tor exit list, or white listing them. This “block only a few” makes for a dice roll for tor users. Specifically the pictrs service just doesn’t serve photos to banned ips but lemmy still works so it just partially breaks.

Asking for a friend.

Can blahaj commit to either blocking all of the ips on the tor exit list, or white listing them. This “block only a few” makes for a dice roll for tor users. Specifically the pictrs service just doesn’t serve photos to banned ips but lemmy still works so it just partially breaks.

Asking for a friend.

0

Lemmy v0.19.16 fixes moderate security advisory

preview

This release mitigates a potential security issue with the image endpoint. In short, an attacker can inject query parameters and make proxied requests to arbitrary URLs. See the security advisory for details.

Also there are fixes for the database connection pool. The pool size is now at least two, as a lower size can result in deadlocks. Additionally there are now connection timeouts added. If your server logs show pool timeout errors, you should increase database.pool_size in the Lemmy config.

  • Fix for image proxy filetypes by @dessalines in #6357
  • Enable DB connection timeout by @Nutomic in #6355
  • Use min database pool size of 2. by @dessalines in #6345

github.com/LemmyNet/lemmy/…/GHSA-jvxv-2jjp-jxc3

This release mitigates a potential security issue with the image endpoint. In short, an attacker can inject query parameters and make proxied requests to arbitrary URLs. See the security advisory for details.

Also there are fixes for the database connection pool. The pool size is now at least two, as a lower size can result in deadlocks. Additionally there are now connection timeouts added. If your server logs show pool timeout errors, you should increase database.pool_size in the Lemmy config.

  • Fix for image proxy filetypes by @dessalines in #6357
  • Enable DB connection timeout by @Nutomic in #6355
  • Use min database pool size of 2. by @dessalines in #6345

github.com/LemmyNet/lemmy/…/GHSA-jvxv-2jjp-jxc3

0

programming.dev has been defederated

preview

We’ve been seeing frequent spam waves of targeted harassment from accounts made on programming.dev over the course of several weeks, which has among other unacceptable things contained transphobia, obscene pictures of animals, calling for the victim to commit suicide, and other hateful rhetoric.

For these reasons we are defederating from programming.dev. We may refederate in the future if we have reason to believe there will be no further problems like these from their instance.

Edit: I’ve spoken with the admins there and I may refederate once I have more details on their application system. To be clear they don’t support anything posted by these accounts and are deleting them as they are detected.

Edit: We’ve refedereted.

We’ve been seeing frequent spam waves of targeted harassment from accounts made on programming.dev over the course of several weeks, which has among other unacceptable things contained transphobia, obscene pictures of animals, calling for the victim to commit suicide, and other hateful rhetoric.

For these reasons we are defederating from programming.dev. We may refederate in the future if we have reason to believe there will be no further problems like these from their instance.

Edit: I’ve spoken with the admins there and I may refederate once I have more details on their application system. To be clear they don’t support anything posted by these accounts and are deleting them as they are detected.

Edit: We’ve refedereted.

0

Cannot access a community from another instance even though neither instance has each other blocked

preview

I cannot access !4tran4@sh.itjust.works from lemmy.blahaj.zone, a couple friends also had the same problem, other communities from sh.itjust.works are accessible though, and 4tran4 is accessible from other instances like lemmy.world

I cannot access !4tran4@sh.itjust.works from lemmy.blahaj.zone, a couple friends also had the same problem, other communities from sh.itjust.works are accessible though, and 4tran4 is accessible from other instances like lemmy.world

0

[SOLVED] is there a way for me to reset my password if I didn't provide an email when registering?

preview

I’m only logged in on Voyager right now and there’s nowhere where I can reset my password, and I can’t log in on web to do that since I forgot my password. I didn’t provide an email when registering, am I screwed or is there any hope? Worst case scenario, this might be my push to switch to the Piefed instance I guess

EDIT: I managed to log in on my other device by ripping my token out of Voyager, yes it’s a very janky solution that probably won’t last long but it works for now

EDIT 2: Turns out, I did have an email attached to this acc, just a really obscure one I never used. Problem solved 😁

I’m only logged in on Voyager right now and there’s nowhere where I can reset my password, and I can’t log in on web to do that since I forgot my password. I didn’t provide an email when registering, am I screwed or is there any hope? Worst case scenario, this might be my push to switch to the Piefed instance I guess

EDIT: I managed to log in on my other device by ripping my token out of Voyager, yes it’s a very janky solution that probably won’t last long but it works for now

EDIT 2: Turns out, I did have an email attached to this acc, just a really obscure one I never used. Problem solved 😁

0

How do I move to Blahaj Piefed from Lemmy?

preview

I keep hearing about all of the new features that Piefed has compared to Lemmy, so I would like to try it out. However, I’m having trouble making an account.

I tried registering at piefed.blahaj.zone/auth/register

I see the note to get the token from my Lemmy account but when I click on lemmy.blahaj.zone/link I receive an error I get redirected to mllym and receive the following error: “Authentication Failed No authentication token found. Please make sure you’re accessing this page through the proper authentication flow.”

I also tried just creating an account a while back without using the token but I don’t think it ever got approved.

Thanks for any help!

I keep hearing about all of the new features that Piefed has compared to Lemmy, so I would like to try it out. However, I’m having trouble making an account.

I tried registering at piefed.blahaj.zone/auth/register

I see the note to get the token from my Lemmy account but when I click on lemmy.blahaj.zone/link I receive an error I get redirected to mllym and receive the following error: “Authentication Failed No authentication token found. Please make sure you’re accessing this page through the proper authentication flow.”

I also tried just creating an account a while back without using the token but I don’t think it ever got approved.

Thanks for any help!

0

Donation banner from Lemmy Devs upon logging in

preview

When we logged in today we found this.

We would like it removed if possible, thank you.

Alt text (since we got an overflow error the ‘official’ way):

A banner with a light blue background and a X at the top right to indicate the possibility to close it.

The text says: “Support Lemmy development. An open source project the size of Lemmy needs constant work to manage the project, implement new features and fix bugs. Dessalines and Nutomic work full-time on these tasks and more. As there in no advertising or tracking, all of our work is funded through donations. Even do there is barely enough time in the day, and no time for a second job. The only available option are user donations. To keep it viable donations need to reach a minimum of 5000€ per month, resulting in a modest salary of 2500€ per developer. If that goal is reached we can stop worrying about money, and fully focus on improving the software for the benefit of all users and instances. We especially rely on recurring donations to secure the long-term development and make Lemmy the best it can be.

If you want more information before donating, consider the comparison with Reddit. It began as startup funded by rich investors. The site is managed by corporate executives who over time have become more and more disconnected from normal users. Their main goal is to make investors happy and to make a profit. This leads to user-hostile decisions like firing the employee responsible for AMAs, blocking third-party apps and more. As Reddit is a single website under a single authority, it means all users need to follow the same rules, including ridiculous ones like censoring the name “Luigi”.

Lemmy represents a new type of social media which is the complete opposite of Reddit. It is split across many different websites, each with its own rules, and managed by normal people who actually care about the users. There is no company and no profit motive. Much of the work is carried out by volunteer admins, mods and posters, who contribute out of enthusiasm and not for money. For users this is great as there is no advertising nor tracking, and no chance of takeover by a billionaire. Additionally there are no builtin political or ideological restrictions. You can use the software for any purpose you like, add your own restrictions or scrutinize its inner workings. Lemmy truly belongs to everyone.

Nutomic and Dessalines, Lemmy Developers.”

There is a slightly darker blue button under this text with the word Donate on it.

When we logged in today we found this.

We would like it removed if possible, thank you.

Alt text (since we got an overflow error the ‘official’ way):

A banner with a light blue background and a X at the top right to indicate the possibility to close it.

The text says: “Support Lemmy development. An open source project the size of Lemmy needs constant work to manage the project, implement new features and fix bugs. Dessalines and Nutomic work full-time on these tasks and more. As there in no advertising or tracking, all of our work is funded through donations. Even do there is barely enough time in the day, and no time for a second job. The only available option are user donations. To keep it viable donations need to reach a minimum of 5000€ per month, resulting in a modest salary of 2500€ per developer. If that goal is reached we can stop worrying about money, and fully focus on improving the software for the benefit of all users and instances. We especially rely on recurring donations to secure the long-term development and make Lemmy the best it can be.

If you want more information before donating, consider the comparison with Reddit. It began as startup funded by rich investors. The site is managed by corporate executives who over time have become more and more disconnected from normal users. Their main goal is to make investors happy and to make a profit. This leads to user-hostile decisions like firing the employee responsible for AMAs, blocking third-party apps and more. As Reddit is a single website under a single authority, it means all users need to follow the same rules, including ridiculous ones like censoring the name “Luigi”.

Lemmy represents a new type of social media which is the complete opposite of Reddit. It is split across many different websites, each with its own rules, and managed by normal people who actually care about the users. There is no company and no profit motive. Much of the work is carried out by volunteer admins, mods and posters, who contribute out of enthusiasm and not for money. For users this is great as there is no advertising nor tracking, and no chance of takeover by a billionaire. Additionally there are no builtin political or ideological restrictions. You can use the software for any purpose you like, add your own restrictions or scrutinize its inner workings. Lemmy truly belongs to everyone.

Nutomic and Dessalines, Lemmy Developers.”

There is a slightly darker blue button under this text with the word Donate on it.

0

Lemmy v0.19.15 is available with DDoS prevention

preview

And Lemmy version 1 is on the horizon

Lemmy Release v0.19.14

Changes

Recently some malicious users started to use an exploit where they would post rule violating content and then delete the account. This would prevent admins and mods from viewing the user profile to find other posts, and would also prevent federation of ban actions.

The new release fixes these problems. Thanks to @flamingos-cant for contributing to solve this. Upgrade instructions

There are no breaking changes with this release.

Follow the upgrade instructions for ansible or docker.

Lemmy Release v0.19.15 and Testing for 1.0

Changes

We messed up the previous release and did not include the full list of changes. In fact there were a handful of other bug fixes, and notably a maximum page limit of 10 to prevent a DDoS attack. Some users were also hitting this limit, so with this version the limit is increased to 100. We apologize for these mistakes.

Here is the full changelog since 0.19.13:

  • Don’t allow accessing page numbers greater than 10 by @dessalines #6017
  • Update deps based on cargo audit by @Nutomic in #6258
  • Increase page limit to 100 by @Nutomic in #6252
  • Ban federation for deleted users by @Nutomic in #6207
  • Federate mod actions on deleted users by @Nutomic in #6199
  • Allow admins to view deleted user profiles by @Nutomic in #6194
  • Adding creator and community indexes for post_aggregates. by @dessalines in #6025
  • Ignore apub person banners which cannot be parsed by @Nutomic in #6015u

Lemmy 1.0

Now for the good news, the development version of Lemmy 1.0 is available for testing on voyager.lemmy.ml with lots of new features. Registration is open, you’re welcome to create an account. Feel free to post spam and try everything out. Here is only a short overview:

Multi-communities: Combine different communities together into a custom feed.
Post scheduling: Specify when your post should be published.
Keyword filter: Automatically hide posts about certain topics.
Private communities: Only followers can view the content, and need to be approved manually by mods. Other community visibilities are also available (unlisted, local only).
New notification system: Including notifications for mod actions, and subscribing to communities and posts to be notified about new comments.
OAuth: Login to Lemmy with existing account from another website. Use this link to signup with your Github account (the UI still needs to be improved).
Post Tags: Categorize posts within a community (UI part not implemented yet).
User vote totals: You can see the total number of upvotes and downvotes given to each user.
User notes: You can keep notes on other users.
Combined Feeds: View your saved, liked posts and comments together in a single list.
Comment Locking: Mods can now lock comments recursively.
GDPR style data exporting: You can now export your full posting history as a JSON file.
Plugins: Can be written in JS, Python, Rust, and any other language that targets Webassembly. The test server has a plugin for automatic language tagging of posts.
Cursor pagination: Don’t lose your place in the feed when switching pages.
API v3 compat: Lemmy 1.0 can be used by existing apps with no changes (but most new features are only available via the new API v4).
More: Countless smaller features, bug fixes and improvements, too much to list here.

All the above mentioned features are already implemented and fully working, but may need some polishing. If you encounter any problems, please open an issue (backend, frontend). voyager.lemmy.ml is automatically updated to the latest development version every night, so that changes can immediately be tested.

Keep in mind that Lemmy 1.0 is still in alpha state. There may be breaking changes and critical bugs, so do not attempt to upgrade your own instances yet. We intend to publish the first beta version in January, along with API docs and upgrade instructions for test servers.

We hope that you are as excited about these new features as we are. With all this said, happy testing and Merry Christmas! Upgrade instructions

There are no breaking changes with this release.

Follow the upgrade instructions for ansible or docker.

And Lemmy version 1 is on the horizon

Lemmy Release v0.19.14

Changes

Recently some malicious users started to use an exploit where they would post rule violating content and then delete the account. This would prevent admins and mods from viewing the user profile to find other posts, and would also prevent federation of ban actions.

The new release fixes these problems. Thanks to @flamingos-cant for contributing to solve this. Upgrade instructions

There are no breaking changes with this release.

Follow the upgrade instructions for ansible or docker.

Lemmy Release v0.19.15 and Testing for 1.0

Changes

We messed up the previous release and did not include the full list of changes. In fact there were a handful of other bug fixes, and notably a maximum page limit of 10 to prevent a DDoS attack. Some users were also hitting this limit, so with this version the limit is increased to 100. We apologize for these mistakes.

Here is the full changelog since 0.19.13:

  • Don’t allow accessing page numbers greater than 10 by @dessalines #6017
  • Update deps based on cargo audit by @Nutomic in #6258
  • Increase page limit to 100 by @Nutomic in #6252
  • Ban federation for deleted users by @Nutomic in #6207
  • Federate mod actions on deleted users by @Nutomic in #6199
  • Allow admins to view deleted user profiles by @Nutomic in #6194
  • Adding creator and community indexes for post_aggregates. by @dessalines in #6025
  • Ignore apub person banners which cannot be parsed by @Nutomic in #6015u

Lemmy 1.0

Now for the good news, the development version of Lemmy 1.0 is available for testing on voyager.lemmy.ml with lots of new features. Registration is open, you’re welcome to create an account. Feel free to post spam and try everything out. Here is only a short overview:

Multi-communities: Combine different communities together into a custom feed.
Post scheduling: Specify when your post should be published.
Keyword filter: Automatically hide posts about certain topics.
Private communities: Only followers can view the content, and need to be approved manually by mods. Other community visibilities are also available (unlisted, local only).
New notification system: Including notifications for mod actions, and subscribing to communities and posts to be notified about new comments.
OAuth: Login to Lemmy with existing account from another website. Use this link to signup with your Github account (the UI still needs to be improved).
Post Tags: Categorize posts within a community (UI part not implemented yet).
User vote totals: You can see the total number of upvotes and downvotes given to each user.
User notes: You can keep notes on other users.
Combined Feeds: View your saved, liked posts and comments together in a single list.
Comment Locking: Mods can now lock comments recursively.
GDPR style data exporting: You can now export your full posting history as a JSON file.
Plugins: Can be written in JS, Python, Rust, and any other language that targets Webassembly. The test server has a plugin for automatic language tagging of posts.
Cursor pagination: Don’t lose your place in the feed when switching pages.
API v3 compat: Lemmy 1.0 can be used by existing apps with no changes (but most new features are only available via the new API v4).
More: Countless smaller features, bug fixes and improvements, too much to list here.

All the above mentioned features are already implemented and fully working, but may need some polishing. If you encounter any problems, please open an issue (backend, frontend). voyager.lemmy.ml is automatically updated to the latest development version every night, so that changes can immediately be tested.

Keep in mind that Lemmy 1.0 is still in alpha state. There may be breaking changes and critical bugs, so do not attempt to upgrade your own instances yet. We intend to publish the first beta version in January, along with API docs and upgrade instructions for test servers.

We hope that you are as excited about these new features as we are. With all this said, happy testing and Merry Christmas! Upgrade instructions

There are no breaking changes with this release.

Follow the upgrade instructions for ansible or docker.

0

mlmym breaks Blahaj?

preview

I’m fairly new to Blahaj and was trying out the different interfaces for a couple of days by choosing “once” on different ones to feel it out. I decided that I liked the old Reddit style and selected “always” on mlmym.

I didn’t have any problems when I was selecting “once” for mlmym, but when I chose “always”, it crapped itself. Immediately afterward, I was no longer able to access Blahaj.

I see myself logged in on the top right, but the page says “unable to retrieve site. there doesn’t seem to be anything here”

I get this same error when checking through Chrome, Firefox, and Tor, even if I’m not logged in. If I do try to log in on another browser, I put in my credentials and get the “unable to retrieve site” error and it does not log me in.

I can only access Blahaj again by using a direct link to a sub with a different interface prefix (lem.lemmy.blahaj.zone/c/main for example).

Sometimes I’m able to quickly hit “cancel redirect” on the default page that comes up when it’s trying to push to mlmym.

I’ve changed it to “always” on Blorp instead and it works fine, but I’d really rather use mlmym.

Is there a fix for this?

I’m fairly new to Blahaj and was trying out the different interfaces for a couple of days by choosing “once” on different ones to feel it out. I decided that I liked the old Reddit style and selected “always” on mlmym.

I didn’t have any problems when I was selecting “once” for mlmym, but when I chose “always”, it crapped itself. Immediately afterward, I was no longer able to access Blahaj.

I see myself logged in on the top right, but the page says “unable to retrieve site. there doesn’t seem to be anything here”

I get this same error when checking through Chrome, Firefox, and Tor, even if I’m not logged in. If I do try to log in on another browser, I put in my credentials and get the “unable to retrieve site” error and it does not log me in.

I can only access Blahaj again by using a direct link to a sub with a different interface prefix (lem.lemmy.blahaj.zone/c/main for example).

Sometimes I’m able to quickly hit “cancel redirect” on the default page that comes up when it’s trying to push to mlmym.

I’ve changed it to “always” on Blorp instead and it works fine, but I’d really rather use mlmym.

Is there a fix for this?

0

Blåhaj zone - the nitty gritty.

preview

Hey all! You asked for it, so here it is. I’ma drop a diagram here and will refer to it throughout the rest of this post:

Our infrastructure

In simple terms, the way it all works is we have our protected servers in the backend.

PERSISTENCE

We run our postgres database defensively with 3 dedicated (metal) servers, the main servers each have 2× 1.92TB enterprise-grade NVMe drives mirrored (RAID-1).

We use patroni + percona postgres to manage the cluster. Each instance has a software watchdog to trip-wire a failure.

Scripts automate promotion to make sure under normal circumstances (healthy cluster) that the main server, our big EPYC 7401P 128GiB DDR4(ECC) i350 NIC is the primary.

We have a second server which is a less-powerful i9-12900K 128Gib DDR4(non-ECC) i219v NIC that acts as a read-only secondary, and gets promoted to primary on failover.

Then there’s the little server that replicates for backups and potential dual-failure disaster scenarios, a meager Ryzen 7 3700X 64GiB DDR4(ECC) i210 NIC and it has 2× 8TB enterprise-grade spinny disks striped (RAID-0), to keep the DB and backups safe.

It will become primary if the other 2 servers cannot.

The database servers are not connected to directly by any of our services, there’s instead a load balancer in front which targets the 3× server’s HAProxy instances that have one port directed at the current primary and another port for the current secondary.

This database infrastructure is the biggest, costliest and most engineered part of our setup (which is very frugal for what it is). It’s taken me through a near catastrauphic situation (double server failure). You can ask Ada… I was freaking the fuck out.

Additionally we have a single Redis instance which runs on a quad CPU ARM (Ampere) 8GiB RAM 80GB SSD.

  • Primary server: €83.70/m
  • Secondary server: €61.70/m
  • Backup server: €40.70/m
  • Load balancer: €5.39/m
  • Redis: €6.49/m
  • Total: €197.98/m (AUD ~$350) for the persistence layer.

APPLICATION

We then have a prometheus/grafana monitoring box at another €6.49/m.

Then we have the services which run just like everyone else on various pieces of hardware, in docker containers for most, but some run standalone on their own hosts. Sharkey €24.49, Lemmy €12.49/m, Synapse €12.49/m, everything else smaller (pyfedi, pixelfed, friendica, photon frontend, various different static frontends, Ada’s latest project of the week) runs on a single dedicated docker host costing €38.70/m.

That brings us to another €101.15/m for the application layer.

EDGE

Then under that we now have the edge nodes, which are completely standalone and do not have internal VPCs etc, it’s TLS in, TLS out for these machines.

Each node is generally around 2× vCPU 1GB RAM 25GB SSD 2TB bandwidth for around €6/m. We have 4, so that’s around €24/m all up.

End user flow

So when you vist the site, you will first typically hit our DNS server. Our DNS server uses the requesting IP, or EDNS client subnet provided to work out which healthy node is closest to your region, and gives you back that IP address.

Side note: It’s important to realise that up until this point, what domain you requested is known to yourself and the DNS provider you used. If you care about privacy, you should install a pihole (you can install it in a docker container, you don’t need a raspberry pi), and set it’s upstream DNS to Quad9 with ECS and DNSSEC enabled (or if you’re really adventurous, install your own unbound server and bypass intermediaries completely).

We run a dual-stack IPv4/IPv6 network all the way through so if you’re on IPv6, you’ll get our v6 IPs, and hopefully enjoy a less NATted, wider MTU’d, packet un-fragmented journey through the internet.

Once you have the IP address from the DNS server, you will connect to the caching caddy server on the closest healthy node to your geographical location and it will terminate your TLS session, decrypting your request.

At this point we’ll see if we have the asset to the request you made cached locally, if so we can send it straight back to you, super quickly!

If not then it will connect to the upstream server in our core location over a (presumably) much larger, less latent and more resilient trunk pipe than most consumer-grade bandwidth will provide. (Unless you run your own redundant-path dark fibre into your house, which I’m not discounting entirely… I know people.)

The returned response will then be evaluated for cacheability and sent back to you.

The build

We wanted to make sure that if one of these endpoints degrade / get attacked / shut down / die, that we can spin up a new one really quick. So the deployment and configuration is completely managed by an Ansible configuration. The deployment of a single node or even a complete replacement of all nodes takes about 10 minutes.

Our nodes run 2 pieces of third party software, and a few scripts to manage things.

DNS

For the DNS resolution we run gdnsd with 2 plugins, http_status and geoip.

The http_status plugin monitors the health of the other nodes to make sure it’s not sending people to nodes that don’t respond.

The geoip plugin uses the requesting IP to determine what region/country you’re from, and select a priority list of nodes closes to that region. The first healthy node in that list is the node that’s selected.

CACHING REVERSE-PROXY

For the web-serving component, we run a custom xcaddy compiled caddy server with a few modules included: cache-handler, otter storage, coraza WAF, ratelimit, layer4, maxmind and crowdsec.

At the moment only the first 3 are in use, but the other 4 are included in case we need to mitigate attacks or other edge cases in the future.

And that’s pretty much it!

If anyone wants any help with setting up their own version of this, or needs more details, let me know. I’d be happy to help.

If a lot of people are interested (which I doubt at this stage, but who knows?) I’d even be willing to create a project or make it dockerisable etc, but I suspect that it’s something that most people would just use Cloudflare et. al. for, if the privacy aspect wasn’t such a concern.

Hey all! You asked for it, so here it is. I’ma drop a diagram here and will refer to it throughout the rest of this post:

Our infrastructure

In simple terms, the way it all works is we have our protected servers in the backend.

PERSISTENCE

We run our postgres database defensively with 3 dedicated (metal) servers, the main servers each have 2× 1.92TB enterprise-grade NVMe drives mirrored (RAID-1).

We use patroni + percona postgres to manage the cluster. Each instance has a software watchdog to trip-wire a failure.

Scripts automate promotion to make sure under normal circumstances (healthy cluster) that the main server, our big EPYC 7401P 128GiB DDR4(ECC) i350 NIC is the primary.

We have a second server which is a less-powerful i9-12900K 128Gib DDR4(non-ECC) i219v NIC that acts as a read-only secondary, and gets promoted to primary on failover.

Then there’s the little server that replicates for backups and potential dual-failure disaster scenarios, a meager Ryzen 7 3700X 64GiB DDR4(ECC) i210 NIC and it has 2× 8TB enterprise-grade spinny disks striped (RAID-0), to keep the DB and backups safe.

It will become primary if the other 2 servers cannot.

The database servers are not connected to directly by any of our services, there’s instead a load balancer in front which targets the 3× server’s HAProxy instances that have one port directed at the current primary and another port for the current secondary.

This database infrastructure is the biggest, costliest and most engineered part of our setup (which is very frugal for what it is). It’s taken me through a near catastrauphic situation (double server failure). You can ask Ada… I was freaking the fuck out.

Additionally we have a single Redis instance which runs on a quad CPU ARM (Ampere) 8GiB RAM 80GB SSD.

  • Primary server: €83.70/m
  • Secondary server: €61.70/m
  • Backup server: €40.70/m
  • Load balancer: €5.39/m
  • Redis: €6.49/m
  • Total: €197.98/m (AUD ~$350) for the persistence layer.

APPLICATION

We then have a prometheus/grafana monitoring box at another €6.49/m.

Then we have the services which run just like everyone else on various pieces of hardware, in docker containers for most, but some run standalone on their own hosts. Sharkey €24.49, Lemmy €12.49/m, Synapse €12.49/m, everything else smaller (pyfedi, pixelfed, friendica, photon frontend, various different static frontends, Ada’s latest project of the week) runs on a single dedicated docker host costing €38.70/m.

That brings us to another €101.15/m for the application layer.

EDGE

Then under that we now have the edge nodes, which are completely standalone and do not have internal VPCs etc, it’s TLS in, TLS out for these machines.

Each node is generally around 2× vCPU 1GB RAM 25GB SSD 2TB bandwidth for around €6/m. We have 4, so that’s around €24/m all up.

End user flow

So when you vist the site, you will first typically hit our DNS server. Our DNS server uses the requesting IP, or EDNS client subnet provided to work out which healthy node is closest to your region, and gives you back that IP address.

Side note: It’s important to realise that up until this point, what domain you requested is known to yourself and the DNS provider you used. If you care about privacy, you should install a pihole (you can install it in a docker container, you don’t need a raspberry pi), and set it’s upstream DNS to Quad9 with ECS and DNSSEC enabled (or if you’re really adventurous, install your own unbound server and bypass intermediaries completely).

We run a dual-stack IPv4/IPv6 network all the way through so if you’re on IPv6, you’ll get our v6 IPs, and hopefully enjoy a less NATted, wider MTU’d, packet un-fragmented journey through the internet.

Once you have the IP address from the DNS server, you will connect to the caching caddy server on the closest healthy node to your geographical location and it will terminate your TLS session, decrypting your request.

At this point we’ll see if we have the asset to the request you made cached locally, if so we can send it straight back to you, super quickly!

If not then it will connect to the upstream server in our core location over a (presumably) much larger, less latent and more resilient trunk pipe than most consumer-grade bandwidth will provide. (Unless you run your own redundant-path dark fibre into your house, which I’m not discounting entirely… I know people.)

The returned response will then be evaluated for cacheability and sent back to you.

The build

We wanted to make sure that if one of these endpoints degrade / get attacked / shut down / die, that we can spin up a new one really quick. So the deployment and configuration is completely managed by an Ansible configuration. The deployment of a single node or even a complete replacement of all nodes takes about 10 minutes.

Our nodes run 2 pieces of third party software, and a few scripts to manage things.

DNS

For the DNS resolution we run gdnsd with 2 plugins, http_status and geoip.

The http_status plugin monitors the health of the other nodes to make sure it’s not sending people to nodes that don’t respond.

The geoip plugin uses the requesting IP to determine what region/country you’re from, and select a priority list of nodes closes to that region. The first healthy node in that list is the node that’s selected.

CACHING REVERSE-PROXY

For the web-serving component, we run a custom xcaddy compiled caddy server with a few modules included: cache-handler, otter storage, coraza WAF, ratelimit, layer4, maxmind and crowdsec.

At the moment only the first 3 are in use, but the other 4 are included in case we need to mitigate attacks or other edge cases in the future.

And that’s pretty much it!

If anyone wants any help with setting up their own version of this, or needs more details, let me know. I’d be happy to help.

If a lot of people are interested (which I doubt at this stage, but who knows?) I’d even be willing to create a project or make it dockerisable etc, but I suspect that it’s something that most people would just use Cloudflare et. al. for, if the privacy aspect wasn’t such a concern.

0

Changes to the instance networking

preview

I’ve recently found myself without much to do (short version: the company that my company was contracting to went into voluntary administration just before Christmas, while Ada and I were away in Melbourne), so I’ve had a little bit of time on my hands to do some work on the site infrastructure, free from meetings and corporate wankery. YAY!

One of the things I’ve wanted to do for a while now is setup some form of edge-node caching and geo-DNS to get the various sites we host closer to you folks who use our instances.

And yes, there’s Cloudflare… and Akamai… and Bunny.net… however as a safe-haven for vulnerable minorities, and with the geo-political situation the way it is these days, we really need to be super careful about where we terminate your connections. Who are the intermediate people who can see and collect your data. Who can switch our servers off at a moment’s notice, suspend the domain names, shut us down?

Until recently we’ve known that we are slow on the edge, but we controlled all our own hardware, and we’ve not had the capacity to do much about it.

So over the last few days, I’ve taken the time to setup a bunch of edge nodes, migrate DNS away from third party providers, move domain name registrars.

The end result is that (with a few minor site interruptions) now we have our own CDN that we control all the way from DNS resolution until you hit the database on our dedicated servers. Your traffic is encrypted all the way through, our core infrastructure isn’t exposed to people who sniff around to see who they can try to report us and shut us down, nobody else can see your browsing it in transit, and for people not in or around Finland, it’s noticeably faster to load the site and click around.

To make sure you’re all fully informed, I’ll carefully disclose our decisions and new structure.

Firstly our edge servers are on Vultr and DigitalOcean. These 2 providers from our research seem to be quite neutral and non-politically aligned, and neither one by themselves can take us entirely down, and neither one of them are where our core infrastructure is located.

Secondly our edge locations have been carefully chosen to be regions that are outside jurisdictions where we can currently see political turmoil, overly zealous conservatism and fascist activity. We’ve chosen Toronto Canada, Sydney Australia, Amsterdam Netherlands and Frankfurt Germany as our edge node and DNS server locations.

Thirdly we’ve moved our domains into EuroDNS registrar to minimize the chance that the USA pressures companies to take action against our domains. EuroDNS is a large company headquartered in Luxembourg, and with no ties to the US itself, it’s parent company or any sibling companies, this gives us comfort that they can resist any political pressure which may be applied.

If there’s any interest in how we setup the infrastructure, let me know and I can make a separate technical post about it.

EDIT - here it is: lemmyverse.link/lemmy.blahaj.zone/post/36690717

I’ve recently found myself without much to do (short version: the company that my company was contracting to went into voluntary administration just before Christmas, while Ada and I were away in Melbourne), so I’ve had a little bit of time on my hands to do some work on the site infrastructure, free from meetings and corporate wankery. YAY!

One of the things I’ve wanted to do for a while now is setup some form of edge-node caching and geo-DNS to get the various sites we host closer to you folks who use our instances.

And yes, there’s Cloudflare… and Akamai… and Bunny.net… however as a safe-haven for vulnerable minorities, and with the geo-political situation the way it is these days, we really need to be super careful about where we terminate your connections. Who are the intermediate people who can see and collect your data. Who can switch our servers off at a moment’s notice, suspend the domain names, shut us down?

Until recently we’ve known that we are slow on the edge, but we controlled all our own hardware, and we’ve not had the capacity to do much about it.

So over the last few days, I’ve taken the time to setup a bunch of edge nodes, migrate DNS away from third party providers, move domain name registrars.

The end result is that (with a few minor site interruptions) now we have our own CDN that we control all the way from DNS resolution until you hit the database on our dedicated servers. Your traffic is encrypted all the way through, our core infrastructure isn’t exposed to people who sniff around to see who they can try to report us and shut us down, nobody else can see your browsing it in transit, and for people not in or around Finland, it’s noticeably faster to load the site and click around.

To make sure you’re all fully informed, I’ll carefully disclose our decisions and new structure.

Firstly our edge servers are on Vultr and DigitalOcean. These 2 providers from our research seem to be quite neutral and non-politically aligned, and neither one by themselves can take us entirely down, and neither one of them are where our core infrastructure is located.

Secondly our edge locations have been carefully chosen to be regions that are outside jurisdictions where we can currently see political turmoil, overly zealous conservatism and fascist activity. We’ve chosen Toronto Canada, Sydney Australia, Amsterdam Netherlands and Frankfurt Germany as our edge node and DNS server locations.

Thirdly we’ve moved our domains into EuroDNS registrar to minimize the chance that the USA pressures companies to take action against our domains. EuroDNS is a large company headquartered in Luxembourg, and with no ties to the US itself, it’s parent company or any sibling companies, this gives us comfort that they can resist any political pressure which may be applied.

If there’s any interest in how we setup the infrastructure, let me know and I can make a separate technical post about it.

EDIT - here it is: lemmyverse.link/lemmy.blahaj.zone/post/36690717

0

Got error with Blahaj linker when trying to make piefed account.

preview

I meant to make a piefed account a while back and never got around to it. Tried to do so today and when I clicked the link to get my code I got an error instead.

Authentication Failed

No authentication token found. Please make sure you’re accessing this page through the proper authentication flow.

I even tried reloading the page after disabling all my plugins and still got the error (although the styling looked a lot better after disabling NoScript, even though I have blahaj marked as allowed anyways.)

I meant to make a piefed account a while back and never got around to it. Tried to do so today and when I clicked the link to get my code I got an error instead.

Authentication Failed

No authentication token found. Please make sure you’re accessing this page through the proper authentication flow.

I even tried reloading the page after disabling all my plugins and still got the error (although the styling looked a lot better after disabling NoScript, even though I have blahaj marked as allowed anyways.)