Yes, there’s no current hooks provided by django-wiki for user registration etc. I have opened requests to add them and I’m planning to adjust the procedure further then. I could also extend the django-wiki myself, but I have my hands full already with my other projects.
Ultimately the best would indeed be some sort of lemmy oauth system to register. I’m hoping this might be possible at some point in the future. This kind of thing requires more developers jumping in and this is partly why I make these posts as well.
While I love Dokuwiki as well, the fact that it has a slightly different markup language would be a stumbling block for users moving info over. Also, django-wiki is python, which I know and can extend, while Dokuwiki is php, which I don’t. :)
Unfortunately profile changes do not federate well at all currently. Very inconsistent federation so no proper solution currently. Hopefully this will resolve at the software matures.
It’s a fine balance. A service like this needs so many talents, it’s very difficult for one to know all of them. You need 1. a infrastructure engineer/linux sysadmin, 2. an API/backend software dev, 3. a Frontend/GUI dev and a 4. Database Engineer/Administrator. These 4 are very very difficult to do well in one person, since almost each of them has infinite depth.
It seems like Firefish developer is good at 2 and very good at 3. That helps attract people to the software because it seems to fancy. But that sets up for failure, as its popularity becomes its own undoing, as the infra and/or the database cannot cope, and then the hapless developer is left running around like a headless chicken. I feel like similar issues are affecting kbin at the moment.
But the opposite is also not great. I’m great at 1 & 2, can kinda handle 4 but I absolutely suck at 3 (UI). As a result, while I can run a custom service with 200K accounts reliably, I can’t make it look good for shit. To cover my failings, the backend and the API are completely open, and I’ve invited anyone who wants to make an frontend, no questions asked. It’s not perfect, but it works.
The scope of building a large webservice is so large, it’s impossible for one person to handle it alone. But it’s also very very difficult to find competent and trustworthy people to cover the aspects you cannot. Especially DBAs! DBAs could be considered like the healer in a “Holy Trinity” game (Tank/Healer/DPS). It’s the role everyone needs but very few enjoy playing.
I wish firefish luck, but I doubt moving to a different DB is going to solve this issue. I’m honestly surprised this is the approach they went for, instead of just tuning postgresql.
Reddit threatening to ban /r/piracy made me setup a failover in raddle. Raddle restricting sign-ups for months made me switch the failover to lemmy.ml. Reddit protests made me setup lemmy.dbzer0.com and make it the primary location for /c/piracy
Use shampoo, and conditioner to avoid split ends. Cut the ends every half a year or so to avoid looking frizzy (ask your friends or a haircutter for advise). You can use hairbands. In fact you can just use a hairband just for the hair in the front to allow you to still have to mane.