Proof generation and verification algorithms in eddsa-jcs-2022 cryptosuite are changing:
https://socialhub.activitypub.rocks/t/fep-8b32-object-integrity-proofs/2725/73
Proof generation and verification algorithms in eddsa-jcs-2022 cryptosuite are changing:
https://socialhub.activitypub.rocks/t/fep-8b32-object-integrity-proofs/2725/73
@angus @wordpress Another test
@gunnm @monero The address from profile field can be displayed near each comment. This is how tipping button works on my site.
But if you want to count tips, and do it for each comment separately, that's much more complicated. I don't know if plugin system will be powerful enough for this.
>There is no social media using tipping as piconeros
There is, I'm using it right now. Try to click on the "fediverse" icon near my comment, and on my site you'll see a donation button.
>looking for opinions and discussion of this could be done in Monero.town
The easiest way is to convince Lemmy devs to implement profile fields: https://github.com/LemmyNet/lemmy-ui/issues/2411
After that you can add a machine readable XMR address to your profile
@manlycoffee did:plc is just a single server that stores account data
In ActivityPub world we can have real nomadic identities, controlled not by a startup that may disappear tomorrow, but by people themselves
https://codeberg.org/fediverse/fep/src/branch/main/fep/ef61/fep-ef61.md
@tokyo_0 You can create an additional collection similar to followers and put it into the to field. This feature sometimes called "circles" or "lists". It is implemented in Streams, maybe in Hubzilla too.
@arcanicanis @nimda @harblinger Dino displays OMEMO error only when it is enabled. Otherwise there was a "delivery failed" message.
But now everything is working. Thanks!
@Tadano I'm afraid this feature will require a bit more time. There are several ways to do that and I'm not sure which one is better.
@julian Activities like Announce(Create(Note)) are the main point of FEP-1b12:
>In case the incoming activity is deemed valid, the group MUST wrap it in an Announce activity, with the original activity as object.
Announce(Note) is an additional activity that Lemmy sends to remain compatible with micro-blogging apps.
@giacelvecio Mitra doesn't forward replies to other conversation participants (yet)
@julian Makes sense. Accept if origin is the same, otherwise retrieve from source. I think Announce(Create(Note)) and other FEP-1b12 activities should be processed in the same way:
https://socialhub.activitypub.rocks/t/fep-1b12-group-federation/2724/68
@julian ^ How it works in NodeBB? Do you authenticate wrapped activities?
@fabio @dansup @jwildeboer @Chocobozzz @thelinuxEXP @Techaltar
No, the $XMR field in profile is just a static address. The link to subscription page is just below that. This special page is only needed for compatibility with other software, and with FEP-0837 users don't need to leave their instance (that's the intent behind this FEP).
I should note that FEP-0837 does not require people to use digital currencies, it is designed to be currency agnostic, and even supports gift economy. The relevant part of the proposal is "Accepting an agreement" step:
>The finalized agreement MAY have url property containing one or more links to resources associated with the agreement. An example of such resource is a payment page (which can be represented as FEP-0ea0 link).
In other words, payment actually happens outside of protocol, and the recipient server sends a confirmation only when the payment is complete.
Transaction states were outside of scope of this FEP, but we can add them if necessary (it is still a draft).
@thelinuxEXP @dansup @jwildeboer @Chocobozzz @fabio @Techaltar
A mechanism for federated payments was proposed in FEP-0837: https://codeberg.org/fediverse/fep/src/branch/main/fep/0837/fep-0837.md
It should work with any currency and in any kind of application. I'm already using it to facilitate subscription payments in my own project.
@serapath @jwildeboer FEP process doesn't prevent people from extending the protocol, in fact it has the opposite goal. But it protects Fediverse by decentralizing standards development. It doesn't dictate what is a standard and what is not, instead developers decide for themselves which FEPs they want to implement, and eventually some FEPs may become de-facto standards
>delivery failed
>This contact doesn't support OMEMO encryption
@nimda pls help. I'm trying to establish a connection from were.social XMPP server
cc @arcanicanis
@waifu If I make a 88x31, would you add it?
@tallship Yes, it is a feature from GitHub Flavored Markdown
~~text~~ renders as <del>text</del>
@mario says Hubzilla will support this tag: https://hub.somaton.com/item/5d22eb3e-79eb-4e4e-9831-5aa269d70c4a
But people are also reporting that Fedilab doesn't display it correctly so I'm hesitant to enable this feature. The perceived meaning of the message can be very different without this piece of markup.
@harblinger @dino Dino enjoyer here. The only desktop client that just works and doesn't pull 1000 dependencies. I wouldn't call it fancy though
@realcaseyrollins Disappointing. Didn't expect that from a client.
Some servers might remove the <del> HTML tag, but even Mastodon doesn't do that since version 4.2
Developer of ActivityPub-based micro-blogging and content subscription platform Mitra. Working on Fediverse standards: https://codeberg.org/silverpill/feps
076萌SNS is a social network, courtesy of 076. It runs on GNU social, version 2.0.2-beta0, available under the GNU Affero General Public License.
All 076萌SNS content and data are available under the Creative Commons Attribution 3.0 license.