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

@mischievoustomato

Looks like a problem with the network, either on your side or at comp.lain.la. I'd try to contact the instance admin

@mischievoustomato I don't know what could cause that, but it is probably not related to mitra, because on my servers fetch-actor works as expected, and if I remember correctly you're using the deb package, so the binary is exactly the same.

@mischievoustomato In ActivityPub users are called "actors" and have unique IDs that are URLs (like the one I posted). Addresses like Nimbius666@comp.lain.la are secondary identifiers.

Yes, fetch-actor works with actor IDs. You can also paste actor ID (URL) into the search box of your client

@steve Pleroma?

If you mean relay-only implementations then top 3 are

aoderelay 89
pleroma/activityrelay 48
yukimochi/activity-relay 42

@mischievoustomato It is reachable from my server. Try searching for actor ID instead of webfinger address: https://comp.lain.la/users/Nimbius666

@mischievoustomato Some deliveries are taking too much time. You can try to set a lower timeout in your config file:

(default is 30 seconds)

This is a workaround, of course. Hopefully I'll find some time to work on a proper solution soon.

@lsn To be honest I think Internet Archive is overrated. It's a useful service, but the real internet archive is torrent network. All content that is valuable to humanity ends up there

@mischievoustomato What the log shows? Are there items in outgoing queue as well?

'ap' URLs are not valid URIs according to RFC-3986. FEP-ef61 describes a possible solution: percent-encode a DID (the authority component of an 'ap' URL)

Today I found another solution. RFC-3986 allows future, as-yet-undefined IP literal address formats if they are enclosed in square brackets and prefixed with a version flag.

For example, this is a valid URI:

#fep_ef61

@manyfold I don't have time for that rn, maybe some other day if any of those issues remain

@mkljczk Not planning, and I agree that it doesn't make any sense.

Something like pleroma.metadata.features would be preferable

@manyfold Thanks, I'll be testing against it.

Follow-Accept: OK.
Comments: OK, but there's an issue with hashtags. The property name should be tag, not tags
Models: 500 Internal Server Error (example: https://manyfold.floppy.org.uk/models/LfzPs8c5)

I also tried to use outbox collection. It appears to be self-referential structure because current and first pages have same IDs as outbox:

@frogzone @icedquinn @nimda @sun @jeffcliff

>This ipfs system needs to have provisions to exclusively connect over i2p or tor

Does ipfs support tor/i2p connections now?

@manyfold Are there any creators to follow? I'd like to test federation.

@hollo

Emoji names have extra colons

@jupiter_rowland @mikedev @underlap

>Other than all this, a non-public development version of @silverpill's Mitra has nomadic identity via ActivityPub in development. I'm not sure whether FEP-ef61 is implemented in the release version yet.

At the moment Mitra can interact with nomadic actors on other servers, but can't host them locally.
I'm currently working on a security framework that covers both vanilla AP and nomadic AP, and trying to fix interop between mitra and streams (tracking issue: https://codeberg.org/streams/streams/issues/178).

Mitra will be able to host nomadic actors as streams does, that will probably come in mid-2025.

cc @helge

@smallcircles

I agree that SocialHub would be a better place for Fediverse Ideas, but I didn't start that repo...
@helge what do you think about @strypey 's suggestion ?

@snarfed.org ActivityPub is push + pull. Every AP server also works as a client, for example when it discovers activity.actor or object.inReplyTo. Pulling collections is less common, but even Mastodon does that occasionally

@julian @trwnh @thisismissem Server operators can read all private messages. Strict ID check is not completely useless, because it might prevent leaks in case of a software bug, but it doesn't provide any additional security guarantees

@julian @crepels @jdp23 @jdp23 It is not special, but it has same origin as person-actor. If you accept origin-based security model, there is little practical difference