toothbrush

Curious to know if anyone finds it usable!

https://github.com/toothbrush/Spotiqueue

Totally agreed. That's one thing I find sad living in Australia: I barely see any (I don't think I recall seeing any in the past 2 years).

What i used to do back in the day, and appeared to work fine when i tested this weekend, is so-called flowed mode. [1] I think it's a controversial feature, because it's a brittle hack, but anecdotally an email i sent this weekend as a test displayed fine on an iPhone.

And indeed, i'm totally with you on wanting to use/send text email but not look like a freak with weirdly broken 80-char lines in paragraphs.

1. https://rinzewind.org/blog-en/2017/a-small-trick-for-sending...

Thank you so much for the kind words. It really means a lot to us.

> comments through Github is interesting in a brilliant way

Thank you! Honestly we're just cheap/lazy – we really wanted a super low-maintenance blogging platform, and static pages are amazing IMHO. This gave us "all" of both worlds, sort of.

I apologise if folks have already seen it, since it actually (surprisingly) got a bunch of traction here on HN over the weekend, but that has been our quarantine project, for what it's worth!

And here i was thinking HTML was a bit like LaTeX – mostly whitespace-agnostic! Just shows you what spending too long in academia will do to you.

Super interesting, what you're saying about the OpenType Sanitizer – i'd wondered why it appears you can't use bitmapped fonts in browsers (although another commenter claims you can – i don't know either way).

I'll have a look at Bits'N'Picas, thanks for the heads up!

However, your other idea is great! You might enjoy https://paschke-images-test.s3.amazonaws.com/welcome.html ;)

If it's really illegible, i wonder if there isn't some other rendering bug happening – we admittedly didn't do much testing other than Chrome/Safari/Firefox on latest macOS. And i've seen some pretty weird glitches with this kind of custom font, e.g., https://github.com/jdan/98.css/issues/13. If something is truly that broken feel free to hit us up at webmaster@ with a screenshot, we'd appreciate the bug reports!

I see this more as a "just because we can" art project, than anything else.

EDIT: it also occurs to me that i have tons of respect for the hours of effort that would've gone into making fonts back then be beautiful at such small DPI. I think it's a good example of constraints producing interesting/good/impressive art. But i should avoid waxing too philosophical!

We have indeed still got a bunch of visual glitches we couldn't iron out, including the one ~saagarjha has reported to WebKit! We had assumed it was our font being broken, but i'm keen to follow that one.

Otherwise getting hinting right on all browsers in high-DPI has basically been impossible. Maybe we should simply recommend everyone use a Windows 98 User Agent ;)

We were making silly games in Visual Basic 6, because that struck us as a cool thing to do. However, it's hard to show them to your friends, when they all use macOS or Linux. Plus, we didn't want them to miss out on the nostalgic feeling of booting up Windows 98. So, after a lot of blood/sweat/tears and a physical copy of the MS Windows 95 Resource Kit book, we finally can ±roughly automatically install a Windows 98SE machine in QEMU, load it with our games and some settings, and then upload it to S3 to be "played" with copy.sh's v86 engine.

Without further ado: https://paschke-images-test.s3.amazonaws.com/welcome.html

This comment boggles the mind. I would wager that probably for thousands of years, cooking has been a communal (if perhaps gendered, good riddance) affair, and only with the advent of the unemployed housewife of the 50s suddenly the kitchen is seen as this private affair.

But i guess i'm the wrong person to be commenting, because generally i'm no fan of all this extreme individualism :)

> However, I think it's not that easy. 4 digit PIN, one account, I guess it gets flagged fast if someone tries to brute force it. You should try it, hm?

Their security page says 3 incorrect attempts means you need to call up their call centre. But as you point out, how hard would it be to socially engineer your way in.

What would other ethical webmasters here do? Only use HTTP access logs?

EDIT: to be clear: i could also write a bunch of tooling myself to parse access logs or report events to a backend, but that feels like a lot of work + reinventing the wheel + maintenance/security scare.