This would be super-useful because currently not many tools exist for non-tech users for creating graph datasets AND visually laying them out in a sensible way.
2,584 karma · joined December 13, 2009
This would be super-useful because currently not many tools exist for non-tech users for creating graph datasets AND visually laying them out in a sensible way.
The stuff here is called an "Activity" around "Objects". Follow request is a "Follow" activity with the "Actor" as the object. A tweet is a "Create" activity with the "Note" being the object. There's an entire vocabulary defined in the spec: https://www.w3.org/TR/activitystreams-vocabulary/#object-typ...
This way, all kinds of social platforms - from YouTube to GitHub - can be modeled in this general distributed pub/sub system.
I think this needs to be thought carefully. A house, because it's saleable, represents an opportunity cost. If the market value doubles overnight, a rational actor should re-evaluate whether it is still the best course to continue to live in it, rather than sell it.
Browsers already have both user identity across multiple devices and ability to sync data. It just needs to be extended to cookies and localstorage.
One of the most frustating thing about the current generation of note-taking apps has been that either they are available as an offline app, or as a VS Code plugin. Many of them have turned into VC-funded startups - keeping the web version as a proprietary product, blindlt following Roam.
It's an attempt to organize world's knowledge. Right now, it looks like GoodReads-like social network for learning resources organized by topics, formats, difficulty levels etc. But there's a knowledge-graph that separates ideas and the medium those ideas are expressed in. For eg: "Sapiens - the book" and "TED Talk given by Yuval Harari" are connected to the same node.
This idea isn't anything new. Here is Danny Hillis talking about it at OSCON 2012: https://youtu.be/wKcZ8ozCah0
The code is open-source on github: https://github.com/learn-awesome/learn/
https://news.ycombinator.com/item?id=30208558
- Scaling is not a worry.
- Simplicity is essential because developers are volunteering their time.
- Users also benefit because they only need to manage a database and not 6 different server language runtimes. Can even use managed services like Supabase or RDS.
Also, the HTML page on CDN wouldn’t know what endpoint (domain, port) user has deployed their API on. One more thing for user to configure. Here, the HTML configures window.postgrest_url which the JS code can use.
It simplifies the 3-tier architecture (DB, server, client) into effectively 2-tier because the server environment is replaced by a standard binary (PostgREST) with zero hand-written code. This is 33% improvement in language/framework complexity if nothing else.
If needed, one can also write postgresql functions/triggers in Javascript/Python/etc for productivity - although this doesn't seem to have taken off yet.
The times are changing though. If there's anybody here from Supabase team, would love to chat about these topics.
I really think there's a lot of value in this model for users to self-host apps. PostgreSQL can run cron jobs, operate on external data with foreign data wrappers, and even do some number-crunching with Madlib right within SQL.
So, the user only has to manage a postgresql db, retains control on data and can easily get upgrades of webapps via CDN and mobile apps via app stores. Developers benefit because (a) there is no server-side programming language to deploy/maintain and (b) PostgREST API is very well thought-out and very predictable - leading to easier development across frontend/mobile frameworks.
This would not only help with music practice, karaoke,
> Signal had to verify that MobileCoin worked before exposing their users to the technology. That process took a long time because MobileCoin has lots of complicated moving parts.
> With respect to price, no one truly understands the market. It’s impossible to predict future price.
- https://twitter.com/mobilecoin/status/1379830618876338179
Reeks of utter BS. As the reply on this tweet says, features can be developed while being kept switched off with a flag.
The one called "Trading Basics" by ISB seems like a good starting point.
We users trust our browsers a lot already. And they've been good stewards so far (such as end-to-end encryption of sync data). This proposal in meant to leverage browser sync and push to replace social logins such as Google, Facebook etc.