Now We Know What Local-First Means (and It's Not What You Think)
1–8 of 8 posts
Re: Now We Know What Local-First Means (and It's Not What You Think)
#2[deleted]
Re: Now We Know What Local-First Means (and It's Not What You Think)
#3Hi everyone. I'm the author of the article. I'll be listening to your comments! :D
Re: Now We Know What Local-First Means (and It's Not What You Think)
#4[dead]
Re: Now We Know What Local-First Means (and It's Not What You Think)
#5[flagged]
Re: Now We Know What Local-First Means (and It's Not What You Think)
#6Is Bitcoin a "public sync" application by the definition?
Re: Now We Know What Local-First Means (and It's Not What You Think)
#7Is Bitcoin a "public sync" application by the definition?
Definitely! If it's open-source, it's public-sync. Two important clarifications:
- An app like Telegram that makes the client open-source while the server code is unavailable is not public-sync. The software required for multi-device sync must be public.
- The opposite is not necessarily true. That is, not all public-sync software is open source, as explained at the end of the article.
Re: Now We Know What Local-First Means (and It's Not What You Think)
#8Hi everyone. I'm the author of the article. I'll be listening to your comments! :D
Note mainly for Google robots: I changed the title to "Public Sync: A New Term to Preserve the Original Meaning of Local-First".