Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • Aug 11 2021 20:52
    @RubenVerborgh banned @mikeadams1
  • Jan 04 2021 20:23
    @RubenVerborgh banned @WebCivics_twitter
  • Jan 04 2021 20:18
    @RubenVerborgh banned @SailingDigital_twitter
  • May 27 2019 06:08
    User @Mitzi-Laszlo unbanned @in1t3r
  • May 23 2019 06:49
    @Mitzi-Laszlo banned @in1t3r
  • May 16 2019 09:49
    @Mitzi-Laszlo banned @mediaprophet
  • Feb 01 2019 22:04
    User @melvincarvalho unbanned @namedgraph_twitter
  • Feb 01 2019 21:49
    @melvincarvalho banned @namedgraph_twitter
Matthias Evering
@ewingson
okay, @jeff-zucker really didn't want to promote anything but was thinking in the sense of diversity..........
Jeff Zucker
@jeff-zucker
Right, but if you want it on sp.org, the way to do that is with a PR. Submitting a PR will put it on record that you believe providers X,Y,Z should be listed. Then it is up to the Team to decide if they agree or to ask you questions about the additions.
You don't need to jutify the PR, just submit it and that will give people something to react to. Though it may take time to react since we have lots of things we are dealing with.
Matthias Evering
@ewingson
but the most robust and permanent
then I'm honoured I do the best to maintain the root machine professionally
Jeff Zucker
@jeff-zucker
Yes, that's great service. Thank you! And I'm not saying the others on your list will be rejected, no way to know unless you submit it. :-)
Matthias Evering
@ewingson
even Sir Tim himself stated in some Solid World some months ago that we have to live with some fluctuation, some appearing, some disppearing so let's leave it this way a while ;-)
and if you ask me...... just in case we wanna expand the list, the UK's Open University Server would be the next to include
Matthias Evering
@ewingson
Jeff Zucker
@jeff-zucker
That does look good, but telling me and posting here will do nothing. Make a PR.
  1. fork github sp.org repo 2. change the file you want to change 3. create a PR.
Matthias Evering
@ewingson
I think it goes: 01.a) ask them what the hosting provider is cause thats a mandatory field
Jeff Zucker
@jeff-zucker
Well, yes, you need to gather the info first. :-)
Matthias Evering
@ewingson
will do. wilco. gonna search for contact info and do that immediately by mail.
Jeff Zucker
@jeff-zucker
It would also be helpful to know if they are a) inviting the public to create pods b) intend to be around for a while and keep the server updated c) are experimental or a full-service
Matthias Evering
@ewingson
they're up for at least a year or two already, but want no vital sensible data stored as they are experimental but I guess you have to say that ;-)
the 5.6.3 they are using is from feb., 4th
Jeff Zucker
@jeff-zucker
That is 5 versions from current, not a very good sign.
Matthias Evering
@ewingson
guess the good news is: if they updated on Feb. 4th, they at least care in some way, cause they are already around since longer than that..... I have asked them the needed questions now
Nick Form
@nickform:matrix.org
[m]
Is anyone aware of any work to support traditional email in Solid? In my mind an smtp server would deliver messages into a write-only container within a pod and there would be a selection of different front end apps for viewing and composting messages. I'm a bit sketchy on how outbound mail would work but it doesn't seem insurmountable.
I know that Solid opens up possibilities for more modern forms of messaging as were demoed in recent Solid World presentations but the biggest cache of my data that lives in someone else's server is my email and I would love to one day be able to move it to a Solid pod where I would then have full control.
Jeff Zucker
@jeff-zucker
An mbox -> RDF converter shouldn't be too hard to write if no one has done it yet. Pod inboxen are, by default world appendable (anyone can create new but not read or change). I think one of the spec panels is looking at data migration, you might ask in the specifications channel.
Nick Form
@nickform:matrix.org
[m]
Thanks Jeff. Migration it's one thing but actually being able to receive email into my pod from legacy email servers is my main thrust.
I found some useful prior art at https://www.w3.org/wiki/ConverterToRdf
Colby Russell
@crussell_gitlab
@jeff-zucker the "Solid-Node-Client" link in the solid-rest README is a 404: https://github.com/solid/solid-rest/blob/main/README.md links to https://github.com/solid/solid-rest/blob/main
Jeff Zucker
@jeff-zucker
@crussell_gitlab thanks, should be https://github.com/solid/solid-node-client, I'll change it
1 reply
Solid-Rest is not well documented, so feel free to ping me with questions
Colby Russell
@crussell_gitlab

anyone aware of any work to support traditional email in Solid?

https://schema.org/EmailMessage provides a start for the data model. The protocols would need work/specification.

Colby Russell
@crussell_gitlab

As a workaround to that...

Runbox, the email provider I use, has been modernizing their web client. https://community.runbox.com/t/the-runbox-7-roadmap/732 It's conceivable that you could propose Solid integration as a bounty, add support to Runbox 7, and then collect the bounty (subject to buy-in from TPTB).

