Tbf forks should be separated in the repo view on GitHub from repos you’ve created
Tbf forks should be separated in the repo view on GitHub from repos you’ve created
Forgejo uses SQlite
That’s a red flag
Not very convincing without reasoning
It’s nice and all, but in a GitHub/GitLab PR workflow world, your commits are mostly squashed and rewritten by the remote, so it doesn’t even show up on main
So there’s really only a benefit if you don’t use squash and bother with maintaining proper commit messages in your PRs
If you take the largest instances and sum the subscribers you’re probably 99% of the way there for most communities. There may be outliers, of course
Basically an old-school, minimalist phone
Next level stupid
Except on /c/reddit ?!
This is very different. Chrome sends all of your text to Google
Pretty crazy that Firefox has builtin local translation now
Git has pre-commit hooks?
I get that they’re embarrassed to mention it, but it’s still worth a bullet in the release notes I reckon
The speed ups are definitely understated in the release notes if they are that significant
I mean there’s no way this is intended behavior. Others are confirming as well. You can just delete others’ comments along with yours (or at least their appearance in the thread)
It does for me. I also checked on the website, not logged in. feddit.de instance
Lemmy URLs suck, tbh. It’s just an instance-specific post id. They should definitely offer speaking URLs at the very least, ideally cross-instance
Not defending spez, but their business model was not designed to support third party apps, that much is true. They needed a proper model to share profits with third party apps.
How they went about “fixing” that was completely dilletantish and dumbfounding, though. Now they’re not getting any of that potential extra profit and lost a significant amount of users on top
https://github.com/discuitnet/discuit