Seems like a reasonable size limit for a modern phone camera picture.

Really they have had a ton of outages throughout their existence compared to other instances but at some times it was better and at times it was worse.

I can’t really confirm those uptime monitor results, for me it hasn’t worked a single time in the last few days.

Not sure why but feddit.de was broken with themed errors for a day or more and now just shows a white page with Server error for the last 2-3 days. Even status.feddit.de just results in a timeout.

And many mail providers block all incoming mail from dynamic IP address pools.

sh.itjust.works is still on 0.18 so it shouldn’t be affected by the 0.19 federation bugs.

Absolutely, which is why all those notions that the extreme anti-mod crowd on here has about an admin-free forum are fundamentally impossible even if you ignore spam problems.

And even if there wasn’t they have full database access so they can wipe whatever they want (given the technical knowledge required). It is also not possible to prevent that, no matter what Lemmy developers implement.

No, proxy_pass is the URL for the backend, that should be a valid IP, it is okay to use it in listen, where you have [::]:80 (the extra square brackets are just to distinguish the colon between IP and port from the internal ones in the IPv6 address).

http://0.0.0.0:1236/pictrs/image/730840b6-d6ec-4a40-8668-36b89c6c1d33.png

https://0.0.0.0/

proxy_pass http://0.0.0.0:1236;

0.0.0.0 is not a valid IP and thus not a valid URL. 0.0.0.0 is a special value you can use as a listen IP to listen on all IPv4 local interface addresses (:: is the IPv6 equivalent which is the short form for the IPv6 address that is all zeroes; that one will listen on both IPv4 and IPv6 local interface addresses so you should prefer it 99% of the time in 2023) but you can not use it for an actual connection.

This most likely means the storage on the instance you are trying to use is full.

Then you should report a bug to Keepass if they show a warning at login fields but not at signup ones.

When inspecting the signup password field and the login password field both seem to have a limit of 60.

At most you could probably list instances that the current instance tried to federate with but failed. Since instances only try to federate with instances where users have a subscription to a community on the other instance there might be instances out there that just never even tried to federate with a given instance that still have it blocked.

Thanks, that was very helpful. I was basically hoping to find a document that covered the second half of your comment.

I don’t have any concrete plans to work on Lemmy so far but I was thinking about the possibility of tags for posts (especially but not only NSFW ones) and filters that work on those tags. Of course if you can rely on the author to tag everything that would probably just be some new extension to the post object but I was considering the option of something similar to the tag systems on adult image or story hosting sistes or Steam where third parties can add, modify or remove tags/metadata about the content in some way too.

It sounds to me as if something like that would probably be modelled similar to top-level comments in the AP ecosystem (but of course displayed and used differently).