feature: incorporate plan1 foundation for peersky parity #276
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
heyo- ty from sillyz.computer here-- i'm stepping back from open source being my full time gig, but want to decentralize my research before i go-- a two weeks notice hand-off of sorts.
to date, sillyz has been about bridging systems through user experience, which in practice is javascript for writing hypertext, what i lovingly refer to as "my elves"; tiny hypertext helpers.
my overall hypothesis is that the key to interoperable systems are portable, re-mixable components.
this PR adds baseline compatibility between sillyz.computer, plan98 systems, peersky-browser as of yesterday, which unlocks any of these unstable elves (plan1) and any of these more stable elves (plan98).
by incorporating this pr, it'll be possible to begin to bridge client experiences from within peersky, agregore, and sillyz.
one of my personal favorites is a shared bulletin-board (still experimental), currently powered by https://gun.eco, but we can agree on any state synchronization engine for
{x,y,z,width,height}and it'll work across environments. We also don't need to incorporate this elf, but this PR opens up new potential experimental avenues, leveraging my library of elves to date.the most documented demonstration of plan98 to date is in this https://braid.org meeting from last month.