Web developer and Studio Lead at Deloitte Digital in Düsseldorf, Germany.
The Indieweb wiki page on Bookmark (https://
Thanks for sharing your thoughts on the DWeb. You point out some true challenges that this exciting Web Space is facing at the time you wrote the post and is still facing today. About the "phasing out" or disappearing of the data on the IPFS network; I personally think it's kind poetic almost that for as long as someone is interested in content, it will always be there on the IPFS network. You only need one node with the content to have the data to be able to reach it. Unfortunately perhaps, the https://
Great article, especially from my point of view of being a Surface Pro 4 user since 2014, I can relate as well.
But I'm not like you. For my day job we got issued powerful Macbooks with i9 CPUs and 32GB or RAM and there are no complaints there, perhaps except for that these machines are almost completely locked down and I don't dare doing anything personal on it.
So I only use the Surface for my light-weight after-hours dabbling and messing around with shell scripts and JavaScript code. The only times I really see it struggle is when I'm running Beaker Browser and Patchwork and Syncthing at the same time. But I learned to be patient and just keep one thing open at a time. And I don't do Desktop Apps. I wished I could learn how to program that. Getting some inspiration from the people over dabbling with Gemini and Go and Rust, there's even a really cool client programmed in C.
My question though: would Microsoft allow you to build Windows 10 for x86–64 in their fancy Azure Cloud? Perhaps that's what they are aiming for? Would that be an option?
Since the p2p network relies on people hosting and seeding I do see how a "boolean flag" for checking if the visitor is "hosting" would be a nice thing to have for some hyperdrive owners have put a lot of effort in gathering and publishing their content on the network.
And therefore I could understand that this could be used as a form of "paywall" to control the access to "freemium" content. I think this would be only fair if used in moderation. To call it "extortion", is a bit exaggerated as the whole network literally depends on us sharing each others content.
However, there are indeed privacy related issues. This API, together with our public IP addresses could be used to create a way for some hyperdrive owners to start tracking their visitors.
If the "gratitude" feature would be part of the main Beaker interface, within Sharing Hyperdrives, I will leave open here.
Perhaps it should be made "optional" for the visitors, within the permissions dialog, to disclose to the owner of the hyperdrives to announce that they are hosting the drive or not. Beaker browser itself should not show any explicit banners or notifications. That would be up for the hyperdrive owners to interpret.
Technically, I would even add a datetime stamp so there are more variants possible in how the hyperdrive owner can process is visitors are seeding or not.
James Tomasino wrote about his experience with implementing #IndieWeb Webmentions on his Gopher blog.
To bridge my webmention from HTTP to Gopher, I'm web-mentioning his post through the Floodgap Gopher proxy. If you're using Lynx or another Gopher-capable browser, open his post here: gopher://gopher.black:70/phlog/20191223-webmentions-and-microsub