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

@tesaguri FEP-ef61 is designed to support generative DID methods such as did:key. But if non-generative method is used, such as did:web, implementers can use services to enable DID -> ActivityPub discovery

@mkljczk I'll add that. Thank you!

@mkljczk You mean for post content? How Pleroma provides that list of supported types?

@mischievoustomato I don't know, maybe it is caused by http server configuration

I just logged in to phanpy.social, it can connect to my instance without issues. Config:

@mkljczk

When I try to log in at pl.mkljczk.pl it redirects me to Mitra authorization page, but client_id and redirect_uri are undefined:

@mischievoustomato

When web client is located on a different domain, you need to allow cross-origin requests in your config:

https://codeberg.org/silverpill/mitra/src/tag/v3.6.0/config.example.yaml#L20-L21

I don't know why Tokodon is not working. The redirect_uri parameter in your address bar starts with 'tokodon', I guess the browser is supposed to open it in Tokodon app? That would be hard to figure out without a help from client developer

@mischievoustomato What kind of spam? For some reason all those spam waves are not reaching my instance.

If they use mentions, I recommend changing "Accept mentions from" setting in your profile to "People I follow and my followers" (you can change it back when the spam wave is over)

@mkljczk

Yeah, Mangane fork is barely active and apparently their primary goal is to annoy Alex

>I tried to improve compatibility with Mitra in my fork of Soapbox (it needs a better name) but didn’t really test it

Awesome! I'll give it a try.

@lsn

@julian @trwnh @thisismissem

>How that is represented via ActivityPub is probably detailed in some FEP

FEP-e232? I think you can add content or summary property to FEP-e232 link to represent HTML content of a quote

@mischievoustomato Does this message come from Mitra or Tokodon?
It would help if you send me a screenshot

@5dh @fediverse Financial incentive is not the only possible cause. If project leaders stop listening to their users for some other reason, you'll get the same result.
And there is another, more subtle problem: protocol bloat. Fediverse services are getting more and more complicated, and the cost of creating a new platform is constantly increasing. If this problem is not addressed, at some point Fediverse will start looking like a web browser market, where new players can't compete due to an immense implementation complexity.

@elvecio We're still having interop issues. I fixed one problem on my side, but adjustments need to be made on the streams side as well

@elvecio Send a message to me, I'll figure out what's wrong

@ax3 @japananon If they do something stupid with the protocol (almost a certainty), we can fork off. That would destroy a lot of value, but might be necessary

@elvecio No, I don't see it

@evan @darius @julian Merged: https://codeberg.org/fediverse/fep/src/branch/main/fep/76ea/fep-76ea.md

@elvecio Good, I can see your request as well. Now we need to wait until 'release' branch is updated

@elvecio My server didn't process the message, but this is is known issue which should be fixed in 'dev'

I sent a follow request to your channel. Could you accept it?

@elvecio Let's do it with release version then. What is your nomadic ID?

@elvecio Some of these issues has been fixed in streams dev branch: https://codeberg.org/streams/streams/issues/178#issuecomment-2350039
And wizard.casa now runs Mitra v3.6.0, which also includes compatibility fixes.

If you have an up-do-date streams instance with a nomadic account, let's do some interop testing.