Web developer and Studio Lead at Deloitte Digital in Düsseldorf, Germany.
1 min read
IPFS CID: QmYc27yb1A6NXi8tag1kTK3qJhQgKoEgshvLvaWCLidms4
https://
Hyperdrive: hyper://7ee7976f578c0a5256c8892fe522b5f08bcf36aef31ac5b97d99bf5289417db1
FWIW: I'm mirroring the #Bellingcat Ukraine TimeMap now also on a Hyperdrive; if you know what it is, you can help seed the data. The address is at: hyper://a8e160046a8fc5c171e9135d74ee785d4f74794af6d867633061899cbe506a12/
1 min read
The map is available here: https://
The TimeMap data is powered by three JSON files.
To help distribute the data, the files were imported to IPFS.
The three JSON files are now available in IPNS namespace:
k2k4r8k7lcogpmkq9mkf3ykg1rexvhmxcinz5z91k8v49gbem6ivjp1v
Due to peer-to-peer decentralisation these files are available through active IPFS gateways:
https://
https://
https://
https://
The data is now also available in this hyperdrive: hyper://a8e160046a8fc5c171e9135d74ee785d4f74794af6d867633061899cbe506a12/
See https://
Note that these are snapshots of the state as it was released at that time. New data will not show up in these files due to the immutable state of the files.
QmYu2zM9YQBNs5DrkFhDpjCTQTfoZkuPoKYUSWP1urnHKx
https://
Here are the IPFS CIDs to the three JSON files powering the data used in the map:
QmQa6feYmnpZKC72QNoSsipq1TgevaKmrVgZuWuaqXwCt5
QmUxJfkVPUxYQ9XhW2dqUnyEnaKmMaoEHnXDqy6cmXpAi4
QmbbYx2xnn5R8HFogJgEb6kqvUoaPQPLZkjWtPTqqdJZPx
Here are the links to the files:
https://
https://
https://
@RangerMauve Not sure if you already had put the video on IPFS, here is the CID QmVEKci1FF4ZiLcayguVQ5512nCPxTkP98LZsmq6GCNPRB - pinning it from my machine and i'll keep it running. Also seeding your hyperdrive so it should at least how 1 connected peer. A snapshot of your site is at QmSSRVqtgtvGRJpG29tezwvdRryuwbUN8V6SKRH1yRqFVj
Cool feature of https://
It's pretty neat how fast "surfing" on a static site in a Hyperdrive is , feels like the ideal solution for a local intranet set or small community website. Also Agregore Browser is cool.
Back on Hyperdrive with my personal site:
hyper://johanbove.info/ or directly at hyper://2593c89d6cbf2b830c71099cbe541459d333df67d9a846e2133ebbbfdef8d8bd/
See: https://
Using a symlink junction now for keeping the Beaker Browser Hyperdrive directory on a bigger hard drive. Apparently however there is something like null bytes on NTFS partitions which make the drive seem much bigger than it actually is. After zipping the 12GB directory it resulted in a 500MB archive file.
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.
Anyone started building a chess game using our #Hyper profiles yet? Most of the features are already provided by Beaker (address book, permissions for writing); the only things we need to do is to get the chessboard and the chess engine and bring all the pieces together in a sweet #hyperdrive app.
@MVD_Vandie Not sure if @Gatewaybrowser will support dat:// too. If not, it can probably be added. A mobile hyperdrive client is really something we need for widespread adoption of hyperdrive and dat sites and drives. The fact that Gatewaybrowser supports the Beaker API is really cool as it means all apps "made for desktop" will work "on mobile" too.
@GatewayBrowser @pfrazee Let's already create our Hyperdrive sites "mobile first" .
😏😼
1 min read
Actually: Beaker OS would be very similar to Google's Chrome OS which installs on many laptops. What would be necessary to make Beaker OS "bootable" ?
A list of basic applications any computer should have
We can use web applications in @Beakerbrowser for our own usage safely without having to enter _once_ a password or user-name. Just select the hyperdrive profile you want to use from a dialog and you're good to go.
For the past year, we've been working hard on the v10 release of Hyperdrive. After a long period of beta testing, we're excited to announce that it's ready for general use!