Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Thoughts around Rotonde #3

Open
cblgh opened this issue Nov 24, 2016 · 1 comment
Open

Thoughts around Rotonde #3

cblgh opened this issue Nov 24, 2016 · 1 comment
Labels

Comments

@cblgh
Copy link
Contributor

cblgh commented Nov 24, 2016

below are various disjointed thoughts on the rotonde project at the moment

part 1

  • abstract db access from the beginning
    • (making it easier to transition out of text into something else, should someone wish to)
    • simply done through wrapper functions: writeToDb(data) - doesn't need to be more complicated
  • point of focus is communication between nodes
    • how does it happen
    • when does it happen
    • through what means does it happen
  • discovery isn't important for us to write, use existing means
    • (social media, website postings, word of mouth)
    • (alternatively: discovery can occur on node-per-node basis,
      you can see nodes that follow this node & are followed by this node)
  • minimalist, fast, scriptable

---extraneous thoughts---

  • echoing the early web with everybody creating custom, unique webpages
  • runnable as an app, in the terminal, as a server
  • explicitly lacking an authorization system
    • aim of this idea is to prevent centralization on one node
  • verifiability?
    • how do we prevent clone accounts, should we prevent clone accounts?
    • how do people know i am me, are there other simple mechanisms we can use for this end?
    • do we even have to write anything ourselves, do we have to care?
      • if you link your portal, page, profile from your website/social media it doesn't matter

part 2

i think we want to make something as small as possible and work within the
constraints we set ourselves, constraints based on what problems are hard for
us to solve with this tool - and just design around those problems

i think the best way to view all of these preliminary discussions, and whatever
things are in the rotonde repo before dec 1st, as exploring the topic,
generating ideas to find the best ones to run with when we start

i think it would be okay and good if people could browse the protocol, view
other nodes without having a domain or a server

i think offline instances should still be accessible, or rather their content
should still be viewable

i think at the moment there might be many different versions of rotonde
floating around

@neauoire
Copy link
Member

neauoire added the Fairly Sized Thoughts label 4 hours ago

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants