-
Dear Beaker people, It would be pretty sad to loose sites currently published on dat:// If you're not at least supporting a read-only display of dat:// resources, you're basically asking everyone who ever published on dat:// to point people to a legacy version of Beaker to access their material or to completely redo their sites and links. This will be especially difficult for collaborative projects spread across several dat:// datasets, for instance Floating Swarm by Rafäel Bastide. dat://de037e790893b7113b93bc523c4cf7671acdbc370bfa0acc00e0b3781a83b56b/ There also doesn't seem to be a DNS→Hyperdrive or .well-known→Hyperdrive plan in place yet that for instance was used on https://digitalfolklore.org that points to a dat:// site with different resources available at dat://f1a5ed8cd08dc9704d6261c899bbd0f5a0851e596f132d6edc562c1a4948c43e/ I have also figured out that on my System (Ubuntu Linux using AppImage versions of Beaker) it is not apparent how to run legacy versions of Beaker if the latest version is installed. All my 0.8.x AppImages now launch the 1.0 pre-release. Don't become the Yahoo of p2p! 😉 |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 7 replies
-
I agree with @despens. Here is a non-exhaustive list of dat-related projects that just can’t be lost or broken, most of them can’t be changed or adapted without changing their nature:
Thank you @despens for pointing this issue. Even though Beaker+Hyperdrive sounds exciting, I think Beaker should not deny its past, on the contrary, it is very much in the P2P spirit to make sure content remain accessible in hyperspace and hypertime :) |
Beta Was this translation helpful? Give feedback.
-
We are listening to yall here and trying to make the best call we can. It's a time juggling act. We knew losing the existing dat:// content sucks but we're also trying to keep a forward pace going -- after taking over a year to just get out the 1.0 beta, we didn't want to delay longer for legacy dat support. We want people to migrate to Hypercore and our main goal with legacy support is to make that possible. (It would help if I didn't keep shipping a broken dat converter on windows.) That said, I know migrating takes some time and it would be helpful to be able to still view dats. I think I can hack together a way for the dat converter to access the network (instead of only locally-saved dats as right now) and also support dat-dns. I also think I can get the web pages to display rather than showing only the converter interface. The converter could move to some other browser UI. What that doesn't include is the old Do yall feel like that would be enough? |
Beta Was this translation helpful? Give feedback.
-
Gonna chime in real quick here. Of course, archival was always a critical part of my interest in Has been a lot of fun watching this mature, and congrats on the release! |
Beta Was this translation helpful? Give feedback.
-
Good news - master branch now has read-only browsing for dat:// sites. We should release it this week (Thursday if we maintain our regular schedule). The updates will also make it much easier to test the dat:// converter, so hopefully fewer releases will have breaks in the code. |
Beta Was this translation helpful? Give feedback.
Good news - master branch now has read-only browsing for dat:// sites. We should release it this week (Thursday if we maintain our regular schedule).
The updates will also make it much easier to test the dat:// converter, so hopefully fewer releases will have breaks in the code.