6 ms·
>> The big difference: Beaker can host websites. So, for individual user to host a website, he/she need to keep his/her hosting laptop alive all the time?
by st380752143 6y ago
>> The big difference: Beaker can host websites.
So, for individual user to host a website, he/she need to keep his/her hosting laptop alive all the time?
- pfraze 6y agoYou're right, you or some peer needs to keep it online. That could be a service, or using the hyp cli tool, or beaker itself, or etc. There's gotta be one peer somewhere. EDIT: don't talk about up/down votes, my bad
- akavel 6y agoI don't know the Hypercore community well enough to be able to say for them, but I know it's similar with IPFS, and for it there are already a few commercial services providing such kind of hosting/replication (a.k.a. "pinning"). During a recent hackathon at my workplace, I led an experimental project based on such services: https://github.com/wpengine/hackathon-catation https://github.com/wpengine/hackathon-catation
- Blahah 6y agoThere are several such things for Beaker/dat/hyper* too! https://hashbase.io/ https://hashbase.io/ is the one by the Beaker team.
- mmmeff 6y agoI'm particularly excited about the prospects of setting up a peer of my dat archives on my mobile phone. It's an always on, power efficient computing device. Not ideal for speed, but seems like a great fit for a last-ditch-effort layer of redundancy when hosting on hypercore.
- Blahah 6y agoLike https://hashbase.io/ https://hashbase.io/, which you can use (very intuitively) from within beaker to add a stable peer. Which you know because you made it all :D
- mmcclure 6y agoThere used to be a service/project called Hashbase[1] that would "pin" (aka seed) a site for you. Looks like it's inactive, though, which is a shame since it feels like something along these lines would be pretty necessary for any Beaker sites you might consider remotely real/serious. [1] https://github.com/beakerbrowser/hashbase https://github.com/beakerbrowser/hashbase