Notices by silverpill (silverpill@mitra.social), page 13

@monerobull @monero @owe_addams

>their garbage tier mascot

Wait, zcash has a mascot?

@elvecietemergency @streams @einer @mikedev This is probably caused by Mastodon: https://github.com/mastodon/mastodon/issues/31921

@hollo Adding Hollo to FEP-e232 implementation list: https://codeberg.org/fediverse/fep/pulls/392

@jenniferplusplus @samsethi @julian Pleroma uses Listen activities to display "currently listening" status: https://docs-develop.pleroma.social/backend/development/API/pleroma_api/#get-apiv1pleromaaccountsidscrobbles
I think this activity can also be used for counting podcast listeners.

@Hyolobrika https://links.hackliberty.org seems to fit the description

@sun FEP-521a is supposed to be used in situations where identity is based on a domain name (HTTP signatures, FEP-8b32 integrity proofs on non-portable objects).

If you want to have a key-based identity, you can keep your identity key on a client as described in FEP-ae97. It works roughly as you said, HTTP signing keys are generated on a client, added to actor document via FEP-521a, and then shared with servers for delegated HTTP signing (we're doing it in a hacky way, that needs to be improved).

>encrypted messages

The most well-thought proposal I've seen so far is https://github.com/soatok/mastodon-e2ee-specification but it's completely unrelated to what I'm doing with key-based identity

@mischievoustomato Verify that your storage_dir points to a new location https://codeberg.org/silverpill/mitra/src/tag/v3.5.0/config.example.yaml#L11 (media is stored in <storage_dir>/media)

@mischievoustomato @tk @graf @anemone @sun @J 100% committed. I'd say we're just getting started

@gvlx @mariusor The blockchain integration component? It's going to stay in Mitra codebase. A small amount of related code is present in apx_core (encodings and cryptographic primitives), it is not for payments, but for experimenting with client-side signing.

I agree that it would make more sense to maintain this library independently. Will do this before publishing it on crates.io

@LaurensHof

>I’ve split all news about Bluesky and the ATmosphere into it’s own separate newsletter

You did the right thing. Bluesky is not part of Fediverse, and shouldn't have been included in this newsletter

I'm working on a Rust library for building ActivityPub apps:

https://codeberg.org/silverpill/mitra/src/branch/main/apx_sdk

This code was originally a part of Mitra, but over time I moved re-usable functions into independent packages and then started using them in other projects, Activity Connect and fep-ae97-client. Compared to activitypub-federation-rust, it is a low-level library with fewer dependencies, suitable for both servers and clients. The key feature is support for nomadic identity.

Currently there's no documentation and API is not well designed, but I will be improving it. The license is AGPL-3.0

#fedidev #fep_ef61

@adiz @arcanicanis

Yes.
I made a proof-of-concept client that controls user's identity key and generates portable activities:

https://codeberg.org/silverpill/fep-ae97-client

@tadano In 2.5.0 you can do this with your custom.css:

This customization method appears to be quite powerful, I like it. What do you think?

@arcanicanis I think in ActivityPub-land domains will play an important role even after introducing portable identities. If some gateways will start spamming they can be easily blocked

@trwnh @evan @erincandescent @julian +1 for forward chron, that way you can start displaying posts without fetching the whole thread

@julian I reported this to you because one user asked me by "why I can't discover this NodeBB thread from my instance?". I think this is going to happen quite often across the Fediverse.
Maybe in the future we will figure out how to deal with these collections, but right now this leads to a bad user experience

@trwnh @evan @erincandescent @evan

@julian Another report: when NodeBB generates an Announce(Create) activity, the ID of Announce has wrong origin. Here's an example:

ID indicates that activity has originated on my server, but this is not possible :)

@trwnh @julian Because it is not clear how client should display this collection. Searching for URL is a common UI pattern: user expects to see a post or a profile as a result (this is not unique to Mastodon).

Server can attempt to fetch the first item in a collection, but NodeBB's FEP-7888 collection doesn't identify itself as a "thread". It has "OrderedCollectionPage" type and properties that many other collections also have

@julian The URL of this topic is https://community.nodebb.org/topic/17867/pre-alpha-activitypub-related-bug-reports
When I make a request with AP Accept header, the server responds with a Collection. Technically, this is not wrong, but I think most people would expect a top-level post (Note / Article) when making such request

@hongminhee It is okay to embed this collection, for example Mastodon does that.