Code of Conduct: https://github.com/solid/process/blob/main/code-of-conduct.md - Website: https://solidproject.org/ - Repos: https://github.com/solid/
Atm I'm using Java & JavaScript for a lot of things from small 50 people companies, to software thats been key to some projects requiring ~300 mil transactions to be processed in a short amount of time.
Where I'm working on Java, its usually to bridge them to the world of JavaScript
I did work with a framework called Enonic XP which enabled me to work with JavaScript on the backend through Nashorn, which was ok most of the time, but could also be quite hellish at its worst =P
now I try to focus mostly on JavaScript, HTML and CSS and hope that Solid servers can give me most of what I need wrt back end functionality ^_^
I've been onto what's now moreover known as solid, atm, for ~19 years (since 2000, when I wrote a paper about an "iBank", inspired by a relatives work that won.him a Nobel prize (function of.synaptic nerve cells, John carew eccles) and my.Application of.that theory to.online data storage; moving forward, @sideshowtom, I'll follow-up.
Hi all, I've been following Solid from afar for a little while now with some considerable excitement for all of the obvious reasons around privacy, decentralization, etc., but I'm sad to say that every experience I've had with Solid has been rather poor. The reason for this is that I happen to be blind, so I use a screen reader. I understand that things are very much in a prototyping stage at this point, but I think that standards conformance like adhering to markup validation and also the rather well-documented success criteria from WCAG 2.1 align completely with the values of TBL and others behind this important and significant work. When things don't start out accessible, they very rarely ever become so. An inclusive design methodology can really help here, as there seems to already be various tooling being built around the various apps in Solid from different providers (I'm still learning the lingo, by the way, so sorry if I mess that up). This kind of inertia will only grow, and if accessibility is not being considered from the beginning, then I would consider that an incredible tragedy for work as important as this. I will try to follow this channel, but this interface is not the most accessible, ironically enough, so please forgive me if there are delays in response or an absense of feedback. If there's someone that's an appropriate individual to have a longer in-depth email or phone conversation with, I'd be happy to do so. I happen to also be an expert in accessibility, with a focus on web accessibility, so I am very much willing to put my time and effort where my words are, but I feele it important to note that accessibility should hopefully be a basic tenant of this work so we do not inadvertently continue the exclusion of persons with disabilities, amongst others, due to the inaccessibility of the various interfaces surrounding this project. I'm sorry to open with a "complaint" so to speak, but I feel this is super critical, and I hope there's an opportunity to rapidly enhance the accessibility of the various interfaces and perhaps enforce accessibility as strictly as any privacy and security concerns, which is a principle that I trust this group of amazing people agrees with. Thank you for anything/everything you can do to help make Solid better for all people of various abilities, and also sorry for the long opener.
Hello all, I’m Michael.
I want to introduce myself to you as someone who is following solid and taken an interest in the Dataist movement.
I will be the first to admit to you I’m 100% clueless to all things dev but I’m doing what I can to educate myself and be a part of the community.
I’m a complete NeWb and I don’t know anything yet but I’m working hard to educate myself and learn things.
I hope I can be accepted even though I’m not a dev or programmer.
I look forward to learning. 👍🏻
I want to introduce myself to you as someone who is following solid and taken an interest in the Dataist movement.
I will be the first to admit to you I’m 100% clueless to all things dev but I’m doing what I can to educate myself and be a part of the community.
I’m a complete NeWb and I don’t know anything yet but I’m working hard to educate myself and learn things.
I hope I can be accepted even though I’m not a dev or programmer.
I look forward to learning. 👍🏻
@sinabahram you should also post your intro on the Solid Forum ... @Mitzi-Laszlo is the community manager and may have some suggestions about where such a working group might live.
@thatmikehill welcome! We need thinkers and testers and promoters as well as developers. You should introduce yourself on the forum
@sinabahram Welcome! I couldn't agree more with you, and it is so good to have you here. By all means, please continue to provide feedback when you can. I'd be super interested in having your feedback on https://dokie.li/ - the content there is more or less what the application can produce, or at least the intention when all of the components are working smoothly :) WCAG is a top-priority. ATAG and UUAG are also on the map. If you'd like to discuss further, eg. features you'd like to use, there is a dedicated public chat at https://gitter.im/linkeddata/dokieli .
Would it be ok for me to contact you when we've started the work on the data browser? I would love help to ensure that we include everyone
the goal is very similar to solid and it was started a couple years ago but never got much attention
Hi folks. I've seen some work around a more concrete social client from @melvincarvalho some time back and wondered whether there was any traction on this or other similar application? Has anyone prototyped out a "Facebook replacement" that could be considered at an alpha / beta stage? Is there intent or current work underway within the community toward building something outside the basic microblogging / Twitter use case?
@jeff-zucker Funnily enough, it was another post from that same author that I'd read as well: https://safenetforum.org/t/solid-social-decentralised-social-network-using-linked-data-solid/17385
And thanks for sharing that link. It still doesn't quite look like what I'd consider to be something that the typical non-technical user would view as being a potential alternative to their expectation of "a social network", but it does look like a very interesting blogging platform!
@Phil-Wheeler I think you’re correct, most non-techies won’t even have any clue what to do with it. I can say this because I’m one of them. I have a POD with STACK now (I think that’s what it’s called)
And I have know clue what the heck I doing or what it’s really for or how to use it. 😆
But I’m trusting I’ll learn little by little and there is a movement and vision that Tim Berners Lee has and I don’t know dev or programming, but I want to be a part of it.
So some, maybe very few of us non-technicals will be here with ya. 😁
“The web as I envisaged it, we have not seen it yet. The future is still so much bigger than the past.” - TimBL
And I have know clue what the heck I doing or what it’s really for or how to use it. 😆
But I’m trusting I’ll learn little by little and there is a movement and vision that Tim Berners Lee has and I don’t know dev or programming, but I want to be a part of it.
So some, maybe very few of us non-technicals will be here with ya. 😁
“The web as I envisaged it, we have not seen it yet. The future is still so much bigger than the past.” - TimBL
@thatmikehill Heh. Yeah - stick with it. I think there's a slowly-growing discomfort with the walled gardens where you are the product. I'm a web developer on the .Net stack by trade, so I'm technically capable but I'm not going to launch into rolling my own app if there's already a good candidate out there.
We have at least two different list of solid apps, which differ much. One at the w3c wiki and the other in the solid/solid-apps GitHub repo Since it inevitable that those lists diverge, and surely will again even if we try to "clean up" I think we should decide for one location. Are there any preferences for one or the other or reasons to keep both?
Here's a weird one, working on Plume I'm trying to use solid-auth-client fetch (which maps to rdflib) to overwrite config.json with PUT. The same put() function is used for saving blog posts with '.ttl' extension and content type 'rdf/turtle' and I've also tried saving to a '.txt' file with content type 'text/plain'. Here's the function:
var put = function(url, data, type) {
let contentType = type || 'text/turtle'
var init = {
method: 'PUT',
headers : {
'Content-Type': contentType,
'Content-Length': data.length
},
credentials: 'include',
}
if (data && data.length > 0) {
init['body'] = data;
}
var promise = Solid.fetch(url, init)
.then((resp) => {
if (resp.status === 200 || resp.status === 201) {
return Promise.resolve(parseResponseMeta(resp))
} else {
return Promise.reject({status: resp.status, msg: resp.statusText})
}
})
return promise;
};When I try to save to a file 'config.json' with content type 'application/json' the response is 200, and the file is overwritten but empty. Just changing the content type to 'text/plain' causes the content to be written to a file with a different name ('config$.txt'). Any ideas?
I'm wondering if rdflib doesn't like the 'body' I'm sending, which is the output of
JSON.stringify(config,null,4) which looks like this:"{
"owners": [
"https://localhost:8443/profile/card#me"
],
"title": "Plume (sac-smalinin)",
"tagline": "Light as a feather",
"picture": "img/logo.svg",
"fadeText": true,
"showSources": true,
"cacheUnit": "days",
"defaultPath": "public/posts",
"postsURL": "https://localhost:8443/public/posts/",
"saveDate": 1555152421986,
"postsElement": ".posts",
"loadInBg": false
}"
Just changing the PUT to write to config.txt with type 'text/plain' works. Does rdflib fetch expect something different for 'application/json'?
Or maybe its a node-solid-server thing?
Not sure how the indentation is handled...
Another option would be to save the config as ttl and request jsonld if the client relies on a json serialization
oh nevermind, there it is
why is the content type text/turtle rather than application/json?
This message was deleted
I made a how-to to build a docker solid server on a Synology Nas see : solidforum and solid-wiki for beginners
@bourgeoa thanks for looking but I'm using 5.0.1 :wink:
@jeff-zucker 'text/turtle' is the default but I'm specifying 'application/json' for the '.json' file.
It works with config.txt and 'text/plain' but I get a zero length file if I use config.json and 'application/json'.
I'm going to settle for config.txt, but no doubt we'll want to PUT json files at some point.
I'm using solid-filemanager but this doesn't recurse directories, which is going to be laborious for ordinary folks