Been thinking about [fediverse wiki] after @2chanhaeng@hackers.pub mentioned it today.
Technical Discussion
7
Posts
6
Posters
20
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 hongminhee@hollo.social shared this topic on
-
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
-
Polls are rendering!
screenshot of the latest emoji poll rendered on the ktistec serverI'm working to get all of the little visual elements available across the Fediverse to render in a usable way on Ktistec. When released, users will also be able to vote on polls.
-
Okay, I've setup https://notes.socialcg.org/about
-
@julian i'd say the confusion is primarily that we've shifted topic around several different things and i'm still not sure which is the intended topic of the discussion :x
- deleting posts that are in a thread
- removing posts from a thread
- implications for downstream posts in a thread when some ancestor in the reply chain is deleted/removed
- deleting a thread that is in a forum
- removing a thread from a forum
- moving a thread to the "uncategorized" forum
- ...?
-
@julian if the intent is to signal what happens when nodebb moves a thread to "uncategorized", then i think the simplest thing is for nodebb to treat "uncategorized" as a forum in itself, still. you already assign them an id of -1, so you are in effect treating the "uncategorized" category as a category still.
-
@julian the confusing thing to me, though, is that both Delete and Remove already don't imply anything about posts in the thread if the thread is deleted/removed from the forum.
by default, if you Delete a thread, the forum might still have a broken link to the now-deleted thread, and the posts also have broken links to the thread.
by default, if you Remove a thread from the forum, the posts still exist within the thread.
-
trwnh@mastodon.social specifically however, is that you're not deleting the context. Just removing it.
NodeBB has the concept of a context not belonging to an audience (the "uncategorized" pseudo category.) in those specific situations, contexts would be removed from the audience, not deleted.
Lemmy and Piefed don't have these concepts, so they simply delete them. So therein lies some of the confusion I believe.
-
@julian like removing a whole thread from the forum? Remove(object=thread, target=forum)? this seems like something altogether different than removing posts from a thread.
removing threads from a forum is possible but if the thread is owned by the forum then the forum can also delete them.
the part that differs between impls is whether Delete(thing that is a context) should do anything to objects where context = the Delete.object, right? i think it makes the most sense to just orphan them.
-
trwnh@mastodon.social it signals that the actor is removing the context from the targeted audience.
The audience can optionally announce it, and receivers synchronizing with that audience (per 1b12) should follow suit and remove the context as well.
