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

@Tadano @waifu Not tricky at all, I think the most time consuming task would be UI design

@Tadano @waifu Mitra supports post editing already.
Custom emotes are partially supported - I just need to add an emoji picker. Reactions are planned; no ETA yet.

Yet another FEP-ef61 update: https://codeberg.org/fediverse/fep/pulls/275/files

I added some notes on backward compatibility (DID URLs vs HTTPS URLs vs url property) and location discovery (aliases vs sameAs vs alsoKnownAs vs url).

Verification process was clarified too. In FEP-ef61 world all you need to do is verify the signature. Fragile same-origin checks are no longer necessary.

@Tadano @waifu We're getting there. Any particular feature or features you'd like to see implemented?

I don't know yet who could be the mascot, probably it shouldn't be literally Mitra... Anyway, it would be great to have one.

@Hyolobrika @waifu No I haven't. Ty

The solution I'm working on simply rejects mentions from unknown users.

@waifu Thanks. I'm testing a new anti-spam feature, hopefully they will notice me.

@82eiigquyo Hey you.

@waifu I could use some of this spam, where do you get it?

@harblinger I have the same problem sometimes, it is intermittent. I always thought that it is just me and that it has something to do with Tor and my browser configuration.

cc @nimda

@harblinger Are you using Tor Browser?

@harblinger Known Network should already work in alternative clients (e.g. Husky). And in the next release it will be added to mitra-web as well.

By the way, what happened to SPC?

@japananon I'm going to add a setting that disables notifications from unknown accounts in the next release.
Ultimately all of this boils down to ability to reach / ability to spam tradeoff. The problem can't be solved completely, but Mitra will have fine-grained permission system that will allow its users to find a comfortable middle ground.

#Mitra v2.10.0

https://codeberg.org/silverpill/mitra/releases/tag/v2.10.0
https://codeberg.org/silverpill/mitra-web/releases/tag/v2.10.0

Descriptions (alt text) can be added to uploaded images.
This release also includes a security patch.

New Lemmy RFC: Private Communities

https://github.com/LemmyNet/rfcs/pull/5/files

@pomstan Yes. But I had to change my DNS server to reply to you. Previously deliveries were failing with this error message:

>error trying to connect: dns error: failed to lookup address information: Name does not resolve

@arcanicanis @lanodan @Johann150

>Essentially with FEPs, it feels almost like something that should be treated like trying to get a bill through Congress. “Hey, I’ve got this new proposal, I’ve talked to X and Y project, and they seem onboard, can I count on your support too? Is there any feedback you have on this idea?”

I think this is a correct approach. Not sure about other authors, but for me each proposal is a mini-project, not something that you can write and forget about. Requires a lot of work, but this is exactly how standards in decentralized network should be developed.

@grunfink @gyptazy @tetra quoteUrl is a non-standard property, but widely supported. The proposed standard is FEP-e232, though not everyone is happy with it and mastodon developers are working on an alternate proposal:

https://oisaur.com/users/renchap/statuses/111925462223450502

@iwojima It doesn't support groups yet, I think this bot is a good solution. You can also use install a separate service like Guppe groups or even Lemmy, and send posts from Mitra by mentioning the group account.

@arcanicanis @phpfox

>meanwhile just referencing the activity ID of the Follow alone would be insufficient

In theory this should be sufficient. I do that, works with most software.

@mauve @mauve I think url is better. alsoKnownAs is used for account migrations and has a slightly different meaning in Fediverse (different objects controlled by the same entity).

Perhaps FEP-fffd is suitable for your use case?

Or FEP-ef61 which I'm currently working on.