Colby Russell
@crussell_gitlab
In that case, the web client itself effectively works as an adapter from IMAP-to-linked-data, depositing everything into your pod.
Nick Form
@nickform:matrix.org
[m]
Thanks for the suggestions @crussell_gitlab .
Áine Uí Ghiollagáin
@Aineuig_gitlab
Hi all! Looking forward to learning about the work @ Solid - any suggestions about where to start?
Jeff Zucker
@jeff-zucker
@Aineuig_gitlab - look over https://solidproject.org/, if you have questions, ask them here, or if they are things others might learn from, ask them in https://forum.solidproject.org/ so there is a more easily findable record. Browse that forum to see what others have asked. Solid takes some getting used to so most of us expect puzzled questions, so don't be afraid to ask. There are tutorials on the website and pointers to libraries and apps. Welcome to Solid!
Áine Uí Ghiollagáin
@Aineuig_gitlab
Thanks @jeff-zucker very useful tips! nice to get a friendly welcome as well!
Marrelle Bailey (She/Her)
@MarrelleBailey
Hi everyone, the DEI Chair has some exciting news! We are looking for Solid community members to join the Chair. If you would like to join us, fill out the DEI Chair Application. The application closes on Friday, August 3, at the close of business. I hope to see your application. Link: https://es1cz4pb7oi.typeform.com/to/IPGnqxH8
Marrelle Bailey (She/Her)
@MarrelleBailey
I mean September 3rd
Fred Gibson
@gibsonf1
As we approach our commercial launch, we've just made a major update to https://trinpod.us that now includes a faster and more powerful cognition system and more compatibility with the Solid Spec.
Alexander James Phillips
@AJamesPhillips
Anyone got any advice on how to change the Thing Type of a file using Inrupt's pod browser? https://forum.solidproject.org/t/change-thing-type-on-inrupt-pod-browser/4612 I uploaded a .ttl file but it's showing as thing type application/octet-stream instead of text/turtle and whilst I'm not certain, I think the incorrect thing type is the cause of a 406 I get when I try to use getSolidDataset on it from my application.
1 reply
Thanks in advance.
Fred Gibson
@gibsonf1
We are very excited to start our engagement with Marcus Pedersen Airport Innovation ApS to use Solid Pods for air travelers (touchless identity, biometrics, travel events...): https://www.linkedin.com/posts/graphmetrix_logistics-transportation-biometrics-activity-6836654812126314496-hmri
Joep Meindertsma
@joepio

Hi people! We’ve created a set of UI designs for a Solid Pod. They’re free to re-use, and the source files are included in the repo linked in the article!
https://ontola.io/blog/ui-for-pods/

Jeff Zucker
@jeff-zucker
@gibsonf1 and @joepio - Great stuff, thanks!
Alain Bourgeois
@bourgeoa
thanks good news
Tim Berners-Lee
@timbl
@joepio Thanks for the link to all the UI material and ideas.
I’d like us to design interfaces to our sold stuff, whatatever pods it may be on. I’d like to be able to by default look at stuff in four pods, and at each point, say looking at photo albums or photos, be able to turn on and off different pods from the merged view.
Like layers on a map.
Fred Gibson
@gibsonf1
:thumbsup:
Alexander James Phillips
@AJamesPhillips

@timbl this is really useful, thank you. I'm interested to know more about how you envision the app might be designed / how people might use it, and where different data would be stored :slight_smile:

(Sorry the list got quite long. I feel this is the wrong medium and if something like multiple forum questions, github discussions, email list, etc is better then I'm happy to take it there instead. Also apologies if some of these questions are answered somewhere already, I'm in week 4 of trying to wrap my brain and application around Solid and I think I'm finally getting there... we'll see how on/off mark I am based on the answers you and others give to the below :slight_smile: )

Q1. Are you imagining the images be grouped at the top level by pod, or could you group them by other factors such as the month the image was taken?

Q2. If they are groupable at the top level by a non-pod characteristic do the images have to show which Pod they come from? (related to Q5)

Q3. If I favourite an image so I can easily refind it later ("favourites" could easily then be a top level grouping with all the non favourite images shown further down the page) I assume you're imagining this "favourites" data is stored in my pod? Perhaps on the image meta data itself if I own it, otherwise on a tiny new "image pointer" which has a pointer to the URL (pod, and id) of my friend's image? (related to Q3b etc, Q4, Q6, Q6b)

Q3b. If I want to like or comment on an image where is this information stored by default? In my pod, or in my friends pod? I assume my friend's pod (assuming I have access to it)? But it also needs to be duplicated to my own pod's "image pointer" data so my app can find for me all the images I have liked or commented on?

Q3c. How do we keep those two data sources in sync, which is the source of truth? Is the strategy that the data stays in my friends meta data file and my image pointer just says: "this is an image that if you check it you will probably find you have liked / commented on the image"? For example my friend could delete / empty their meta data file so my app shouldn't have an "image pointer" saying "you liked this image" and then not finding any "like on it"?

Q3d. Trust: if I store my likes and comments in another person's pod, how do I stop someone else fabricating comments from me? I assume we have to move to signing everything?