Cloudy days pose a real problem for solar panels. But a new innovation can convert UV light to energy—even if the sun isn’t shining.
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.
Hey this is test Twt to test receipt of a WebMention from an arbitrary Web-based WebMention 👌 ``` [00:24:21] <zack[m]> ok cool. can you give me a link to a post and i'll reply to it on my site and send a webmention ```
This is a test post to test Yarn.social receiving of webmentions
In the mid 20th century, whole cities’ sewage systems safely and successfully used fish to treat and purify their water. Waste-fed fish ponds are a low-tech, cheap, and sustainable alternative to deal with our own shit — and to obtain high protein food in the process.
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.
Jeremy Keith published an amazing article on how to install a progressive web application (PWA) on your phone. A PWA is a website that can technically be used as an application, as opposed to a regular website which is optimised only to be shown in a web browser. Jeremy's article is definitely worth a read if you want to install a progressive web application on your phone.
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.
The replies I've seen to this post are so frustrating. You can definitely use the latest Javascript features and APIs while still providing access to older browsers and devices. You don't have to provide special access, determine a list of supported versions, or build a specific version for those browsers/devices.
Use a proper HTML foundation and your site will work without Javascript in nearly any browser. That covers weird edge cases like the one described. Then use the module/nomodule technique so you can write the sleekest code with all the modern amenities and still provide an ES5 bundle to browsers that need it. Then your site will work in nearly all cases, no matter the device, browser, or bugs in your code.
<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>
IndieWeb Search, a search engine that indexes sites owned by IndieWeb community members and other related sites, has saved over 421,000 web documents. I maintain IndieWeb Search as a passion project. I wanted a place to search content from IndieWeb sites so that I could find articles and guides that were applicable to the community. Using the search engine, I'm able to get direct answers to niche, community-relevant queries such as how to set up webmentions with a static site or understanding what IRC is.
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.
A retrospective of how things have gone until year end 2021, and based on that some thoughts on where it should go in 2022.
Man, this is really sad to hear. Luckily, Search My Site isn't going anywhere right now, but costs steadily rising while usage remains steadily low is disheartening. We really need independent infrastructure like this, but we have to find a way to support it without advertisement.
2022 was once unimaginable to some web folks.
Wow. I wasn't even in web development yet and I've been using HTML5 my entire career. I can't imagine hoping the web would be subsumed by native apps or thinking it would become obsolete. That was the era of move fast and break things, though, so imagining something being stable for more than a decade must have been hard.
Between Google Chrome experimenting with “following” sites, along with a growing frustration of how social media platforms limit a creator’s reach to their
It's good to see more articles like this and I hope the RSS resurgence continues. As for non-technical people not knowing how to use them, what do you expect? Facebook, Twitter, et al have spent a decade designing and teaching users specific workflows that they control. That shouldn't stop us from trying to make the switch. Sites like About Feeds can help publishers and users, but publishers have to be willing to put the links on their page.
I used to have a section on my site where I shared a list of coffees I consumed. I was excited about this section because:
Congrats on the simplification. I don't want to throw a wrench into that, but just so you're aware, there are experiments with making official post types for most of the types you were posting. The IndieWeb wiki has pages for food/drink, watch, and read posts. I like the approach of making new types a note and just marking up additional properties. Then it's easy for you to manage it just like a note and consuming code can also treat it like a note and ignore the properties it doesn't understand. But there's always that possibility that the new properties gain traction and consumers start using them.
