Microblog

I hate it when I think someone texted me and it turns out to be spam. It's happened so many times now that I'm not sure why my brain keeps giving me the dopamine hit from seeing the notification badge.

social.lol/@bw/113201221791476556

What is the simplest solution for persisting user data?

I frequently run into a situation where I’ve built a neat little frontend app but need to persist some user data. My first instinct is to stick it in local storage, which is cool and totally works. But it’s at risk of being deleted by the browser and it’s not portable to other browsers or devices.

Things I’ve used:

- PHP/MySQL
- PHP/SQLite
- NodeJS/SQLite
- JSON files
- Userbase (third-party service)
- I’ve even used paste.lol as a BE

social.lol/@bw/113181742422111501

HTML for People update:

- Finished a round of proofreading
- Added alt text to 70+ images
- Linked up a ton of resources (used Perma.cc on some of them to prevent link rot)
- Tweaked typography and color scheme
- Repressed symptoms of imposter syndrome enough to get the above done

Still a ton more to do but it’s coming along. I’m looking at a release date around November or December probably.

htmlforpeople.com/

social.lol/@bw/113074626338570867

I wonder if the use of credits is a good compromise for fighting subscription fatigue. It allows a service to make ongoing income in a way that aligns its interests with customers.

You’re paying if you’re using it, but not if you’re not. Of course, credits need to be straightforward—as in how much money they represent, or what clear benefit you get from spending one.

The last thing I want is every web app selling me a bag of gems and gamifying everything for optimal revenue.

social.lol/@bw/113063200530959886