You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
below are various disjointed thoughts on the rotonde project at the moment
part 1
you can see nodes that follow this node & are followed by this node)
---extraneous thoughts---
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
The text was updated successfully, but these errors were encountered: