I find this sort of thing bothers me often enough that I've disabled downloadable_fonts. I think of the web as a place where I read things, so custom fonts that hurt readability are undesirable. I get why designers want a unique style, but I rarely want that as an end user.
Magic links breaking my flow is my top issue as well. My inbox is distracting: don't send me there. One affordance I've seen was a site that detected I was using gmail and crafted a link like https://mail.google.com/mail/u/0/#search/example.com, which brought me directly to the email I needed, while hiding everything else. I think it did a MX lookup to guess my provider.
I wish magic links would go away, but if they need to stay, that approach was the least terrible.
If you're doing this sort of license analysis, try a license detector I built. It tries to guess which license was used and diff any changes. Lots of licenses are small changes from others, so it usually makes multiple guesses.
I think Mastodons API-centric approach has lead to user-friendly results that feel fundamentally different. Mastodon gives me an in-order timeline of just the accounts I follow. I configured it to hide images by default, reduce animations, and to require user action to load more posts (no infinite scroll). It feels so much more tuned to my well-being versus apps that are tuned to maximize adverisement views by trapping you in doom scrolling.
You don't need to be logged in to see content on Mastodon. There are privacy settings that could hide content from non-followers, and mastodon users may be more privacy conscious, but log in is not generally required.
> Random bits are incremented sequentially within the same millisecond
That surprised me. This provides sub-millisecond sorting when the same generator is used (I.E. same process) but doesn't hold across different processes. So you still have unsorted sub-millisecond events in a distributed system, so the concern isn't fully eliminated. It looks like a decent performance optimization though since it reduces calls to generate random bits.
I ended up reading RFC 9562, which talks about a bunch of ideas and tradeoffs with this sort of sub-millisecond sorting.
Yeah this basically negates a lot of the advantages of a unique id IMO:
- scaling ID generation for a distributed system and avoiding a synchronization point
- optimistic locking and idempotency keys
Really cool, I think there are places where something like this could be really useful.
It could be cool to pair this with a SSR backend and package it into a Electron-like desktop app. You'd get basic UI, but it could be very lightweight. The biggest complaint about electron has long been memory usage. Could work great for kiosks too.
reply