Notices by ij (ij@nerdculture.de)

After some days of opening registration on my @pixelfed server, I already have 11 active users.

22 users have registered via curated onboarding. That is: they apply for an account, need to verify their mail address (which they need to do also with open registration) and then I need to approve them.

Those 11 accounts that have been applied, but are not active, are a victim of gmail.com strict mail policy. Gmail was unhappy about the mails and refused them.
Now those accounts are in a stuck state, because they need to confirm their mail addresses before the process can proceed.

Sadly, there is no way to resend the confirmation mail from the web interface (as far as I know). @dansup is already aware of this and wants to fix that.

So, if you are waiting for your account on https://pxlfed.de/ - that's way.

In the meantime gmail.com is accepting those mails, though.

I've updated my settings on https://pxlfed.de to "curated account creation" and submitted the server to be listed in the directory on @pixelfed - maybe that helps @dansup in dealing with the load of new users when there are more instances to choose from.

However, I would like to have an alternative way of registering... but well, maybe another time...

@jope @batteman @codewiz Ah, yes, that 4G barrier... I avoid partitions >4G for important stuff like programs and such. For mass data I use larger partitions with SFS or so, but also doing backups do a second partition. Having a 500 GB SSD in my A3000 is giving you plenty of storage for backups... ;)

@jope @batteman @codewiz Uhm, never had good luck wie AFS/SFS/whatever... with FFS repair is sometimes quite easy, if you are brave enough to do it:
1) quick format the partition
2) run "Unformat" from like qbtools or similar
3) be done.

DiskSalv and other "repair" operations resulted in my issues, sometimes. Quick Format & unformat worked fairly well. Not always, but in >90% of the cases.

@Polychrome NFS or permissions on NFS?

@Sascha Ach!? </loriot>

@slothrop Naja, Prozesse noch nicht.
Ich wuerde aber gerne mal dahin kommen, dass wir von "der User meldet sich und wir springen" weg- und hin zu "der User moechte etwas und wir arbeiten es sinnvoll und konzentriert ab und behalten dabei den Ueberblick" kommen.

Wenn man es verargumentieren will, kann eine Neuanschaffung ja auch ein Change sein...
Ich wuerde aber "Request for Change" eher so sehen wie "bitte ein Port umpatchen" oder "User hat geheiratet und braucht einen neuen Namen" oder "bitte Software XY updaten"

Grad Diskussion ums neue Ticketsystem.

Da gibt es grad die Support Typen:
- Incident
- Problem
- Project
- Request for Change

Nun ist der Wunsch da, "Request for Change" nur noch als "Request" umzubenennen, um auch Anfragen fuer Anschaffungen etc. damit abzudecken.

Ich tu mich da etwas schwer damit und wuerde eher einen neuen Anfragetyp definieren.

Wie schaut es bei euch aus oder wie seht ihr das? Gerne diskutieren. Ich lasse mich auch durch gute Argumente ueberzeugen... 🙂

@TabeaRoessner @padeluun ich hoffe mal, dass da auch die eklatante Unterfinanzierung von freier Software besprochen wird. Weniger Geld für die US-Monopolisten, mehr Geld für OpenDesk, ZenDiS & Co!

@thomasfuchs Maybe I should save that GIF for the elections in the US... ;)

So! Darf ich eure Aufmerksamkeit für diese wichtige Meldung haben?!

Meine letzte Lebkuchenpackung wird gleich geöffnet!

Danke für eure Aufmerksamkeit und euer Mitgefühl! 🎅🏻

@dansup @pixelfed Well, erm, *cough* LDAP? ;-)

@dansup @pixelfed I'm looking forward to a new LDAP integration in 2024 as well! ;-)

@pixelfed @dansup No discord here, but Matrix would be an option... where to find the channel?

@KathiCat

Als die Nazis die Kommunisten holten, habe ich geschwiegen; ich war ja kein Kommunist.

Als sie die Gewerkschaftler holten, habe ich geschwiegen, ich war ja kein Gewerkschaftler.

Als sie die Juden holten, habe ich geschwiegen, ich war ja kein Jude.

Als sie mich holten, gab es keinen mehr, der protestieren konnte.

– Martin Niemöller

@dansup Just a question about LDAP integration in Pixelfed in general:

When having already an account in pre-ldap deployment, then deploy LDAP, will the user with the same account name be the same or another one?

That is: user "ij" exists in Pixelfed before LDAP integration and it does exists in LDAP. When the integration is done, will the LDAP "ij" be merged with the pre-ldap "ij" from Pixelfed backend or will there two seperated accounts?

@dansup @pixelfed Sure! I'm happy to help with feedback about LDAP! :)

@dansup @pixelfed I know that UI stuff is importing for user acceptance, but I'd be willing to contribute like € 100.- for a stable and working LDAP implementation with filter support and configuration via UI (and not patching source files like it is currently).

I just got my report #672 after 5 years of running a Mastodon with up to 25k users during the large influx from last autumn.

My impression is that this quite a low number of reports, which seems to be good.

How about other instances and their number of reports? Do you #mastoadmin's have lots of reports you need to deal with or do you have a low number as well?

@aral I'm running cleanup scripts on Friendica and Mastodon for years now to not grow too big. I was once the largest Friendica node out there and then reduced the (inactive) user count to below 1000 users.

Mastodon was an exemption with its large influx of new users where I grew to >25000 users.

In the past weeks 6.000 users were removed on nerdculture.de because they were not be used in the last 7 months.

But yes, Meta is a threat we must resist.