I’m glad lemmy’s fetching seems to be better: once a community is on your instance its there and you get everything except stuff from servers you’ve defederated with.

thats what their site says, at least when ran through google translate

first I’ve heard of it, but I’m skeptical of their claim to deliver security fixes faster than firefox.

all you need to do is refresh the page after the error message appears and you’re golden, no big deal

deleted by creator

What would you do with that much storage?

It can be easy to be nose-blind to your own smell, trust me its easy to stink enough to be offensive to others but not notice yourself.

They’re doing you a favor by letting you know. Just take the extra moment and put some on in the morning. Just don’t overdo it and douse yourself in body spray; too much body spray is nasty too.

I havn’t looked into it yet, just using plain lemmy-ui for now, but it does look pretty nice

part of it was http signature expiration, showed up as

WARN Error encountered while processing the incoming HTTP request: lemmy_server::root_span_builder: Header is expired
  0: lemmy_server::root_span_builder::HTTP request
            with http.method=POST http.scheme="http" http.host=mylemmyinstance.com http.target=/inbox otel.kind="server" request_id=453c8a92-7bb5-4b7e-a4ad-212e91167d4e http.status_code=400 otel.status_code="OK"
         at src/root_span_builder.rs:16
 LemmyError { message: None, inner: Header is expired, context: "SpanTrace" }

in the logs, and that was fixed

the other part was some nginx config changes

they moved away from the allowlist and now only block some. federation with my own instance just worked after I got updated to 0.18.1 and adjusted my nginx config

they moved away from the allowlist and now only block some.