Been thinking about [fediverse wiki] after @2chanhaeng@hackers.pub mentioned it today.
Technical Discussion
7
Posts
6
Posters
3
Views
-
Been thinking about fediverse wiki after @2chanhaeng@hackers.pub mentioned it today. Some ideas:
- Cross-instance page linking:
[[Page Title@other-instance.wiki]] - Edit pages on other instances with your home account
- Fork pages across instances:
[[Page@instance-a.wiki]]→[[Page@instance-b.wiki]], sharing edit history up to the fork point
- Merge forked pages later when needed
The fork/merge model feels natural for federated collaboration. Thoughts?
#fediverse #wiki #fedidev #ActivityPub
- Cross-instance page linking:
-
@hongminhee @2chanhaeng Have you heard of ibis? It seems to have already implemented everything you envisioned.
-
@hongminhee @2chanhaeng There is an activitypub application/extension for xwiki https://extensions.xwiki.org/xwiki/bin/view/Extension/ActivityPub%20Application/
I have no idea how well it works
-
undefined 洪 民憙 (Hong Minhee) shared this topic on
-
hongminhee@hollo.social There's Ibis
-
If you're doing
Title@other-instance.wikithat seems to imply that you may be doing webfinger to find the article on the other server? I'd probably not recommend this, since article titles can and do change. You'd probably want to define a "search" endpoint on the instance, and then call that, and maybe you'd write it as:[[:other-instance.wiki:Page name#Section name|Displayed text]]where all you need to do is type[[:other-instance.wiki]]and it gives you UI to search for a page name on the other wiki, and automatically fetches the title to display. When you store the page in the database, you'd store the mapping of:other-instance.wiki:Page name#Section nameto the Object URI for that page / section. (Since AP objects are only mapped to URIs)For doing forks / merging, you'd likely want to keep a CRDT of the changes made, e.g., using AutoMerge: https://automerge.org/
Then the edit collection would contain an ActivityPub representation of the CRDT changes, e.g., some serialization of https://automerge.org/docs/reference/documents/rich-text/
That would allow serverA to merge in serverB's edits, even if the article on serverA had been changed.
-
Though, tbh, someone should probably create a ActivityStreams 2 type for "plain text with facets" where the facets are essentially byte offsets in the plain text, which would enable supporting formatting of course, but also links, mentions, etc.
The content could then still be rendered to HTML, but the source would still be there as an attachment with as plain text + facets + attachments for media.
-
@hongminhee @2chanhaeng I see you already got some comments of this nature but was gonna point them out as well. Ibis is the farthest along but Xwiki was the first to add AP to a wiki that I know of. Also Piefed has an added wiki feature for every community but I don't think they federate that part yet.
Gli ultimi otto messaggi ricevuti dalla Federazione
-
If we're going to be publishing activities regarding resolvable context collections then it may be time to introduce a new object type.
It would be backwards compatible with f228 OrderedCollections... using the new type would signify support for the various activity types perhaps...?
Edit: if this is what you were proposing with client managed collections, then my apologies 😅 the naming threw me off
-
Another solution: introduce a new object class, client-managed collections. These collections should have a property that differentiates them from server-managed collections, e.g. isClientManaged: true. And they shouldn't be paginated.
I think this would be compatible with client-side signing.
But companion object solution seems to be cleaner.
-
@julian that might be it, yeah. languages outside of javascript generally don't make a distinction between null and undefined, and even in javascript these are used inconsistently. for example localStorage.getItem will return null for a missing key. practically speaking, the "intentionally" distinction is a distinction without a difference in most processing contexts.
-
trwnh@mastodon.social undefined and perhaps that's why we're disagreeing on our interpretations of how these values should be handled.
null in JavaScript is very explicitly a declaration that there is no value or "intentionally empty".
null and undefined are two separate things here at least.
-
@julian what does js return instead? in most cases i'm familiar with, programming languages use null or nil or None for anything that doesn't have a value, or any reference which doesn't point anywhere. hence a null pointer exception when you try to dereference a null. if you try to get a value for a key that isn't in the dictionary, you get null by default because there is no value for a missing key. how would you consume a null value? if you have nothing to say, why say anything?
-
trwnh@mastodon.social I'm coding in js, which has all sorts of footguns, but even that won't return null when I attempt to access the non-existent property of an object... 😛
-
@julian this wouldn't be your AP lib, it would be your programming language itself
-
trwnh@mastodon.social as someone working on the consuming side, that is not correct.
If my AP lib automatically assumed null when requesting an object property that didn't exist I'd consider that a bug.
