As a matter of community building, lets make this a monthly thing 😊
Community gardening
As stated in our Wiki, we allow members to create their own communities as a way to encourage contributions, but this comes with the responsibility of active moderation. The site admins can’t moderate all communities and unless a posts gets reported, they might not even know about spam etc. Thus we will regularly prune seemingly abandoned communities.
The current list set for pruning is:
Buy it for lifevolunteer found- Dumpster Diving <- removed
- OpenSourceEcology <- removed
Rat Zonevolunteer foundBoard gamesvolunteer found- Solar Powered Vehicles <- removed
So unless someone wants to step up and take them over for moderation and active contribution, they will be removed at the end of the month.
In addition there are these two communities that attract quite a bit of moderation workload and the current mods need support with that (otherwise it might be better to prune them as well):
Technical updates
The originally planned move to a smaller dedicated server was only partially completed and ran into some issue with 8GB RAM being slightly too small for our current Lemmy database use. It might be just a a memory leak issue that should be fixed with the next Lemmy release, but given some related consideration I decided to try use another server with 16GB RAM instead. This move has not been started yet, but I will try to keep the down-time to a minimum.
This server also has a built in GPU that would likely allow automatic scanning for illegal images via Lemmy-safty. This image recognition script is fully local, so no data is transmitted to any 3rd party, but it will likely result in some false-positives (Likely NSFW / child themed ones, which seems not like a major problem for our instance). Any hits will be removed from the storage automatically so this will also protect our moderators from having to deal with such potentially traumatic imagery.
I also made some progress with the account integration between Lemmy and an XMPP/Jabber server. The idea is that you will be able to use your existing username@slrpnk.net
ID also for federated chat via the Jabber network. This is more secure than the internal Lemmy DMs as Jabber clients support end to end encryption (like Signal more or less). If in the future some Lemmy clients will add privacy preserving UnifiedPush we can also support that via this XMPP server.
I also started trialling a Movim web-client for it, which besides being a nice chat interface for private 1:1 and group chats, can also act as a long-form blogging site (kinda like Medium or Substack) for our members. Lets see if there is an interest in that 🤔
In theory bridges to Matrix, Discord, Telegram etc. could also be added, but it will need some more testing and might not work out. Voice and video calls will also initially not be supported due to some technical issue, but I plan to fix that ASAP.
Draft code of conduct
I am also still looking for feedback on and maybe some contributions to our incomplete draft code of conduct.
Open discussion
If you have any other topics related to our community here on slrpnk.net please comment below.
No idea to be honest. The only thing I could imaging is the location of the VPN. Hypothetically if you are EU based for example, but chose a US based location for your VPN, then a non-VPN connection would be much faster as our servers are located in Portugal.
I am actually connected to a VPN server in Portugal! Are you Portuguese by any chance?
Also, there is something wrong with slrpnk.net, I think? I am seeing some behavior that I used to see on lemmy.world, namely, replying is taking forever (https://lemmy.world/post/90611). I click on “Reply” and it keeps on spinning. I don’t remember how he fixed that, but I think it had something to do with the config file. I think he had debugging enabled or something to that point?
EDIT: It seems like this only happens from the Inbox screen.
EDIT2: Found the post to which I am referring: https://lemmy.world/post/288652. TLDR: “Federation debugging” was enabled. Should be disabled.
EU citizen living in Portugal.
It’s definitely not the “Federation debugging”, but I also noticed some odd stalls from time to time since moving the main database to a different server 3 days ago. I think I’ll need to do some more database tuning on this new server as it isn’t quite as CPU performant as the previous one. Edit: ok did some database tuning, lets see if that helps.
Edit2: Looks like we are occasionally running into this issue (as many other Lemmy instances it seems). I guess the previous database server was just fast enough to usually respond in < 10s, and on the new one it happens more frequently and thus is more noticeable. It doesn’t look like this can be fixed by tweaking the database and rather needs the mentioned Lemmy code improvements that are likely coming in version 0.19 sometimes in the coming weeks.