The systematic thinking in our industry is that settings are the result of design failure. As designers, our goal is to create product experiences that don’t require any adjustment by the user. So offering customization options is often seen as a failure to make firm product decisions. I think there is a misunderstanding about what settings really are.
I always spell it 'wierd' and then have to fix it
I'd love to add push support to my social reader. Getting notifications for webmentions would be really nice. Sites where you kick off some kind of job/process could notify you about changes in status, sites for delivery tracking could notify you about status updates.
And I assume the user is always in control so they can determine which notifications they receive and the priority of each type of notification.
Whoa. This looks like a super cool technology. It's made out of vegetable waste, enables collecting solar energy even when not in direct sunlight, and the panels are flexible so they can be integrated in more than just flat windows. I'm really excited about these and how they could enable easy solar energy.
This is a test post to test Yarn.social receiving of webmentions
Each reason points to a deeper problem: our economy’s inability to value the right things.
This is a fascinating article about a low-tech solution to alleviate some of our climate problems, but with a depressing ending. Political leaders, technologists, and capitalism itself don't value technologies that aren't flashy or are developed and iterated on by native peoples.
It reminds me of my own field, web development, where people are drawn to highly engineered, flashy toolchains instead of working with the systems that is already present (browsers, HTML, DOM APIs, etc). I think the author is right that people want the solution to be separate from the base system. People like the idea of starting from scratch to try to control all the variables, instead of working around issues with creative solutions.
Nice work! If you want to dive even deeper, there's more to PWAs. Adding a ServiceWorker would allow you to cache your assets and even enable offline support.
Jeremy Keith has written a ton on the topic that I've found really useful.
This is the first I'm hearing of whostyles and it sounds really cool. I might try to implement one for my site when I get a chance. Thanks to Maya for posting about this on Lemmy.
<p>As more and more companies begin dabbling with blockchain tech, I'm increasingly bemused by just how blind they appear to be to the growing consumer concern over the same space.</p>
Check out https://searchmysite.net/. It's another independent search engine, though focused on independent websites in general, not just IndieWeb sites. Parts of it are in python and the developer has been looking for other contributors. Maybe your two projects could collaborate or they've picked up some ideas that you could use.