David Dias
David Dias
Leaving this article here https://juretriglav.si/open-source-collaborative-text-editors/, it provides a good update on the state of text editors everywhere, might spark some ideas for PeerPad :)
As far as I can see, the UI doesn't tell me the state of persistence yet.
I've seen users try PeerPad, mess up the URL and enter different pads, ending up very confused why messages do not sync. PeerPad should have its full URL in `baseEmoji`...
There needs to be a strategy around long-term persistence support. If I bookmark a pad today, will I be able to see it in a year? The answer should be...
It should at least tell the user that something is wrong
Here is an idea. In order to solve the "multi tab" issue, the js-ipfs node for PeerPad can be spin up on a Service Worker -- https://github.com/ipfs/ipfs-service-worker -- and then...
^^
## Greetings @ipfs/ipfs-camp-2019-attendees 👋🏽 ### I'm psyched to welcome you to the 🏕 2019 IPFS Camp 🌌 Content Repo 🚀 🚀 It is in this repo that you will find...
@momack2 pointed out that the Go team has a set of principles explicitly written at https://github.com/ipfs/community/blob/master/CONTRIBUTING_GO.md#contributor-principles. I would argue that these are pretty much universal for the whole IPFS project...
What about adding a Contributors table to our Contributors section? This can be done automatically with: https://allcontributors.org/docs/en/overview