Fun fact: while not being exactly like what karma was on Reddit, Lemmy does store the total count of upvotes-downvotes your account has received. You probably can’t see it because it isn’t shown by the frontend (the website you see), but the data is indeed there.
Ansible guide. I didn’t follow this one myself but the guy who set up my instance said it was pretty easy
https://github.com/LemmyNet/lemmy-ansible
…or join a smaller instance.
Also @OP, remember that you can edit titles.
Same, since I updated my instance to 0.18 Jerboa doesn’t work and instantly crashes.
Upvoting this post from Connect for Lemmy. Actually I think I still prefer Jerboa. Unfortunately it has stopped working since I updated my instance to 0.18 so this will have to do for now.
I am working on it! My team and I are working on this issue as we speak (I literally tabbed out of VS Code to answer this) and we plan to roll them out to our modded instance in a matter of days, it’s our top priority.
Extending support for this feature to the wider lemmy codebase is not paramount to our roadmap, but we will certainly make a pull request once we are done. If the lemmy devs will like our implementation and decide to adopt it we will definitely be very glad to help them doing so.
EDIT, 10 days after: only now I see that the links was about post flairs, not user flairs. To clarify, I am working on user flair, no idea if and who is working on post flairs.
Oh I wasn’t aware of this. Very tempting. Now I lowkey wish they miss the deadline on one of the six accounts I requested the data for, so I can do some European style trolling.
Not sure if there’s any lore behind it but I’ve also seen this. The beehaw admins seem to have an habit of making problems go away by pressing the magic button.
My team and I are planning to start working on an AutoMod bot in the near future. It’s going to be built with our custom instance in mind, but the code will he open source for everyone to use.
If I’m actively subscribed do I still get the content […]?
No, the whole point of defed is that your home instance stops “listening” to the updates of the defederated instance. So you’d stop getting updates from any community hosted on @sh.itjust.works period.
This. Defed is not the magic weapon that will solve all your problems. Captcha and email filters should be on by default though.
Couldn’t the protocol be updated to be more compliant with the right to be forgotten? Something like, when a user deletes a comment it gets deleted from the DB of every federated instance. Sure enough, admins might have made backups and that would theoretically go against the GDPR but still… you can only apply these laws to a certain extent. It’s the same as you posting a picture on Facebook, me downloading it and you deleting it afterwards. Even if you were to make a GDPR request to Meta you still couldn’t get the picture on my PC. But that’s not Meta’s fault, they can’t do much about that.
I STRONGLY ADVISE you against doing the following, but for educational purposes, just rename the file .husky/pre-commit to anything else. I called mine _pre-commit and slapped a README next to it documenting what I did. This will turn off the husky pre commit job, which is what runs prettier.
Not sure if it’s the same issue you are having, in my case prettier failed to run and that didn’t allow me to commit at all.
The pain of working on the lemmy frontend. I “fixed” this by turning off prettier.
Friendly reminder that if you aren’t hosting your own instance you don’t have “your own Reddit”
…nor blackjack, nor hookers, for that matter…
Bless! I really like this layout, it’s great. Thanks for sharing.
I like it so much that I could consider including it as the default for the lemmy instance I am building.
I never considered doing that, actually. I always felt like PRs where only useful when you actually had something to show, otherwise you are just spamming a project with useless ideas and "what if"s.
But this is also my first time contributing to an open source project. Learning experience.