Hello, I just signed up. I have no coding skills but I’m eager to help bring this initiative to regular web users. Should I just wait for Solid to develop to a consumer level? Is there any way I could contribute right now?
I may be in the wrong place for this question…
more likely the wrong time with the holidays:-)
Thanks, good point I’ll keep an eye on the forum and maybe bring it up again later. Happy new year for now.
Happy New Year!
& Welcome… As you have no coding skill, perhaps could you represent the ‘end user’ .
First questions I’d like to ask to an enduser is :
- what is a graph for you ?
- do you know what is a triple ?
Hmmm, a test? Seriously? I explored the forum some more, it does not look like this ecosystem is anywhere near ready for release to real-world end users with average tech skills . I’ll keep an eye on Solid and will be in touch when things look more accessible.
In a society full of gbk’s, gods behind keyboards, it’s a wonder we function at all:-)
To be fair to @Smag0, I think he meant it more as a survey than as a test. Most developers see the challenge not as educating users but as making the technology accessible to people who as functioning humans already know an awful lot, way more than can be coded. Apps can’t be made better than people are at negotiating, arguing, compromising, insisting, not to mention just walking around, and all the other things they do. There is a long way to go to align apps with the natural way people do things. Sometimes developers need to know more about how people do things and if the tools are making sense. This ecosystem isn’t ready yet but real-world end users with average tech skills can definitely help get it there.
Looks like I have some time before the sandwiches arrive, so…
- what is a graph for you ?
Usually, something my eyes bounce off of.
- do you know what is a triple ?
You’re not talking about a 3-cylinder motorcycle engine, I’m guessing.
Some of us came here in hopes of seeing progress toward that elusive next big thing in social media, the promise of “Web 3.0” et cetera, willing to help but unprepared for the incomprehensibility of y’all’s discussions. To non-coding non-developers, it’s all very confusing.
I see hints of things beginning to work, but something that works for someone comfortable with slinging code is probably far from being ready for the rest of us.
And that’s cool, take your time, we all appreciate your efforts. At some point though we do need to get together and bridge the divide.
Well, thanks to everyone for the feedback. For me a graph is a visual representation of a series of numbers and in my part of the world a triple is a type of beer. I was hoping to get a pod, share some files, change a paradigm, maybe overthrow a government or a corporation, you know, the usual.
Just kidding of course. Keep up the good work, happy new year and perhaps I’ll speak to y’all later
@Rennek, I didn’t want to test or afraid you… just wanted to throw you some basics of what we are doing here…
Although everyone has certainely other approach (for example, “you are the owner of your data”…), the central point, I think, is data and links between those data .
It is very similar to what is behind Solid and how data is stored :
When i create (as you can see in the video below) two nodes like “Smag0” & “Spoggy” and a link like “developper Of” to link them, I make a triple, and a group of triples can be seen as a graph
For the moment, I store my graph on my Solid POD in json format but i’m working on storing them in Turtle to be more close of Linkeddata spirit, because in it’s core, LinkedData is able to connect multiple knowledge base…
For example, in my graph, if I add another triple like “Smag0”, “lives in”, “Lyon” or “Smag0 locality Lyon”, I could easily connect other that have the same locality, or more I could say that the “Lyon” I use is the same as the one which is stored in another knowledge base like DBpedia and extend this way my graph with data from others graphs or knowledge bases.
Linkeddata and what is around is always confusing at the beginning because we used to think “sequential” or “data in a table”, but in my opinion, graphs offers new perspectives, where everyone can have his own point of view and add what he think is missing, explore data in his own way, following this or that link, where apps can use data from a source or another…
@filsmyth, is this graph https://spoggy.herokuapp.com/?source=https://smag0.solid.community/public/spoggy/Smag0%20%26%20Rennek.json bouncing your eyes too ?
(experimental & hosted on a free heroku server, so if nothing appears wait 15s & refresh to let the server awake)
If so, please guide me to what I can change so it’s more nice for you
You both can help me and other developpers, saying what I must change to my app Spoggy, what you’d like to see, what you don’t understand… I’m really sorry, but i think like a developper : I need a functionnality, so I put it there, and another, so I develop, but perharps this is not the good way, the good location, the good word…
–> “No coding skills” participants are here to drive the coders in the right way ! We are at the beginning of the userexperience, but lot of work have been made in the background…
Thxs for your help (I hope)
Hey there! Great to meet you. I a non-coder too, but this does not prevent me from tinkering with solid. I am just playing around and then looking to translate my experience (and fascination with Linked data and the Semantic Web) into Plain English. e.g. I made this with non-coding skills, just trying my way … https://teodora.solid.community/public/NotesfromTimBernersLeetalkatMozfest2018.htm I think coding is as important as coding our perception and making ourselves ready to make a difference (sorry to be referencing to another post of mine, but this is where I wrote about how I feel about Solid http://www.teodorapetkova.com/poiesis-of-relationships/the-project-solid-as-a-road-assembling-itself-on-the-go/)
Happy New Year btw And I will see you around here. Also take a look at the Hello solid post, you will find other people who are “non-coders”
I think it is fair to say that, yes, Solid, at this point, is mostly for people with tech skills who are ready to put some effort into understanding Solid. Even Inrupt recognizes this - on the “Get a POD” page (https://solid.inrupt.com/get-a-solid-pod) they have " The Solid POD providers below are currently designed for use by a highly technical audience of developers" (highlight by Inrupt!).
Solid is nothing more than a concept for as long as non-coders are unable to use it or unable to follow the technical instructions required. As the internet speeds up, I would like to see a Solid POD Server in every household, with each member of the household owning their own POD on that server, and with the server left on 24/7 as naturally as we now leave on a fridge or a freezer.
For most non-coders, that means finalizing the Solid POD Server software, and then some bright spark creating a graphical user interface (GUI) to enable the Solid POD Server to easily installed on home hardware by non-coders.
Then the same thing needs to be done for the additional apps. They just need a GUI.
At some point (maybe we are in the middle of it) there will be a Cambrian explosion of apps, hopefully many of them free and open source. I think using components can help. More on that here.
Just a small hint: non-coders and applying coders are in the same boat.
In reply to the original question. There is a way in which @Rennek can contribute right now. I would suggest getting two of you registered on one of the existing Solid POD Servers (yourself and a friend for example) and then trying out the growing number of apps, and then providing feedback to the app developer to tell them how you found the experience.
@pheyvaer has developed a chess app where all the content is contained only in your own POD, and the POD of your competitor. There are a growing number of apps and if two of you register you can allow your friend access to your public files (and vice versa) and try out some of those apps between you. Your feedback would help the developer.