@dessalines Works
Announcements
Official announcements from the Lemmy project. Subscribe to this community or add it to your RSS reader in order to be notified about new releases and important updates.
You can also find major news on join-lemmy.org
What do users do if they want to enjoy !hentai@lemmynsfw.com? Will such things be added to the whitelist? I can't seem to access it
Does it make sense to use a single-user instance like I do with pleroma? Probably not at this stage since it would require manual whitelisting, right?
You could I guess, but it'd be a bit weird since lemmy is built around communities.
In a hypothetical future world where there are many vibrant lemmy communities, a person with their own instance could participate in each without their identity being tied to an instance owned by someone else. You could also host a com related to a project you maintain that would be open to lemmy users form other instances, etc.
There is also the problem of having your federation choices made for you. If you use a federation instance with good moderation policies, they also likely do not federate with instances that do not. That's perfectly understandable and I support any instance owner doing that, but I would prefer to make those choices myself.
At this point it might be premature, but maybe this is a use case you want someone kicking the tires on.
Please allow federation for hive.atlanten.se
It looks like you already have federation enabled, but if you're having troubles you're probably best off going to [the support community for assistance at !lemmy_support@lemmy.ml
Thanks! I’m just missing a bunch of comments (but not posts) from Lemmy.ml. I thought lemmy.ml were running on an allow list? Might be something else thought.
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
good tip! I upgraded to 18.1 now. Hopefully fixes the missing comments.
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
Brilliant. i think both were fixed with the ansible update. Thanks for helping out phoenix!
Not sure if you are also knowledgeable about wefwef, I have another question: I have installed wefwef on my host. Works great! Except I can’t get watchtower to update it. I have to do a manual restart of the wefwef constrained every time. I’ve tried to increase the wait time, but no luck. Any tips?
I havn't looked into it yet, just using plain lemmy-ui for now, but it does look pretty nice
I recommend it. It’s a great smartphone frontend. Still missing some small features, but super great usability.
they moved away from the allowlist and now only block some.