@ujeenator Exactly. Key custody is also possible, but currently the work is focused on non custodial solutions.

Added Nomadic ActivityPub page to the ap-next repository:

ap-next/nomadpub.md at main

ap-next - ActivityPub Next

Codeberg.org (codeberg.org)

This is a brief summary of the work we've done. Feedback is welcome!

#NomadicIdentity #fep_ef61

@julian

I still don't understand what is so great about this document.

Many fediverse applications are capable of publishing long-form text and they are interoperating. Mastodon had a couple of issues that prevented it from rendering certain HTML tags and prevented it from showing summaries, but those issues have been fixed. It is not clear what else could be improved.

For the most part, this FEP repeats definitions from ActivityStreams vocabulary. It introduces the useless preview mechanism. It also undermines the efforts to standardize thread backfilling by defining context in a different way. Am I missing something?

@benpate

@julian It has to be accepted manually. I just did that.

@pernia @nomad Good to know!

@xwyqi @nomad It uses JSON-LD processing:

Iceshrimp.NET/FEDERATION.md at dev

Iceshrimp.NET - This repository contains our efforts to continue the Iceshrimp project's legacy - in the form of an entirely new codebase, with a focus on performance, stability and maintainability.

Iceshrimp development (iceshrimp.dev)

This is unfortunate.

@mikedev @nomad The most unusual thing about this actor is not funny ID, but a lack of @context. Mastodon doesn't like this, for some reason

@julian The next test is to follow it

@coolboymew I made a post for you too

@nomad @liaizon

@citc @nomad Nice

@steffo You are running chuckya fork, right? This might explain the difference

@nomad just made a public post mentioning you, do you see it?

@liaizon It might be showing a cached version.

@nomad just made a public post mentioning you, do you see it?

@gabriel @nomad Kudos to misskey devs

Which Fediverse services can see this actor? @nomad

It looks like Mastodon can't parse it, what about others?

How it works between forums, e.g. between Discourse and NodeBB?
Can a Discourse user create a topic in NodeBB category?
Who creates/owns the context collection in this case?

If I create a topic this way, I will be the owner of the context collection. But if the conversation is to be moderated, it should be owned by the group.

Am I correct?

(there is a parallel discussion happening at https://codeberg.org/streams/streams/issues/229)

@julian Does NodeBB support creating new topics by mentioning a group/category?

I wonder how context should be assigned in this case.

@julian @hongminhee @lobsters It is a machine translation from Korean, the original might have been written by a human. But the structure is the same, yeah.

@hongminhee

APx is finally available on crates.io / docs.rs

apx_sdk - Rust

Minimalistic ActivityPub toolkit written in Rust.

(docs.rs)

This is an ActivityPub library used internally in Mitra and in other my projects.

Unlike some other ActivityPub libraries, this library is low-level. It doesn't restrict what databases or frameworks could be used, and doesn't care about object types or properties. There are only URIs, keys, signatures, JSON documents and HTTP requests.
It also contains primitives for building nomadic applications (FEP-ef61).

The license is AGPL-3, but I might consider changing it to a more permissive one.

#apx #activitypub #rust

I think it's important to get an Announce, because the actor who addressed the community might be blocked by that community, or might not be a member of it (if the community is private).
You can try to retrieve the outbox of the addressed community to verify that a post was actually Announce'd

@activitypub