Web developer and Studio Lead at Deloitte Digital in Düsseldorf, Germany.
Digging up some Beakerbrowser hyperdrives from a couple of years ago. Cool to see some are still there.
Was able to send my first Beakermention using Sentamalins application. Yes, this is an implementation of webmentions in Beaker between Hyperdrives. Still early days. But seems very promising.
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.
One of the best things about #Hyperdrives is that we are still able to edit our own content even after publishing. Something some other platforms have difficulty with, even-though they themselves realize that many people would like to edit their posts.
Since https://
Joined the @BeakerBrowser profile #Hyperdrives with my own: <hyper://86fcdeb5ebb4a720f4e5b66fbab67a8051ddf09659cd2622cdeb0de8c4d41267/>
You will need Beakerbrowser to open that link.