+1 for Migadu! I'd been a paying customer for Protonmail for a few years now but stuff like this had slowly been pushing me away. A few months ago I set up Migadu with my own domain and it's worked without issue ever since. Another plus is that I can finally use my own email clients without having to deal with proton bridge
It seems slightly disingenuous to refer to this as “Spotify Developer Tools” while linking to a script specifically for deleting (or unfollowing, rather) playlists. That said, if this was expanded into some slightly broader wrapper around more of the API’s functionality, that could be really useful!
fwiw opening the article in an incognito tab usually does the trick to get past the article limits. That said, you're right on the money about how badly it sometimes seems that medium doesn't want me to ever use their service
I’m a happily paying user of 1Password personally, although I’ve used bitwarden in the past and it’s great and self hostable too. I just prefer 1pass for its fast updates and great integration with the Apple ecosystem. If you wanna host your data with gdrive or the like keepass is less polished but also very solid.
Hard to be completely sure without RH or the family specifying, but browsing r/WSB’s thread on the incident, looks like a lot of people have encountered this exact same issue and had it clear up the next day
I appreciate the no-bs lightweight website sentiment as much as anyone, but I think there's also something to be said about drastically improving readability with some line-height and font styling.
write.as does support custom CSS and JS, so you can, in theory, make look however you want. It isn't quite as light as Bear is, but it's no Medium either.
oh interesting! Yeah I actually hadn't been to their landing page in a long time, totally agree with your there (and feel like it doesn't do their actual blog product justice - to my tastes at least their blogs are perfect, low-key but elegant and very readable).
It looks simple, but isn't technically minimalistic with 77KB .css and loaded fonts. The first page load was actually visibly slow with the fonts repainting in a different typeface.
Sans serifs are overused because they look better on low resolution screens. If you haven't had to use a low resolution screen in a while then you are one of the privileged few.
At small sizes, like 8–13px, sans-serifs look better than serifs. And user interfaces and websites used to be that size.
But for 16px and up, which is what websites of today use, serifs are perfectly fine even on 1× displays (though sure, they’ll look better still on higher-DPI displays, but so will sans-serifs).
I should clarify that it depends on the font. Sans-serifs tend to have fairly even stroke width, but serifs tend to have more variable stroke width, and if the thin is too thin, you get a terrible font. That’s a common shortcoming of serif fonts, and Garamond demonstrates that, being quite unsuitable for screen use below 20px, maybe even 24px. Others like Georgia don’t suffer that weakness.
Are you sure that "websites of today" use 16px or larger universally? HN appears to use 9pt Verdana, which I believe is equivalent to 12px on my Windows system if my math is correct.
Georgia is a terribly underrated font. I'm sure it's heavily hinted to look good at small sizes, but even at large sizes it has an elegance that is lacking in e.g. Times Roman.
This sounds like it ought to be a job for pixel-density media queries [1] in CSS. I doubt this happens often if ever though, because designers. Anyone seen this approach in the wild?
I guess I specifically mean the default browser serif font. There are sites that consciously choose a serif typeface to convey some sense of "we are serious content," but you may notice that none of them use the default browser serif font (except as a last-step fallback).
If I see default browser serif, my immediate thought is "either this is an amateur or something is broken."
I don't have data to back it up, but I've understood from typography gurus that sans-serif fonts are great for signs, short blurbs, etc. But for long (multi-paragraph) reads serif fonts reduce eye fatigue. I think blogs typically fit in that category.
Georgia is a decent serif that will typically be available.
Or just `font-family: serif` which will most commonly be Times New Roman or similar, but will be whatever we prefer for those few of us that set the default fonts.
Seems about par for the course. I'm sure a lot of policy would have to be enacted to allow something like that, and my company (also a large tech company) announced something similar not too long ago.
