Here's another #FEP for representing torrents on activitypub :)
Technical Discussion
7
Posts
3
Posters
21
Views
-
Here's another #FEP for representing torrents on activitypub :)
short, sweet, and with a reference implementation and tests!
towards a federated bittorrent tracker with #sciop !
PR: https://codeberg.org/fediverse/fep/pulls/714
Discussion: https://socialhub.activitypub.rocks/t/fep-d8c8-bittorrent-torrent-objects/8309 (or this thread)
#FEP_d8c8 #BitTorrentOverActivityPub #FederatedP2P #BitTorrent
-
Here's another #FEP for representing torrents on activitypub :)
short, sweet, and with a reference implementation and tests!
towards a federated bittorrent tracker with #sciop !
PR: https://codeberg.org/fediverse/fep/pulls/714
Discussion: https://socialhub.activitypub.rocks/t/fep-d8c8-bittorrent-torrent-objects/8309 (or this thread)
#FEP_d8c8 #BitTorrentOverActivityPub #FederatedP2P #BitTorrent
torrents are just bundles of hashes and a file layout! they (or v2 torrents at least) are actually a really nice way to do content addressing for files and directories. so when combined with the rest of activitypub, e.g. being able to do updates, sign objects, extend them with additional vocabularies, then you get something very interesting indeed....
-
undefined cwebber@social.coop shared this topic on
-
torrents are just bundles of hashes and a file layout! they (or v2 torrents at least) are actually a really nice way to do content addressing for files and directories. so when combined with the rest of activitypub, e.g. being able to do updates, sign objects, extend them with additional vocabularies, then you get something very interesting indeed....
this FEP is trying to be as minimal as possible: just get a representation of an object. but follow-up FEP wills spec out handling other parts of the protocol, e.g. BEP 0039 style updating using object integrity proofs. so tentatively butterfly memeing "is this mutable torrents"
-
Here's another #FEP for representing torrents on activitypub :)
short, sweet, and with a reference implementation and tests!
towards a federated bittorrent tracker with #sciop !
PR: https://codeberg.org/fediverse/fep/pulls/714
Discussion: https://socialhub.activitypub.rocks/t/fep-d8c8-bittorrent-torrent-objects/8309 (or this thread)
#FEP_d8c8 #BitTorrentOverActivityPub #FederatedP2P #BitTorrent
@jonny oh shi
-
this FEP is trying to be as minimal as possible: just get a representation of an object. but follow-up FEP wills spec out handling other parts of the protocol, e.g. BEP 0039 style updating using object integrity proofs. so tentatively butterfly memeing "is this mutable torrents"
what if a torrent contains self-authenticating signed activitypub objects???? what if we could jump back and forth between federation and p2p?
-
Here's another #FEP for representing torrents on activitypub :)
short, sweet, and with a reference implementation and tests!
towards a federated bittorrent tracker with #sciop !
PR: https://codeberg.org/fediverse/fep/pulls/714
Discussion: https://socialhub.activitypub.rocks/t/fep-d8c8-bittorrent-torrent-objects/8309 (or this thread)
#FEP_d8c8 #BitTorrentOverActivityPub #FederatedP2P #BitTorrent
@jonny what a great idea! 🤯
-
@jonny what a great idea! 🤯
@carloshr as always, my best ideas are the ones that seem so obvious to me that i figure someone else surely has already had them
-
undefined oblomov@sociale.network shared this topic on
System shared this topic on
Gli ultimi otto messaggi ricevuti dalla Federazione
-
-
I think the wrapping in <p> is just plain good practice because otherwise rendered content could be injected somewhere resulting in invalid HTML.
Not that browsers ever reject bad HTML anyway heh</p>
-
>Can you explain what goes on in mitra?
When mediaType is text/markdown, the entire content is wrapped in a <p> tag. This was done for compatibility with PeerTube. I think <p> was needed to create a space between the title (name) and the content, since title is prepended to content in Mitra (also a compatibility hack -- for Mastodon API clients).
-
I'd generally discourage RFC7591 in decentralized systems due to the fact that it creates client sprawl (this is currently a problem with Mastodon's client registration mechanism, which is why we created CIMDs) — every client in RFC7591 is a distinct client, with its own client_id and client_secret, which can make client management interfaces difficult to implement (e.g., every time you login on a mobile device or SPA, you'll get a brand new client_id). CIMDs solve this by anchoring client metadata to a URI, and using that URI as the client_id.
If you need to test clients using CIMDs in development, there is cimd-service however, it's currently targeting the AT Protocol ecosystem (so has a few specifics that at present there that would not necessarily make sense of ActivityPub)
-
Speaking of handling markdown. I created funfedi.dev Media Types a while ago (and just added it to the navigation). I lost interest when I saw that nobody properly handled the mediaType attribute of a note. Not that I know what I expected.
Can you explain what goes on in mitra? When mediaType is text/markdown. It changes __bold__ to <p>__bold__</p>, otherwise no paragraph tags. I'm pretty sure, I was once told to use __ for bold and * for emphasize. So my markdown should be good.
Full example ... input activity -> mitra api response
Final note: I am not sure what I would want a proper data format to do. I find the solution of W3C ActivityPub (not W3C ActivityStreams) proposes of putting HTML in content and adding source with the original, from which the HTML was generated ok. Of course, this leaves the existence of the summary and name field superfluous.
-
@reiver@mastodon.social add in NodeBB as well. Markdown first, and probably HTML too, although it will probably be sanitized to death on the way out.
-
@mariusor that's too bad. All I have left is mussels, French fries, large-scale bureaucracy, and peeing statues.
-
@reiver #WriteFreely uses Markdown by default too, but of course sends out HTML to the fediverse
