cross-posted from: https://lemm.ee/post/47963381

> Computer Love by Kraftwerk (1981)

Hey folks!

I'll be updating lemm.ee to 0.19.7 shortly. I'll take it offline & also perform some database maintenance at the same time.

I have been investigating some incoming federation issues, and I haven't been able to find the actual cause. My current theory is that they are related to some server timeouts. I am hoping that the combination of the Lemmy upgrade and database maintenance may help improve the situation, but if not, then I will try other approaches.

Edit: the upgrade has been completed!

Started getting an error "Posts failed loading, retry" whenever Jerboa attempts to load more posts from the "All" feed. This does not seem to happen when viewing specific community feeds. Refreshing the entire feed still works just fine, and produces new posts. I swapped to a couple other instances, such as lemmy.world, and did not get the same behavior. This just started yesterday, 2024-11-17.

I'd upload an image, but image uploads are also broken, have been for a few days.

UPDATE: Seems to be fixed, at the moment.

Hello everyone,

There seems to be some federation delay between lemm.ee and lemmy.ml: https://grafana.lem.rocks/d/bdid38k9p0t1cf/federation-health-single-instance-overview?orgId=1&var-instance=lemm.ee&var-remote_instance=lemmy.ml

There is now a more than 5 days delay between the two instances

@sunaurus@lemm.ee FYI

Is it just on my end? All other instances i have tried (.world, .ml, sh.itjust.works, db0, even hexbear) are displaying thumbnails correctly. I have tried opening lemm.ee in chrome, changing my dns etc.

Anything else I can try? Any help is appreciated.

Here are the screengrabs for those interested https://imgur.com/a/LGlVI6T

Hey!

Unfortunately, Hetzner (our hosting provider) is currently experiencing some network issues. They are planning to address this with an emergency maintenance in roughly 13 hours from now, which will cause lemm.ee downtime. Hopefully we'll be fully recovered later tomorrow!

----

UPDATE: Sorry for the false alarm, I was on the move when I posted this and missed the fact that the Hetzner notice was actually for next month! So it's not as imminent as I originally understood. As we have a whole month to prepare, I will probably be able to come up with some alternative solution to prevent the downtime while they are conducting this maintenance.

Do you think there is censorship on Lemm.ee instances?

Hey folks!

I am looking for feedback from active lemm.ee users on what you all value when it comes to images on Lemmy. I'll go into a bit of detail about what our options are, and then I would ask you to voice your opinion about the issue in the comments.

First, some context for those who don't know. Lemmy software can be configured to handle images in three different ways:

1. Store images locally - whenever an external image is posted somewhere, lemm.ee will download a permanent local copy. When you view posts, you are seeing our local copy of the image.
2. Proxy all images - similarly to the first option, lemm.ee will download a local copy of external images, however, this copy is temporary. It will be automatically deleted shortly after, and if users open the relevant post/comment again in the future, there will be another attempt to download a temporary copy at that point.
3. Pass through external images directly - lemm.ee never downloads any external images, users will always connect directly to the source servers to load the images.

There are pros and cons to each configuration.

Storing images locally

Benefits:

1. Your IP address is never leaked to external image hosts, as you never connect directly to the source server. External image hosts only see the IP address of the lemm.ee server.
2. External servers don't become bottlenecks for opening lemm.ee posts. If an external server is slow, it won't matter, because the image is always available locally

Downsides:

1. As time goes on, our storage will fill up with hundreds of gigabytes of useless images, most of which will never be viewed again after the relevant posts fall off the front page.
2. Many big external image hosts will rate limit bigger Lemmy servers, causing broken images when we fail to make a local copy.
3. Crucially: some people love to spend their time uploading illegal content to online servers. There are tools to try and filter out such content, but these are not perfect. The end result is that there is a high chance of some content like this inadvertently reaching lemm.ee storage and staying there permanently. This downside is why lemm.ee has not, and will not, use this particular configuration.

Proxying images

Benefits: In addition to the same benefits as exist for the permanent local storage, by only temporarily making local copies for the moment they are requested by our users, we free up a ton of storage & remove the risk of permanently storing illegal content on our servers.

Downsides: The key downside is that external rate limits hit us much harder, as we will be requesting external images far more often. This results in a lot of constant broken images on lemm.ee.

