Ideas for Solid apps
I hope to work on this idea myself, after I (hopefully) finish an npm package for rdflib.js for a (pretty basic) serializer to svg.
We’re in the process of mapping out next gen applications for Holochain / Holo. The ideas and ideals behind Solid are very similar to what I was hoping to create in the Holo space, so I’m looking into Solid as well, and starting to play with it. For sure, we are setting up a Solid WebID-ODIC authentication server for all our coming projects.
These technologies encourage a paradigm of new technological horizons, which are further, exponentially progressed when eradicating the typical corrupting human elements of power, money and control. Very exciting.
Incorporating Solid with DAO mentality is sort of the gist of what we’re setting out to accomplish.
I’ve just come across Itty Bitty - this looks like an easy enough Solid app. The point of Itty.Bitty is that all content is stored in the URL, never on a server, making for a very lightweight CMS and/or messaging idea.
https://itty.bitty.site/edit (shorter URL, click on About from there)
I’m just starting to develop a Products website. My wife creates and sells embroidery and knit things.
The idea is that the website would load products from a person’s Solid POD (probably configured in the server environment, but potentially could be input as a field to allow for browsing various people’s stores). Visitors to the website would see that person’s products and be able to purchase them.
The website would then update the inventory counts appropriately so that as things go out of stock they’ll be removed from the website. *This is the hard part… as far as I can tell, this sort of authorization isn’t supported by a solid-server yet… I’m asking around though
Sounds like a great idea. You might try looking at web sockets for that, https://github.com/solid/solid-spec/blob/master/api-websockets.md , to have your app notified of changes to resources on a pod. They are going to Linked Data Notifications, https://www.w3.org/TR/ldn/ , but I dont think thats implemented yet.
The itty bitty thing is very interesting. If I cut-off the last three characters of the created URL then a blank screen shows. I can add the three characters and refresh to see the content. So it seems somewhat useful to send private content, with the last characters sent as a PIN separately. But if someone understood the encoding I guess they could figure out the message. I’d like to know more about this.
“(Solid) is about creating a single Solid API which any app can use to talk to any store, so the user has a choice of several places to put data, and complete control of sharing or not in case. The client-server API is made of HTTP and LDP and WACL and some glue, extra HTTP headers, a little posix metadata. That is a significant, but finite, spec., which every Solid server must meet. Then clients can talk to each other via the servers without the servers needing to know anything about the application. So then we need common standards to allow the clients to interoperate: ‘client-client’ specs. How to discover the user’s contacts, the user’s general stuff, (type indexes), preferences, groups and communities, preferences within those communities. And then domian-specific standards for chat, photos, music, issue tracking, likes, bookmarks, health, fitness, academic records, CV, and so on. Lots to do!”
Betty steps off the private jet holding her full belly. It’s good to be back home amongst the familiar. She breezes through customs with a simple pass of the wrist and a smile.
Her black Tesla Uber sits outside the airport as she makes her we through the private exit, away from prying eyes.
Betty lives a simple life in New York as a financial analyst for Goldman Sachs but always returns here when health is concerned because the medical services are significantly better. The political system isn’t too shabby either given its move towards radical openness and transparency.
“Fuck!” she screams from the back of the car.
“Betty, is everything ok?”
“My water just broke.”
“Hang tight, we’re headed to the hospital now!”
The drivers speeds up with motorway to the hospital and pulls up on the front. A nurse runs out with a stretcher and gets Betty on with the help of the driver.
“Congratulations and best of luck” he shouts as her drives away.
The nurse asks Betty for permission to access her medical records as she picks up a tablet from the side of the stretcher. She grants it by pinching her wristband. “Thank you! We’ll have a doctor with you immediately and page your husband.”
“It’s a healthy baby girl” the doctor says as the nurse wraps her in a blanket and bring her other to her mom.
“What color wristband would you like for her?”
“Excellent choice. We’ll add her vital information on here and attach dates for when you need to return for her checkup. You’ll receive the rest of the Welcome Package at home in a few days.”
Cari is a digital life ecosystem for the Caribbean and Africa. This would be modeled after Aadhaar in India. We strive to make the entire process simple enough for the youngest to the eldest of individuals by removing the heavy technical burden.
We will have to build our own KYC process some nice they are none catering to the Caribbean. Starting within the Caricom region would be ideal due to the common economic zone.
This also allows for multifunctional locations but lower overhead since we are not a traditional banking institution.
Banking + payments
RFID tags for wristband and pendants
RFID readers for Service provider POS
Digital key will be stored by customer
The SAFE Network | Building the new decentralised Internet
SAFE and Solid: the internet as it should be – pierrechevalier83 – Medium
Securing big data in the Cloud by protected mapping over multiple providers (https://www.researchgate.net/publication/308672004_Securing_big_data_in_the_Cloud_by_protected_mapping_over_multiple_providers)