silverpill

@fox I was told that your image doesn't work, something related to the configuration path. So we made another one: https://codeberg.org/silverpill/-/packages/container/mitra/5.7.1

But your image is still listed in the readme - it's good to have a backup.

[Decentralized, federated platform for dog owners]

I haven’t been able to get this idea out of my head for a while now. 😩😁

Why are there centralized platforms for dog owners—but no open, decentralized alternative? 🤔

What if clubs, animal shelters, dog training schools, or local communities could run their own instances while still being interconnected, based on ActivityPub, similar to the Fediverse? 😃

Possible features could include:
🐶 Dog profiles
🚶 Walks & meetups
📍 Dog parks & local spots
⚠️ Poisoned bait and hazard alerts
🔎 Missing & found dogs

The focus would be on data sovereignty, local communities, and open standards instead of a centralized platform. 😉

Attached is a preliminary concept diagram to make the idea more tangible.

I’d be interested to know:
Would you use something like this, or even help build it? ⁉️ 🙄

#Fediverse #ActivityPub #OpenSource #SelfHosting #Dogs #DogLovers #AnimalWelfare #Community #Idea

@PrPl Mitra doesn't require email, by design. But most instances are invite-only.

@silverpill No stance - i.e. All good.

Crypto is a technology in the first place and nothing that should be banned or moderated on the code level. Many people use it in a very positive way.

Abuse and bad acting is always possible and might surely happen in this sector more frequently than elsewhere - but that is actor-related and nothing of our business hosting source code.

If someone would use crypto projects on our CI to act questionable or perform harmful actions - this would be another case then.

@codefloe What is your stance on "cryptocurrency related projects"?

@greyarea I assume this is "Authentication Using an Asymmetric Key" (https://www.rfc-editor.org/rfc/rfc9180.html#name-authentication-using-an-asy)?

Because in "Encryption to a Public Key" mode, sender's key is not used.

If I understand the idea correctly, the ephemeral key would need to be added to fep0806:cipherData. That is, instead of encap_key | ciphertext it will be ephemeral_key_pub | encap_key | ciphertext.

@greyarea

having the sender generate an ephemeral keypair (include the public key envelope)

So the recipient will need to encrypt to this ephemeral key when replying?

@doesnm As far as I know, these are just an implementation quirk.

But repeated parameters are allowed by URL (WHATWHG) standard: https://url.spec.whatwg.org/#urlencoded-parsing

@mariusor FEP-ef61 currently requires that the value of gateways is a comma separated list.

Proposal: Replace gateways query parameter in 'ap' URIs with @gateway, which can be used multiple times

https://codeberg.org/fediverse/fep/pulls/890

Before:

?gateways=https%3A%2F%2Fserver1.example,https%3A%2F%2Fserver2.example

After:

?@gateway=https%3A%2F%2Fserver1.example&@gateway=https%3A%2F%2Fserver2.example

Query parameters are often used to specify collection filters. The @ prefix will make it clear that gateway parameter is special.

#fep_ef61

@caohuak What's worse, Monero is not just a cryptocurrency. It's cryptocurrency for criminals!

@lutindiscret @happyborg I don't feel that mitra is unwelcome there, my interactions with Codeberg team have been mostly pleasant. But I also don't want to count on favorable interpretations.

I didn't ask, but somebody else mentioned mitra in a discussion 7 months ago, and was ignored: https://codeberg.org/Codeberg/Community/issues/2184#issuecomment-8629041

@happyborg No, I think only members of Codeberg organization can vote. I didn't even know this is being considered

@jody_racer No, servers are completely independent.

Migration to another forge may affect discoverability of the project, but in general I don't rely too much on Codeberg. By the way, Mitra now has federated groups, which can be used instead of an issue tracker: @mitra_support

We also explicitly do not tolerate:
...
Content that harms the reputation of Codeberg, such as cryptocurrency related projects.

That's particularly funny. Nothing harms your reputation as much as policies inspired by stupid ragebait like web3isgoinggreat.com

Codeberg is banning "cryptocurrency projects":

https://codeberg.org/Codeberg/org/pulls/1254#issuecomment-19820413

I don't know if Mitra qualifies as such, but I guess it is time to move to a self-hosted forge.

@greyarea

>If the proof covers all of that then it's not strictly needed, but it's cheap paranoia.

Do you mean id/actor/to of a plaintext activity, or of an envelope (EncryptedActivity)?

My understanding is that the properties of an envelope have no effect on security. It can even have a different actor.

I added an example of a plaintext activity: https://codeberg.org/silverpill/feps/src/branch/main/0806/fep-0806.md#plaintext-activity

Also added HPKE mode to the parameter list - mode_base.

@greyarea I added HPKE algorithm parameters to the FEP:

https://codeberg.org/silverpill/feps/src/branch/main/0806/fep-0806.md#algorithms

KEM: DHKEM(X25519, HKDF-SHA256)
AEAD: ChaCha20Poly1305
KDF: HKDF-SHA256
"info" string: fep-0806-info
"aad" string: fep-0806-aad

Does it look right?

KEM/AEAD/KDF choices are not my preferences, I just copied them from another HPKE+ed25519 implementation.

@greyarea @raucao @lain @sozialwelten @koteisaev Is there anything built on top of Noise for group messaging?

As far as I can tell, HPKE is used in MLS

@greyarea Hi, I tried to implement the mechanism described in the FEP and decided to use HPKE (RFC-9180). What do you think of it?

HPKE seems to address the issue you pointed out back then: https://www.rfc-editor.org/rfc/rfc9180.html#name-forward-secrecy.

At least if used properly. The library I am using hard-codes "info" and "aad" strings: https://github.com/rustonbsd/ed25519-dalek-hpke/blob/27b010a9ae25ba4ce051510eadfd103a179dd715/src/lib.rs#L98-L104

Anyway, here's an updated FEP: https://codeberg.org/silverpill/feps/src/branch/main/0806/fep-0806.md

@raucao @lain @sozialwelten @koteisaev