#solidproject — Public Fediverse posts

Static #eportfolio sites for students would be nice, too (or #SolidProject pods or #ATProto PDS sites), at least for college students developing their professional identities. Combining that w/chat, social networking and #OpenBadges is a better foundation than building everything around an enterprise #LMS gradebook. Need better moderation and #E2EE privacy controls though. Have your students vibe code their own final exams in the meantime while Canvas is down ;)
#EdTech
https://hachyderm.io/@inthehands/116539289475889788

@woozle the article was described as "fairly long thinkpiece" by @Profpatsch which with 53 min. read time is an understatement of "fairly long" where it comes to typical online content.

Thank you for taking the time and ponder things! I think that is the most important. We are all so pragmatic and want to have quick results. And our society is asking to be hurried. Everything is urgent. All is in peril. But giving in to that urge is a trap, that makes us weaker as mankind to face our wickedest problems.

Besides "Hammock driven development" mentioned in the article, #Emergence is key. And emergence is WEIRD and fascinating. I just tooted about it in..

https://social.coop/@smallcircles/116384803540561801

--

I used #SolidProject just to contrast a totally opposite approach to how fedi evolves: Fully formal #OpenStandards driven, but with risk to evolve into a 'standards maze' without ecosystem support.

#Mastodon Foundation is a new development. Hopefully they care beyond the app.

#SX #SocialCoding #SocialWeb

@strypey @FinchHaven @naturzukunft2026

For the sake of further clarity I should point to your starting post and this text:

> we need domain-specific applications that leverage ActivityPub’s full semantic potential

And remark that in my opinion and by observation, tapping the sign "Reminder: #ActivityPub is #JSONLD, folks!" isn't enough. Much more is needed than pointing to the #OpenStandards to win back developers minds to adopt #LinkedData. There is a high reluctance and resistance to adoption that must be overcome.

Referring again to that adoption chart I drafted the other day - which is about #SolidProject, but this is where LD is strong(est?) today - "build open standards, and they will come" isn't going so well. I hope that changes, as I have always been a fan of the *notion* of the semantic web. Yet in role of a technology decision maker, not ready to bet on it for a social networking environment.

I've got a promising approach to reactivity for #PodOS on top of a #SolidProject

1. Additions and removals to the RDF store are exposed as rxjs observables

2. Observe methods on a store or Thing filter these changes and emit changes in values of interest
e.g.
https://github.com/pod-os/PodOS/blob/3a3a781f816c301810fb30c22eeef3a1976f371f/core/src/Store.ts#L203

3. Custom components listen to the observe methods to update their state and trigger rerender. When disconnected, the corresponding observe methods also stops filtering changes.

I've started a draft spec defining high level processing and rendering rules to bind an RDF graph to HTML elements.

The UI data binding is specified using HTML attributes, which when hydrated provides valid RDFa.

The idea is to enable bringing pages of data together within a single document

Still early days, but here's the description of a subject-connected list

https://jg10.solidcommunity.net/open-with/rdf-ui-binding.html#subject-connected-list

#LinkedData #RDF #RDFa #SolidProject #PodOS

Please welcome @PodOS to the Fediverse 🎉 Follow it to keep updated about it's development and get interesting tips and tricks about what you can do with it and the #Solid ecosystem.

#Web #PodOS #SolidProject #LinkedData #DataSovereignty #OpenSource

There is also a new #PracticalSolid episode about the #PodOS search feature. Check it out and (⚠ bad pun incoming) let me know how you find it! 😉

https://tube.tchncs.de/w/pcYPSMLt1ZyW1V6ppfDCXM

#Solid #SolidProject

In part 2 of my pantry app blog series, the app supports opening arbitrary resources and we refactor the code into a #PodOS compatible recipe pane that is also used in a pod browser app.

https://jg10.solidcommunity.net/pantry/blog/home.html#part2

#SolidProject

Current security measures for #PodOS compatible panes to be loaded within a #SolidProject pod data browser app:

Avoid triple injection of new panes:
- Panes must be defined only in user's type registry
- Links to HTML fragments are only loaded from the pane's document

Avoid untrusted executable code:
- Scripts in HTML fragments not executed
- Web components instead whitelisted by the browser app and lazy loaded

Still need to trust web components and expect loading of new triples

I did a bit of a redesign for the generic #PodOS data browser. Less clutter & redundancy, focus on human-readable labels & information, while all details can still be accessed if needed.

Try it out yourself at https://browser.pod-os.org/

#Solid #SolidProject

Probably not new #LinkedData ideas, but I've had two big realisations prompted by experimenting with #PodOS

1) I find it easier to build interfaces driven by components to which I have bound specific data rather than focusing on how I am navigating the knowledge graph

2) In an RDF world, this naturally happens by following predicates, and I want this level of control *in addition to* binding higher level shapes.

(Pls excuse rough diagrams)

#SolidProject

Rather than waiting for bugs to be fixed, here's a WIP note editor I've been working on and using, working with a #SolidProject pod.

https://jg10.solidcommunity.net/notes/notes2.html

Provides a Google Keep-like list of cards, but built on a folder of plain text files, inspired by the now defunct Denkzettel app
https://web.archive.org/web/20220819083331/https://play.google.com/store/apps/details?id=com.silli.notizen

A text-loader & (buggy) virtualised list component do most interaction with the server, leveraging #PodOS

Migrating my notes to this app involved copying my text files into my pod.

Dokieli's ( https://dokie.li/ ) Share feature now includes:

* granting and changing access controls;
* copy URL to clipboard;
* sending notifications to contacts' inbox about the article.

Screencast: https://dokie.li/media/video/dokieli-share.webm

Implements:

* https://solidproject.org/TR/protocol
* https://solidproject.org/TR/wac
* https://www.w3.org/TR/ldn/
* https://www.w3.org/2005/Incubator/webid/spec/identity/

Source: https://github.com/dokieli/dokieli

#SolidProject #SolidProtocol #WAC #WebAccessControl #LinkedDataNotifications #LDN #ActivityStreams #WebID

I'm experimenting with "open with" at web scale using #SolidProject

Type registrations on my pod specify an app to use for a given RDF class, in the form of a uri prefix

When I search using #PodOS, a custom component links to the apps I can use to open the result.

Just like other OS, building "open with" into each of my apps lowers barriers to jumping to completely different resources, rather than just those the app can handle

In my #SolidProject feed reader, item cards and detailed views are built with #PodOS compatible custom components inspired by #Mavo

UI data binding connects a widget's value to a resource property RDFa style. Prefixes can be defined in a parent element

Loading an image:

<my-picture property="schema:thumbnailUrl">

Autocompleting a https://yaireo.github.io/tagify/ component with any object that has previously been used with the selected property:

<autocomplete-input property="schema:about">

5. what's the difference between protocols? i think @remotestorage for a more traditional technology stack; @fission for passwordless end-to-end encrypted and stored on #IPFS; #Solid / #SolidProject for storing as linked data to enable machine processing.

each has different approaches. the #ZeroData label encourages interoperability to make the pie larger for everyone.