It would probably be useful, but harder to collect, a summary of:
- Primary/intended topics or users (eg, tech, politics, regional, etc)
- Any unusual moderation patterns
- Most/least blocked
this post was submitted on 07 Jun 2023
147 points (98.7% liked)
Lemmy
12538 readers
1 users here now
Everything about Lemmy; bugs, gripes, praises, and advocacy.
For discussion about the lemmy.ml instance, go to [email protected].
founded 4 years ago
MODERATORS
Shooting for this. It's not beautiful but it's not ugly:
Gonna have to dance around the i8n library for this PR, but it shoudl be possible.
load more comments
(1 replies)
Great work! Can you include the instance description in this list also?
Also i would love to see country but that's doesn't seem to be included in the Lemmy app. I guess you could do a ip lookup on some service to see country if you really wanted to.
load more comments
(1 replies)
It says i can't downvote on beehaw , but going to this (beehaw community post) and downvoting workds.
load more comments
(4 replies)
are manual additions allowed? our host's security blocks some bot traffic and is currently not playing nicely with the stats crawler
load more comments
(2 replies)
I'm a little bit confused by the federation thing. How would I let my instance talk to any other instance except the ones I blacklist?
It's documented here:
By default users on an instance will be able to talk with communities/users on all other instances. This only changes if the instance admin puts hosts in the allowed list or disables federation.
If you add instances to the blocked list then users will be able to talk with all other instances, except those on the blocked list
Oh I see. I had put Lemmy.ml on the allowed list and never intended other instanced to not be allowed.
Fixed, thank you!
there's an option in the admin panel to block certain instances
The new user registration doesn't map to the recommended setting of admin approval only. There have been massive spam account registrations waves in the past and if you can't monitor your instance 24/7 this is the only way to prevent having your instance blocked because of that.
The NU field is determined by checking the registration_mode field in the API. If that's set to closed then I say No. Otherwise, I mark it as Yes.
So if it's open or require_application, I list it as Yes.
Is there an issue with how I've set this up? If so, please name a specific instance and what it should say vs what the table says.
Ah, I managed to mis-read the table. Seems ok for my instance (slrpnk.net). However we do allow users to create new communities.
I just rebuilt it and fixed the NC field. Please let me know if you find any other issues
Seems ok now.
Unrelated: maybe you can query the server location? Especially if it is in the EU or not and thus falls under better user data protection (GDPR)?
thanks for the suggestion. I'll add it to this ticket: