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

@feralthoughts This problem has an easy solution. Mentions don't have to be inserted into posts, they can simply be copied from the parent post.

Some platforms always used implicit addressing. I plan to do this too in the future (Mitra already uses implicit addressing in some cases, e.g. in group conversations).

@jupiter_rowland

@fox Check monero-wallet-rpc logs, if it can't connect to daemon, errors will be logged.

@mkljczk @caohuak It's not by design, I just haven't implemented it yet.

Checking signature on every GET request is expensive so I need to do some optimizations first.

@nimda @dsdarkkogo

Yes, with media proxy everything is hotlinked, not downloaded / cached.

https://codeberg.org/silverpill/mitra/src/branch/main/docs/cache_management.md#media-proxy

@phnt I think I understand now. Yes, it can be done, but I wouldn't change an actor of Update. Better add a new property to it, e.g. updatedByMod: true.

@feralthoughts Yes, conversation containers can be used to enforce conversation scope.

Say user B replies followers-only to the OP. User C then replies followers-only to B’s post. In this case, B’s post will only be visible to B’s followers, while C’s post will only be visible to C’s followers, with further downstream replies inheriting the problem.

This is not a narrowing, it's a change of scope. Narrowing means user C can only reply to B's followers or to B directly.

@feralthoughts Server admin must enable the experimental API first.
All operations with a nomadic account require command-line client, regular interface can't be used. Cloning happens in background.

@nimda @dsdarkkogo Have you tried media proxy? Images load slower and sometimes break but you can afford to keep posts for longer

@phnt Inaccessible in what sense? It is not possible to change the original version of an object if it was created on another server. But you can announce your local moderation actions to other admins.

@feralthoughts Yes, mirroring partially works, but nomadic accounts require a special command-line client:

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

It's not possible to create a nomadic account from the web site.

@feralthoughts

Hashtags: only if they are ActivityPub actors, e.g. https://relay.fedi.buzz/ hashtags
Groups: yes
Relays: yes, and regular users can subscribe too. Actually, there is no special admin interface for subscribing to relays, we just use regular accounts.

@fox Might be a temporary problem (monero-wallet-rpc is busy), or a problem with monero daemon (which is probably not used for signature verification).

@feralthoughts

How does Mitra work in case of public conversations?

Similar to how Mastodon and other micro-blogging platforms work. You're notified only when you're directly addressed (this is usually done by @mention).
It doesn't currently use Conversation Containers for public conversations, but I think the way notifications work will be the same when we switch to containers

Can a respondent to the OP’s public post change the status of their reply post to followers-only or mentioned-users-only?

They can reply with narrower visibility. I think narrowing of the scope should be allowed, but not widening. Although, as far as I know, Streams/Forte allow neither.

If the OP is not a follower of that respondent, and is not tagged, will the reply be visible to the OP?

Currently it is not visible.

@feralthoughts No, this is not supported.

@caohuak @remnant How many CPU cores do you have there?

Some things, like the number of server workers and the size of database connection pool, are proportional to the number of cores. So increasing the number of cores likely leads to more memory usage.

My machine has 1.

@fox There were many replies. Are you looking for this one? https://mitra.social/objects/0199fe58-8aca-872c-b463-175874a76905

I think context property should point to a collection (a dynamic view), but we can introduce a new Delete-able object that is linked to that collection. It could be an actor: https://codeberg.org/fediverse/fep/src/branch/main/fep/f06f/fep-f06f.md

You also mentioned Remove, how it should look in practice? Remove from what target?

@helge ActivityPub requires application/ld+json; profile="https://www.w3.org/ns/activitystreams"

https://www.w3.org/TR/activitypub/#retrieving-objects

The shorter form application/activity+json is nicer, but media type is one of the things about which specification is not ambiguous, so I always use the required one.

application/activity+json is (or was) used by Mastodon, so of course everyone copy-pasted it into their projects.

@fox This is normal if your monero-wallet-rpc is not listening at 10.81.0.4:9015 or if that host is not accessible from mitra machine

fep-ae97-client now verifies activities retrieved from gateways:

- outbox: activities must be portable, actor must match outbox owner.
- inbox: portable activities are verified, non-portable are trusted (client can try to fetch them from origin, but IDs are often not resolvable, so I decided to not do that).

RE: https://mitra.social/.well-known/apgateway/did🔑z6MknVmyPtQmD2SaGnqyGgTVEqfqkkJJnY3YVKBmbzSUNCcX/objects/0199fe39-51c0-192f-f209-0fe3b8fac301