Passing through external images

Benefits:

1. Images are rarely broken, unless the source server goes down.
2. The images never touch our servers, removing a lot of risk with illegal content as well as with storage costs.

Downsides:

1. Our users lose a degree of privacy. Every external image that is loaded on your browser will result in the remote server getting a request directly from your computer to fetch that image - this is pretty much the same as you had visited that external server directly, which lets them log your IP address if they wish.
2. When remote servers are slow, it can slow down the entire page load in some cases.

Current situation

Initially, lemm.ee was using the third option of passing through images. Ever since support for option 2, image proxying, was implemented in Lemmy code, we immediately switched to that option, mainly for the privacy benefits. However, after many months, and being blocked by more and more external servers, it is clear that image proxying is seriously degrading the user experience on lemm.ee. We often end up with broken images, and our users have to deal with the results.

I still believe image proxying is a really valuable feature, but I am starting to believe it is a better fit for small instances which make much less requests to external servers.

As a result, I am now seriously considering switching back to the previous method of passing through external images.

This is where you come in - I would ask you as users to please let me know which do you value more: the privacy that you get from image proxying, or the better user experience you get from directly passing through images from their source. Please let me know in the comments how you feel. If I get enough feedback about people being against image proxying, then I will be switching it off for lemm.ee soon. Thanks for reading & sharing your thoughs, and I hope you have a great weekend!

Been getting a lot of instability out of pictrs the last two days. Nothing in the week before that.

By instability, I'm talking 500 errors when uploading images (POST https://lemm.ee/pictrs/image). They seem pretty much random, I can get around the errors by just repeatedly trying to upload the same file until it works. As far as I can tell, there's nothing I'm doing wrong, trying to upload images too large produces a different, and much more reasonable, error. And there's no info at all in the response, except for the 500 code itself.

In reference to this thread:

• https://lemm.ee/post/44491669
• https://lemmy.world/post/20694710
• https://discuss.tchncs.de/post/23365372

Tl,dr:

• ClubsAll is a closed source platform which fetches Lemmy content
• ClubsAll however does allow Lemmy instances to federate its communities (!clubsall@clubsall.com gives an error, see https://lemm.ee/post/44491669/15374449)
• Comments from ClubsAll do federate to Lemmy communities: (https://lemmy.world/comment/12828092 / https://clubsall.com/posts/what-food-and-or-drink-will-you-eat-when-you-are-senile-and-forget-you-already-had-it-the-meal-before-oD_s4)
• It is not possible to host a ClubsAll instance at the moment

What do you all think about this?

Without using external scripts, is there a way to hide posts that link to specific domains? For example, if I want to hide all posts where the OP put google.com links in the URL field when creating the post.

Following the request from https://lemm.ee/post/38756969 I want to add pronouns to my username. I would like have the full " [he/him]" string appended to my username, however lemm.ee only allows up to 20 characters.

Would it be possible to add more characters or a pronoun selector like on hexbear.net?

I currently have it blocked with ublock Origin, but I would like to be able to completely disable it so that post titles can use 100% of screen width.

cross-posted from: https://lemmy.dbzer0.com/post/25287498

> cross-posted from: https://lemmy.zip/post/19638259 > > > There are about 6 pages.dev domains spamming lemmy.world communities > > > > The volume is definitely inorganic, and is across a wide range of communities > > > > pages.dev is Cloudflare's site hosting which can be used for free - there are likely many legitimate sites that use that domain, but the current flood is suspicious > > > > chronicleresolve.pages.dev > > > > thefreedomproject.pages.dev > > > > versarch.pages.dev > > > > dailypulse.pages.dev > > > > newssphere-6fu.pages.dev > > > > iniko.pages.dev > > > > miniza.pages.dev > > > > orino.pages.dev > > I'm cross posting because @lenny_marlane@lemmy.ml seems to be doing the same thing. > > It might be an attack vector or something idk but better safe than sorry.

Not sure about this one but seems to be following same pattern.

@marvelous_coyote@lemm.ee

_{Anti Commercial-AI license (CC BY-NC-SA 4.0)}

Hey folks!

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

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

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

Edit: turns out it hides hidden posts.

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

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

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

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

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

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

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

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