I had exactly this thought just over a month ago. After mulling it over for a few days, I decided that the only reasonable way to build it would be on top of Scuttlebutt. Alice shares her CV, makes it available via a pub, Bob shares a job description at the same pub, and the two can connect through there, etc.
The advantage of SSB is the absence of the need for an always-on, big data cloud service. The project instead is managed by a swarm of phones all connecting intermittently. It’s very solarpunk.
The big problem for me was the multiple device question. If Alice wants to interact with “FreeLinkedIn” both on her phone and her laptop sporadically over many days, you still need a cloud device to hold state, negating all the benefits granted from SSB. I couldn’t figure a way around this, and then got distracted.
I had exactly this thought just over a month ago. After mulling it over for a few days, I decided that the only reasonable way to build it would be on top of Scuttlebutt. Alice shares her CV, makes it available via a pub, Bob shares a job description at the same pub, and the two can connect through there, etc.
The advantage of SSB is the absence of the need for an always-on, big data cloud service. The project instead is managed by a swarm of phones all connecting intermittently. It’s very solarpunk.
The big problem for me was the multiple device question. If Alice wants to interact with “FreeLinkedIn” both on her phone and her laptop sporadically over many days, you still need a cloud device to hold state, negating all the benefits granted from SSB. I couldn’t figure a way around this, and then got distracted.