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

@giacelvecio I'm also experiencing some issues with the new Hubzilla, for example my likes are rejected (http status 409 is returned). I think this might be related to FEP-8b32 implementation in Hubzilla 9.0

cc @mario

@tallship

@waifu Try to convince him to come back to fedi

@frogzone @nimda You need to select "Markdown" format when you write your post. The default format can be changed in Bloat config.

@pseudocute

@tallship I don't know if Hubzilla implements FEP-e232 (it's a different code repository :)

@tallship The Streams community uses parentheses to indicate that Streams is just a name of code repository, not a "brand".

@julian Have you seen the implementation of private groups in Streams? It is based on the Conversation Containers https://fediversity.site/help/develop/en/Containers
I'll probably use this model in my project.

(There's is comment about it from @mikedev but for some reason it didn't arrive to your server)

It's official now: Threads implemented FEP-e232

https://engineering.fb.com/2024/03/21/networking-traffic/threads-has-entered-the-fediverse/

Article contains a couple of minor inaccuracies: _misskey_quote doesn't build on FEP-e232, and the other property name is quoteUrl, not quoteURL. But overall it's good and I hope other implementers will notice it.

#FEP

@luceos I think the most important part of this proposal is "Requirements" section that says:

>Fediverse software SHOULD implement NodeInfo [NodeInfoRepository].

The reference leads to NodeInfo repository.

It is badly formatted, but otherwise seems to be correct.

My server can now process preferredUsername changes. I also changed everything to use actor ID as a primary identifier. Previously, actor ID was a secondary identifier after the webfinger address - this is a pretty big change and I hope I didn't break anything. Webfinger is now optional (but preferredUsername is still required).

In UI accounts without webfinger address will have actor ID in its place.

https://codeberg.org/fediverse/fep/src/branch/main/fep/03c1/fep-03c1.md

@bot @waifu You can visit my public profile: https://mitra.social/@silverpill. From the inside it looks very similar, just with a sidebar on the right.

@liaizon Ignoring the corpos-vs-people question for a moment, I actually like the symbol. Reminds me of Ubuntu logo

@bot @ElDeadKennedy @waifu No need for Monero logo, but I think she may meet Monero-chan at some point

@bot @waifu It used to be about crypto but not anymore. Today it is just a regular social media server which has some crypto features like subscriptions and wallet login, but they are optional (disabled by default).

@frogzone @nimda @pseudocute Mitra implements Mastodon API (with some differences), so it should work with many Mastodon and Pleroma clients.

Default web client requires JavaScript, but there are alternative no-JS clients, for example Bloat, which was tested and known to work with Mitra (it needs to be installed by the server admin though).

@Hyolobrika Possibly, but if by elements you mean HTML elements, you can already do this with custom elements, data-attributes and a bit of JavaScript.

@Hyolobrika Was there, but moved to Farcaster

@mikedev @hollie

>I've got some background docs if you're interested.

I'd like to read them too.

@greyarea @Revertron I didn't know about transparency logs. Yes, sounds exactly like that

https://certificate.transparency.dev/howctworks/

>A certificate ties together a domain and a public key.

And in our identity system certificate would tie a name in namespace and a public key.

@julian I'm interested. Perhaps there should be a Group actor for announcements that people can follow? It could be a Lemmy community, or Friendica group, even a Discourse category on SocialHub (sorry, I don't know if nodeBB has an equivalent).

@Revertron A single person, or a group, or a company. Let's assume for a moment that IPNS performance has improved and it supports FROST or something like that.

The IPNS name is a namespace root. It is a pointer to some verifiable data structure, probably an append-only log, where all identity operations are recorded: add key, update key, revoke key. If the root key of namespace is distributed, no one can single-handedly add or remove an identity. Operations are performed only by a consensus or a majority vote.

Such system would have all desired properties: redundancy on all levels, organizational diversity (no logical centralization), no payments required, key rotation is possible, user friendly.