Table of contents
- Notes of Weekly Meetings (every other Thursday, 15:00 CET)
- 2025-01-09 CoreDev meeting
- Questions about NextGraph integration
- Data Spaces and RDF Indexing
- APods and Solid frontend-only apps
- ActivityPub integration into Solid
- Memorandum of Understanding
- WAC Standard
- 2024-12-19 CoreDev meeting
- 2024-11-28 open meeting
- 2024-11-07 open meeting
- Notes for 2024-10-31
- 2024-10-24 open meeting
- Notes for 2024-05-27
- 2024-05-20 open meeting
- 2024-05-13 open meeting
- 2024-05-06 open meeting
- 2024-05-30 open meeting
- 2024-05-23 open meeting
- 2024-05-16 open meeting
- 2024-05-09 open meeting
- 2024-05-06 meeting with Hadrian
- 2024-04-25 open meeting
- 2024-04-11 open meeting
- 2024-04-04 open meeting
- FeStoDon (Application from French Academia Network planning to use APods)
- Testing in semapps
- Refactoring of collections
- 2-3 potential applications for APods (and potential fundings)
- Application idea : geolocalized message app
- 2024-03-28 open meeting
- 2024-03-21 open meeting
- 2024-03-14 open meeting
- 2024-03-07 open meeting
This file contains invisible Unicode characters that are indistinguishable to humans but may be processed differently by a computer. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
Notes of Weekly Meetings (every other Thursday, 15:00 CET)
We are having open bi-weekly meetings. In the meetings we demonstrate our current work progress for 20 to 30 minutes and leave room for discussion afterwards.
You are welcome to join if you are interested or want to talk about ActivityPub, Solid or beyond. We are looking forward to hearing of your ideas, questions, and thoughts!
⏲️ When? Every other Thursday at 15:00 CET (in even weeks, as of 2025-04-01 )
📌 Where? https://bbb.paquerette.eu/rooms/ass-hvm-tbf-usp/join
In the past we had core dev meetings every other week. You can see the minutes for them below as well. We have outsourced them to a different time to keep matters more focused.
2025-01-09 CoreDev meeting
Questions about NextGraph integration
How does client-side framework work, is it going to be based on React?
- The idea is to have a common abstraction that both nextgraph and Apods can use in the "back" (in case of NG it's the local client) and that different reactive frameworks can integrate (In react admin it's called data provider). Eventually, you can write your app with one framework and get compatibility with NG and APods
- For now, NG is going to be used as a triple store for APods only.
- Niko is looking for developer support (in rust)
What about braid.js?
- Criticism: http-only, no e2ee, no rdf and a single crdt method (text-based)
Data Spaces and RDF Indexing
Sylvain is going to work on that in the coming months with datami.
APods and Solid frontend-only apps
Frontend-only apps will soon be possible! Will support app of Noel de Martin https://github.com/activitypods/activitypods/pull/367
ActivityPub integration into Solid
We need to add use cases for the new linked web storage working group > Laurin will write use cases
Memorandum of Understanding
https://pad.lescommuns.org/GDwoZyzJSkGPnvaOlJrSqA
We need to sign it before the end of February.
Suggestion by Damon: Add a milestone for an Admin Dashboard. It's important to keep admins happy and make moderation easy! We need to ask NLnet if we can add another milestone.
WAC Standard
Should be changed, since not very practical. Niko: We are supposed to have a community call soon on that
2024-12-19 CoreDev meeting
Present: Sébastien, Laurin, Niko, Sylvain, Damon
WAC permissions
We realized that our WAC implementation are not compliant with the specs. We always look for the "default permissions" of the parent containers, but in Solid if we find an authorization attached to a resource (a document, even a blank one), we must NOT look at the parent containers.
There will be a Special Topic meeting in January to talk about this.
It may be difficult to make the WAC permissions evolve because now everything will be done on the new LWS working group ?
We need to check if we can do that with ACP. But ACP has no editor at the moment...
Maybe ask Pavlik how he uses ACP for default containers permissions ? (this is needed for SAI)
In the meantime, we are not going to change our way to handle default container permissions, because it would render our code much more difficult to maintain.
Troubles with proxy
https://github.com/assemblee-virtuelle/semapps/issues/1343
Good work from Sylvain, it has been merged !
Update on capabilities
We decided to go with VC, because ZCap is basically abandonned.
Laurin is looking through several libraries. They have advantages and disadvantages. One is by digital bazaar, the other one doesn't support multikey format.
Laurin talked with Niko about the format of VC. VC specs is not very specific about how to do it, the main purpose is more about authentication, while what we do is more related to authorization.
What is left to do is creating the capability, sending it through an activity (Create or Authorize ? to be discussed in issues maybe) and allow the user to invoke the capability.
There is a header in VC spec for this invocation.
Jesse is going to present at the FOSDEM something about having SPARQL queries with signed results (with VC) (with partial disclosure...)
Update on group storages
Almost finished with groups creation, deletion and settings: https://github.com/activitypods/activitypods/issues/357
Then I'll move on with completing SAI implementation, and first of all Data Registries.
Soon we should also have the possibility of having frontend-only apps, because the app installation will not depend on ActivityPub anymore, but will simply use the SAI specs. Noel de Martin has been reporting on this problem.
Security review processing
Most critical things are about SPARQL injections.
Maybe we can ask some more money to NLNet if it's a lot of work
Maybe use functions like "sparqlhere some ${var}" ?
Maybe use more SPARQL.js ?
Niko already did this kind of checks on the WAC services he implemented in 2021.
Update on NextGraph
Niko is planning to implement WAC permissions check in NextGraph by early next year. It will only be for Read queries, not Update queries, so we will still need to do more checks on the middleware.
It would be nice to talk about NextGraph during the FOSDEM ActivityPods presentation. The DID part can be interesting for them.
2024-11-28 open meeting
- There's a technical discussion about missing requirements of the Client to Server spec on the Social Hub forum
- we sould chime in on that!
- Sébastien has drafted an article on this topic already
- MastoPod is c2s only
- we need inbox collection filtering and applied for funding for that
- Steve has considered applying for funding for that before
- We have applied for funding on MastoPod in regard to that
- we sould chime in on that!
- Updates on Collective Online Datastores
- We talked with elf Pavlik about the Solid Application Interoperability spec, authorization, creating groups/organizations and sharing / granting data access
- APub is the easy part here, solid the hard one (not much specified in that regard)
- Mastopod (Sébastien shows a demo)
- Multi-language
- You can upload images to post, thanks to Sylvain
- Public and private profiles, and posts
- bookmarking <- and how is this standardized
- Blogging App updates
- People are starting to use it and give feedbacks
- Screenshots https://fosstodon.org/@laurin@mastodon.online/113403424238810069
2024-11-07 open meeting
Present: Sébastien, Laurin, Marc, Damon
-
News
- Sébastien will give a presentation at Solid practitioner meeting on December 5
- We are applying for a FOSDEM talk
-
CODs update
- multiple challenges:
- solid interop
- create features we need
- don't rewrite the APods framework
- we are going to do refactorings for the APods grant and we need to be cautious with collisions
- Should we allow users to create multi storages / Pods (not affecting multiple cods)?
- Séb: Besides refactoring issues, this might be hard in regard to UX
- Though it might be useful to split WebId storage and rest data storage
- implement solid OIDC
- manage list of owners for resources
- how do we manage app, organization, user WebIds
- sub-groups: Do they have separate WebIds? What about ACLs here?
- SAI apps and organizations - who authorizes / "installs"?
- SAI also allow delegated grants, that would be useful at some point.
-
reactive frontend (moved to later)
-
beginners meeting: there is a person interested from GEN Europe, there were no responses to Laurin's poll
-
cdlt querying for blogging app object suggestions: probably we can create a
Serverin react admin otherwise a custom SPARQL query
Notes for 2024-10-31
Present: Bumblefudge, Sébastien, Damon, Laurin, Guillaume
Capabilities
Niko and Laurin talked about APods implementation of a capability-mechanism to delegate activity-related authority. We did research on OCapN and considered UCAN and ZCaps and concluded that zCaps seems to be the best fit since it is a thin layer, uses RDF and is closely related to the VC, object Integrity, etc. specs. Related FEPs
- https://codeberg.org/fediverse/fep/src/branch/main/fep/8b32/fep-8b32.md
- https://codeberg.org/fediverse/fep/src/branch/main/fep/521a/fep-521a.md
We will probably write a blog post about this at some point.
Native framework for APods?
- For v3, we will separate the frontend components, so they are usable independently from Apods (in other solid environments). So other solid libraries will be compatible. Same goes for AP Client-to-Server libraries.
- It might be hard to maintain another framework implementation.
Timeline for MastoPod
There will probably be another developer joining us, to help with improvements for MastoPod. We will likely get funding for this.
2024-10-24 open meeting
Present: Laurin, Alice, Sébastien, Marc
New meeting for App devs
- A one in French and soon another one in English.
- Laurin will find a date
LDO and typings
- Goal to use for type safety in back- and frontend
Collective Online Datastores
- Sébastien has been drafting questions on this
- Sébastient going to look at Community Solid Server, to see how they handle separation of identity and data store
- Will share a document about how solidweb.me is doing it
Notes for 2024-05-27
Present: Damon, Sébastien, Laurin, Carty
- Brief update of Solid notifications
- Push and pull notifications to watch for resources and containers changes
- Also a way to watch for collections
- Laurin implemented Websockets and Sébastien already implemented Webhooks
- Works with Mastodon, but also comes automatically for applications that use the useCollections hooks.
- Laurin is going to help Niko on NextGraph in the next few weeks.
- Added cache for Mastopod and ActivityPods frontend. The "stale time" was missing.
- docker containers and developer experience
- Sébastien created docker and docker-compose files for making it easy to set up pod providers.
- docker files for all application parts (frontend, backend, welcome to my place, ...)
- There was an issue with environment variables for the frontend: Since the frontend is compiled to a bundle with the .env variables in the binary, he had to create an API that translates the .env file to dynamically loadable json
- testing / developing: app developers will be able to use docker images of APods instead of cloning the repo and setting everything up manually
- Sébastien created docker and docker-compose files for making it easy to set up pod providers.
- DIDs in APods with NextGraph?
- With NextGraph, every named graph (resource) has it's did indentifier, containing a public key. The same will be true for WebId resources but there are some discussions open on how this will end up.
- Federated timelines - is that feasible with APods
- Not in the same. What makes more sense is to have content aggregators apps which collect activities from users. The user will have to authorize a dedicated app to share certain activities. The app backend would listen to those events and could generate a shared feed from multiple users this way.
2024-05-20 open meeting
Present: Damon, Sébastien, Laurin
- How would content annotation / labelers work?
- Labelers should be completely separate services that you can subscribe to / fetch for content of interest. The original activities shouldn't be modified
- Clients or Apps can manage the annotation information correctly in regard to UX/UI
- Dan (Pixelfed) would like to consider APods as a messenger app, called SUP.
- APods for transport & storage; encryption would have to be done client-side
- What is left for 2.0?
- migration of WelcomeToMyPlace, documentation, tutorials, app boilerplate, logic and frontend for apps with changing access needs
2024-05-13 open meeting
Present: Damon, Sébastien, Laurin
Updates on issues Sébastien was tackling
- Invitations for events from WelcomeToMyPlace to someone who hasn't installed it -- users should be able to disable messages from there.
With APods2, installing the app will create new container(s).
If you get an invite, your pod will store it for you. However the container hasn't been created. 2 Options:
- Either create a collection even without having installed the app (dirty solution, easier for now)
- Or iterate through the inbox for old events once installing the app
- Seb changed the ldp registery so that every pod has its own registry. This makes sense since apps like wtmp are external but it makes it hard again for pods without the app. Using controlled containers everywhere makes startup slow having to register every route into cache. Alternative: type index (preferred)
- announcer service (later to be changed to capabilities): problems with concurrency and authorization and information that might become available after some time - sending an email notification the event to others might cause problems because not all data and permissions are available yet
- In solid we are not able to mirror remote resources. With APods is possible though using mirrored graphs. This makes querying and filtering data easy. E.g. for finding contacts and searching infos about them. Sébastien will ask the solid community how they handle this caching issue (if they do).
Solid Notification Protocol & WebSockts (Laurin)
- Laurin has implemented a new moleculer-web service mixin to support registering websocket routes.
- He now creates a service to support the Solid Notification protocol over a WebSocket channel (currently only hooks are implemented). Note: He could check, if we can implement support for pings / polling to check, if web hook connections are still alive.
Others
Laurin received work opportunies, one for frontend work, one for creating an APods based blogging app.
2024-05-06 open meeting
- Present: Damon, Laurin
- Nlnet Submission finished
- Sébastien on leave
- discussion on moderation in APods
- Currently we have basically no moderation tooling
- Damon raised the issue that moderation of instance administrators (for non-illegal content) has the threat of patronizing users. More fine-grained methods using e.g. external lists as done with ATProto is a more sensible approach. Laurin agrees.
- Laurin low on money right now and is looking for job opportunities until the next nlnet grant comes
2024-05-30 open meeting
ActivityPods and Nextgraph updates:
- On Monday, there was a meeting with Niko, about milestones on NextGraph integration (relevant for nlnet application)
- A lot of new issues were created, mostly on semapps, e.g. https://github.com/assemblee-virtuelle/semapps/issues/1263
- One issue is that in nextgraph all graphs use cryptographic identifiers (
did:ng) which will need to be mapped to http URIs. So all URIs will have a cryptographic URI now.
Cooperative for ActivityPods
- Future idea
- One motive is to foster maintenance, refactorings, community and application ecosystem.
- nlnet is great but does can't finance maintenance work
- We will need a lot more stability before growing. This is something we can and should do after we finished with version 3
NLNET
- Application almost finished, will be sent tomorrow
Others
- there is a person running a company hosting single-user mastodon instances. He's willing to give away 10,000 USD for a deviant art alternative based on AP. APods could be a good software to use here.
- There are probably a lot more of those initiatives coming up in the next time
2024-05-23 open meeting
-
Updates from GENeurope
- ideal: every eco-community has its own COD, every person has a POD
- share a common mindset on how data is to be shared rather than gathered
- applied for funding which we can benefit from by helping them with development
- maybe they can get funding for developing CODs and then as a second step on top of this apps like classified ads
-
Update from CG
- Could become a Special Topic maybe together with slash-semantics
- Collides with the hierarchical problems. Looks like an open issue for them.
- Sympathy for storing nquads
- Some people discovered the possibility of triplestore storage !
- Would be less GDPR compliant to do it on the client side.
-
NLNET submission
- There's a call on monday about NextGraph integration and defining milestones in that regards
- Submission almost finished. Some github issues to be created
- ActivityPub groups, Bluesky compatibility, DID, etc, could be put in another grant request. Groups more relevant when we will have CODs.
2024-05-16 open meeting
- Talked about fixes for failing unit tests in the key service with version 2.0 branch
- Discussed what is left to do for the nlnet application for June.
- We are going to start with ~15min technical meetings on Mondays, Wednesdays, and Fridays (on demand) to update each other regularly on what we have been or are going to code so that it's easier to coordinate, get opinions, and not interfere with each other.
2024-05-09 open meeting
-
Sebastien at solid symposium in Belgium
- spoke with people from muze.nl - they plan to create a pod provider in php with AP support
- one of the workshop take aways: solid will need a stronger ecosystem of apps, not only the one killer app
- sebastien raised critique of hierarchical pod structure, he also posted an issue (see also https://github.com/assemblee-virtuelle/activitypods/issues/220)
- talk on data space - they seem to put little effort in data privacy and the intentions are rather to put data together and create value from that. The goal is to agree on APIs within the industries. Also they want support for law-enforcement access.
- Chat about dev experience: https://hackmd.io/cR9W1RiyQX61eYN6JLAwLw
- Workshop from the creator of https://m-ld.org/
- Generally, people from solid world have trouble understanding AP
-
nlnet grants
- most projects from the current grant are finished
- the application is due on first of June
- For the next grant, we will apply for issues around
- removing Fusekis WAC plugin dependency
- solid compliance
- NextGraph compatibility
- LDO support (frontend and backend)
- making semapps frontend packages compatible with any solid pod
- Linked Data Fragments (?)
- Collective Online Datastores
- Importing data from another pod or Mastodon account
2024-05-06 meeting with Hadrian
Sebastien was at the Solid Symposium
-
Talked with a lot of people on AP and solid topics
-
Talked with Sarven about AP and Solid
- goal is to add more glue between solid and AP, Hadrian notes that AP should not become a part of the solid spec but that solid notifications do not cover a lot of common use cases
-
Another company is planning to use Pods with AP, so there might be a second implementation on its way in a while
Hadrian had brought up the idea of the management API at the Community Group meeting
- Positive feedback
- issue: resource constraints - who can work on it?
- it's going to be put on the agenda again, Sébastien is going to join next meeting
Pod Export
- Exporting Pods (Laurin will work on this) - frontend app traverses ldp containers vs backend
- server-side (preference): backend can handle compression and supports asynchronous processing; backend can sign the export; faster
- client-side: you can't guarantee, if the content of the pod is authoritative and complete; how do you deal with large files?
- also, we need to differentiate between archive structure and the way you build it (git repository style)
- There have been discussions on this, Hadrian will send the links and put it on the agenda for the community group for Wednesday
Other technical discussions
- structure of webId URIs: URIs tie you to a DNS domains.
- we should separate between identity, address, identifier
- ideally, the URI slug should be globally unique (to not be dependent on provider); those problems have been solved before - rather than the current webId spec, it might be better to instead state requirements to be fulfilled (e.g. like with DID, public key encoded in webId, so that two webIds with the same key but different domains are treated as the same entity)
- Concept of pods with cdn - how do you manage permissions for intermediaries
- Seb: Ideally, pods should talk to each other directly
- issue with routing and identifier; Hadrian really happy about: https://keri.one/
Action items
- put together use cases for solid -- what does this imply in regard to a pod management API
- e.g. read, right, migrate, trusted apps, ...
2024-04-25 open meeting
Laurin has been finishing the key and migration service. Some unit test cases for migration to go still
Memory (Damon)
- moving albeit not as fast as hoped
- looking at implementing proxies to fetch data for clients (same as with apods)
- studying relays for custom feeds
Sebastien met with Hadrian about pathways for APods on Monday, now every fortnight
There was an issue with mypod.store which prevented server from starting due to database inconsistencies. Fixed for now. Laurin creates an issue to fix inconsistencies and prevent them from stopping startup.
2024-04-11 open meeting
- Quad stores and Fuseki
- we have fuseki 3.19 (?) running; fuseki is on version 5 or so
- Right now, new graphs can be created with SPARQL but need to be set in the configuration to be persisted. It's not really been designed for the use case to have a lot of named graphs, at least not in our version.
- Semapps uses one default graph, one named graph for acl, one for mirrored (cache) resources.
- we can add an application for refactoring to the grant (will require research on details). We will probably want named graphs, to support RDF resources, that is triples with multiple resources (named gaph is equivalent to the resource name).
- oxigraph has the downside of not supporting multiple datasets per instance (would require multiple app instance) > to investigate
- discussion on rdf star (statements about triples) vs named graphs / quads
- What's left for version 2.0?
- migrate welcome2myplace (Sebastien)
- check documentation for migration
- GDPR compliance: delete and export pod data (Laurin)
- documentation
- final tests
- Will be finished on 1st of July maximum
- migrate welcome2myplace (Sebastien)
- News from Hadrian
- We had a meeting on Monday. He supports the project with advocacy and suggestions for progressing the project, e.g. funding models, community work, ...
- We're creating action items right now.
- Another meeting about project FeStoDon with the french academia consortium, to discuss tech requirements
- ideally we would need 2 devs, one back- one frontend
- they need versioning / journaling for resources
- they are asking for 1 million, could fund development for 2-3 years
- first, this will be used as a test for a dozen of labs, to see how well it works
- Their objective is to increase cooperation between research labs
- Sebastien had meeting with https://letsco.co last week that is considering to develop their next application with ActivityPods
- Developer Experience and RDF Typing
- Laurin considers using LDO (Linked data objects) or ldkit in the future. It has typing support. You don't need to worry about JSON-LD formatting (with prefix, with URL, without anything...)
- We need to evaluate how much time it would take to setup and maintain
- Things to apply for in the new grant request
- We'll talk about it another time
- Updates from Memory
- Setting up a fork of Mastopod with IPFS data store
- they got an ios dev
- more to come next week :)
- PadPod / PodPad Application Idea
- https://github.com/assemblee-virtuelle/activitypods/discussions/209
- idea to have application for pads in ActivityPods
- will require real time crdt handled by app backend
- maybe worth checking out https://dokie.li/ and https://cryptpad.fr/
- feel free to post other app ideas on the same category
2024-04-04 open meeting
- FeStoDon
- Laurin: Testing in SemApps
- PodService or not
- Sebastien's refactoring of collections
- Julien: 2-3 potential applications for APods (and potential fundings)
- privacy & consent
- indexing digital commons (world commons catalog)
- collective open datasets
- Sébastien: idea for geolocalized message app
FeStoDon (Application from French Academia Network planning to use APods)
Contacted by EHESS, building a consortium with the CNRS and other academic players. As academic actors, they are going to apply for a call for project. They want to make an application for researchers based on ActivityPods. They are major players in the academic field, and they have good chances to be selected.
Open Science / privacy / decentralized communication between pods / share data between services /
Potential additional resources to hire developpers for APods
Challenges : increasing security / versioning / user interfaces /
Next steps ? : submit application on may 2d 2024 / goal : write the grant application beforehand / sync w/ the project leader to identify where to contribute on a technical aspect or scientific dimension /
More infos about the project here
Testing in semapps
- Unit test on key servers - should they use the semapps pod service?
- The pod service might migrate to APods in the future, so if we need additional pod-integration tests, add them there.
- Unit test vs integration tests
Tech channel on Matrix ?
- Laurin will add new channel and rename newbie to implementer's / users channel
Refactoring of collections
PR containing this current work : https://github.com/assemblee-virtuelle/semapps/pull/1242
Add items to collections (activty stream spec : follower collection / like collections / replies .... )
Collections are added automatically but need for creating collections (i.e. events)
All what was in the APods backend side is being moved to the application part
Refactoring on the registry
Options of the collection: sorting, etc... Before it was used on the memory
Main idea: push this feat to integrate it into ActivityPub spec itself
Sebastien happy :) : it was a feat he wanted to integrate since a long time
https://activitypods.org/specs/solid/#patch-method-
Collection is not a container, it's another way to store data. You can't post to a collection (items are uri linked to the container ?).
2-3 potential applications for APods (and potential fundings)
-
Met several actors in Canada, including Digital Transparency Lab: https://www.transparencylab.ca/. There is new regulations in Canada inspired from EU regulations (DSA, GDPR...). A new way to consent on services online (alternative to the "I accept the CGU"...). Decoupling between what the company saves in their database, and what is saved on the user's data space. ActivityPods is a really interesting solution for this kind of usage. cf : https://docs.google.com/presentation/d/1dyRuz8gtl_-retPOSe3UdYBjbmM9kmaG4IQliNUqDdQ/edit?usp=sharing
-
Use ActivityPods to create some kind of "digital commons catalog". Trying to find a way to fund this kind of project.
-
Collective online datasets. A application grant was deposited to NGI (Commons Fund) : https://commons.ngi.eu/. Use ActivityPods to store decentralized data. One challenge would be to allow to create CODs (collective online datastore), another would be to create a frontend that is easy to use. Ideally something close to Git. cf : https://docs.google.com/presentation/d/1kkzJ5nx5EtPz9nFNUVBCsoukzuCtLb88gH7irEmN2BE/edit?usp=sharing / https://docs.google.com/spreadsheets/d/1QN0zkzjrJf4nJ3klgzz0FXDw0l-SRD6u6r83_6NsDCA/edit?usp=sharing
Application idea : geolocalized message app
Yaourtophone (~ "tin can phone")
Messages only for people close to you geographically (in a radius of 10 km for instance) / distinguish people having received or not the message
Idea's roots : Guillaume lives in a countryside / group of people are spread on the territory / some message subjects are more relevant for people near you.
A POC to show off what could be done w/ APods.
[name=Julien] - Idea to invent a FLOSS and decentralized dating app
question about privacy : would it be possible for an user to choose to share its location or not / with whom ?
2024-03-28 open meeting
Agenda
- Chat about the merits of ActivityPods (sorry, not everything documented here)
- Migrating data between pods / AP accounts
- One account for multiple purposes
- spec compliance and interoperability
- Opinions on Solid
- should public data be stored in the same format / way than private data (sub question : is solid adapted for public data?)
- How do federate / pin / share data in solid?
- with https://app.syreen.fr/, data made public by changing the WAC-(web acces control) permission is shared with an aggregator pod as relay (semapps ldp server)
- The aggregator can be used to view the data (aggregators have the possibility to server different purposes)
- OOD and COD (Open online datastore; Collective online datastore)
- data stored with public or within organisation, respectively
- What is public vs private vs inaccessible data in AP vs Solid
- Using data for private purposes (e.g. login with my solid pod, store new data there)
- Using data for social purposes (ActivityPub) (e.g. talk with my friends, my family, etc).
- Using / advertising data for platforms like ebay
- Publishing data for public purposes, e.g. scientific data, wikidata
- what is your objective in medium term?
- deliver activitypods 2.0 before summer
- ask for grant on 1st of June (work done with several developers)
- developers (a lot of issues open in semapps, we could use 10 devs)
- grants
- more applications using APods
- Support multiple / other triple store / quad store
- More compatibility with solid
- stability
- security
- documentation
- credibilty
- scalability
- APods has a great opportunity to have global impact: access to huge userbase and various applications; social communication, (Social) data storage; data sharing
- What's the purpose of showing of Mastopod as APods app
- Show that it's easy to have one account for multiple purposes
- show that it was easy to implement, since you only need a client to implement
- quicker and easier to build applications with access to existing data and users
- Damon on AP relay to test
- following mastodon hashtags, instances and similar (mastodon streaming api -> AP actor (https://github.com/astro/buzzrelay)
- next: allow-list federation & authorized fetch
- goal: allow more granular content-control (e.g. filtered by criteria other that hashtags) -- bluesky in comparison has support for custom feeds right now (e.g. about ice cream)
- goal: add outbox to add support for relaying AP activities
- new "my data" explore tab on native APods client: https://github.com/assemblee-virtuelle/activitypods/pull/190 with i18n translations for the data
- new draft by Sébastien "big data to proximity data" https://docs.google.com/document/d/1akCvhbx--4-7TczogUcyHu0tfnENaEcl/edit?usp=sharing&ouid=117895457416604421615&rtpof=true&sd=true
2024-03-21 open meeting
Hadrian Zbarcea attended who is currently community manager at Inrupt, among others.
- He's very interested in the project and was sharing ideas about import and export across different pods and about a no-login / ssh-style login structure for a basic local-first pod server, e.g. for testing-purposes.
- He also offered to add AcitivtyPods to https://solidproject.org/apps and https://solidproject.org/users/get-a-pod
- And he advocated for participation in the current solid hackathon: https://solidhack.org/ (possibly for pod export and import)
- Other topics we touched and for future discussion: Portability of WebId, Import and Export of Pods
Sebastién was at FediForum and gave a 5-minute introduction to MastoPod. Afterwards there was a workshop and some basic notes were taken: https://notes.qiqochat.com/p/cc1-GrcfqOqdeUGrFpqgSmSruwvtc-cuWMJ-2-4?showControls=true&showChat=false&showLineNumbers=true&useMonospaceFont=false&userName=Sebastien%20Rosset&embed=true
Damon was interested in possible ATProto PDS (Personal Data Store) integration with APods and opened a discussion. Same for Nostr, which is a very straight-forward, simple protocol that works with relays (discussion). Since everyone is quite busy at the moment, this might take a while to progress.
2024-03-14 open meeting
-
Migration from Community Solid Server to Semapps / APods (Maxime) & Solid Compliance
- Maxime is working on Startin-Blox for indexing using communica (https://comunica.dev/)
- Maybe Maxime could work on that since Sébastien is too busy
- Theo and Sébastien talked about developing an extension for Community Solid Server: It should be fairly straight-forward since it is built modularly using js classes
-
NLNet funding
- Deadline 2024-04-01 (the one after that is in June, NLNet recommended to apply before)
- Release for 2.0. is taking longer
- Funding request for making APods triple-store agnostic
- This could support quad-store and bring us closer to Solid-LDP-Compliance
- And we could use Oxigraph
- Sébastien is not sure if he can write an application by April.
- Guillaume offered support and will talk to Maxime
-
Updates on MyData Tab in APods client
- Video here: https://github.com/assemblee-virtuelle/activitypods/pull/190
- In the future, deleting / viewing permissions should be possible
- Since many properties are rather boring for end-users we might have a developer-view option (which could also allow to view JSON-LD and Turtle data)
- Sebastien will present at fedi forum
-
Sébastien is going to write a blog article about his learnings from implementing an Apods Mastodon client
-
Review Comment from Sébastien on Damons latest comment on custom subdomain webids
- https://github.com/assemblee-virtuelle/activitypods/issues/192 For now, the feature request is mostly intended to support webid / actor addressing with custom subdomains, e.g. https://alice.mypod.store
-
Memory
- The team is partly based in Nigeria, partly USA
- 2 developpers
- Mostly going to be open-sourced (excluding UI)
- Work so far has mostly been on research, design (UX, UI largely settled), engaging with communities, and planning
- NLNet might be a place to apply for funding for the backend (they prefer research and development work)
-
Future discussion: Becoming more protocol-agnostic (looking at popularity of bluesky/ATProto etc.), c.f. BridgyFed (user-level translator) Cf Granary : https://github.com/assemblee-virtuelle/activitypods/issues/184 (maybe something for requesting grants from)
- Adopting different communication protocols should be fairly easy.
- Adopting alternatives to Solid is hard, since Solid define everything about how we should store data, handle permissions, etc.
2024-03-07 open meeting
LDP Registry
Goal is to dereference the public key in the WebId, because Laurin is working on key management (for LD signature and Z-Cap).
- LDP registry code: https://github.com/assemblee-virtuelle/semapps/blob/next/src/middleware/packages/ldp/services/registry/index.
- There is a ControlledContainerMixin (https://semapps.org/docs/middleware/ldp/controlled-container), but the WebID is not using it. So he wants to refactor it to use it.
- WebID is used for Pods and non-Pods configuration. It's probably better not to "fix"
- LDP Registry needs to be better documented (on SemApps website or in-line comments)
Self-hosting
People are worried about having to choose a Pod provider, and would prefer to have their own self-hosted Pod Provider (with only their account).
- This is something we plan to offer
- Mastodon offer an installation for one-account instances
- Damon will create an issue about this subject.
Mastopod presentation by Sébastien
https://github.com/assemblee-virtuelle/mastopod
- Took around 3 working days to code until now
- Uses client-to-server API and supports foreign account infinite scrolling (in comparison to Mastodon). We think we are the only one to do that ! Required to pass through our proxy to solve CORS problems, and also because some Mastodon servers are running in "protected" mode, which require HTTP signature to fetch objects.
- We fixed Mastodon-compatibility problems https://github.com/assemblee-virtuelle/semapps/pull/1238
- We improved
useCollectionhook to handle infinite loader. Loading inbox, outbox or followers/following lists is now very easy, thanks to react-query. https://github.com/assemblee-virtuelle/semapps/pull/1237
Presentation of Memory by Damon
- Focus on UX
- Selection of communities
- Use Signal protocol for encryption
- Side Note: There's a new article from Inrupt team about Solid & E2EE: https://www.inrupt.com/blog/solid-e2e
- More questions maybe next week!
NLnet
Call between Sébastien and employee at NLnet.
- Funding Requirements: Mostly, they can't fund pure maintenance work, in contrast to what the name suggests.
- They talked about the worries of where Solid is going and that it hasn't gained wide-spread adoption. Doubts were also expressed, if ActivityPub is going to make the race and attract majorities (over ATProto for example). But since APods is very modular, it should be possible to change protocols if the time requires to or to use bridges
My Data tab
- Sébastien is going to implement a new tab on the ActivityPods frontend app that can let users browse the data in their pods.