You should! You don't have to be qualified to have something interesting to say - and you're doing it, so you know more than most people!
It matters a little bit - Google measures performance on real devices through CrUX, and that feeds into their rankings - but not much. There's no real incentive to go for a Lighthouse performance score above 80 or so.
CDNs are common - but are they really necessary? Is a single origin the performance pitfall many think it is?
I use https://fedoraproject.org/coreos/ for my server/website. My host doesn't offer it as an image so I have to upload it myself, but I use an ISO I made with the CLI to automatically set up everything anyway. It works pretty well, I configured auto updates and I can just forget about it.
The MusicBrainz project sends thousands of emails every day to its diverse contributors. However, the existing email system was limited, having organically grown over the project's lifetime. It could only send emails in English, and only in plain text. The experience that new contributors got could ...
You missed out this fairly important bit re go-git:
it is not supported or packaged because it is not fully compatible and could corrupt Git repositories.
As far as being tied to git proper, that's because there is no drop-in alternative implementation that implements all the functionality that you need to run a Git server. Right now, Git proper is your only option. That might change as gitoxide matures, but that could take years.
Yeah, or even the inbox in lemmy. It's a surprisingly common thing.
Regarding your first paragraph, this results limit is per page. To get the next page, you take your timestamp of the last item and use it in from_time, or whatever you've called it. It's still a pagination technique.
Regarding custom sorting, some of the techniques in the article can do this, some of them can't. Obviously timestamp based pagination can't, however the ID-based pagination that I mentioned can.
This whole article was sprung from a discussion of exactly that case, because users often simply don't delete notifications. It's very common for users to have years of undismissed notifications stacked up under the notification bell, and it's not a good experience to load them all at once.
They fixed this in version 0.19 pr #3872 (note that the cursor here is a way of hiding a post ID to continue from, as far as I can see).
Also, lame article? 😖
Not a problem because passwords are hashed, which means they take up a fixed size, and you should have form upload size limits anyway.
Pagination is a core part of many APIs, but many methods have hidden pitfalls. This post explores these common issues.
