Conversation

Notices

1. Embed this notice
   洪 民憙 (Hong Minhee) (hongminhee@todon.eu)'s status on Sunday, 24-Mar-2024 22:59:28 JST 洪 民憙 (Hong Minhee)

   #Fedify finally has a step-by-step tutorial! It's perfectly fine if you're not familiar with the #ActivityPub protocol or the #Deno runtime. Here's the link for beta readers:

   https://unstable.fedify.dev/tutorial/

   • Embed this notice
     洪 民憙 (Hong Minhee) (hongminhee@todon.eu)'s status on Monday, 25-Mar-2024 00:59:39 JST 洪 民憙 (Hong Minhee)

     in reply to

     • marius

     @mariusor Unfortunately, that's the official installation method that the Deno documentation says. 😥

   • Embed this notice
     marius (mariusor@metalhead.club)'s status on Monday, 25-Mar-2024 00:59:40 JST marius

     in reply to

     > curl -fsSL https://deno.land/install.sh | sh

     @hongminhee no please, no. :(

   • Embed this notice
     洪 民憙 (Hong Minhee) (hongminhee@todon.eu)'s status on Monday, 25-Mar-2024 10:21:22 JST 洪 民憙 (Hong Minhee)

     in reply to

     • Erlend Sogge Heggen
     • Aumetra Ⓐ :nonbinary: :good_boy:​

     @0x0 @erlend Although Fedify already implements HTTP Signatures, relying on Kitsune's implementation for performance might be an option. However, I'm not sure how much of a performance gain it would be, since Fedify already relies on Deno's Web Cryptography API, which is implemented in Rust. 🤔

   • Embed this notice
     Aumetra Ⓐ :nonbinary: :good_boy:​ (0x0@corteximplant.com)'s status on Monday, 25-Mar-2024 10:21:23 JST Aumetra Ⓐ :nonbinary: :good_boy:​

     in reply to

     • Erlend Sogge Heggen

     @erlend @hongminhee well, its something we can figure out if there is interest in collaborating on that.
     then we can figure out the logistics of packaging these things in something that can be distributed well

   • Embed this notice
     Aumetra Ⓐ :nonbinary: :good_boy:​ (0x0@corteximplant.com)'s status on Monday, 25-Mar-2024 10:21:24 JST Aumetra Ⓐ :nonbinary: :good_boy:​

     in reply to

     • Erlend Sogge Heggen

     @erlend @hongminhee depends on the module. when disabling the easy module, it could totally compile to wasm i think. the easy module depends on rayon to asyncify the cryptography which doesn't play well with wasm (because it spawns threads)

   • Embed this notice
     Erlend Sogge Heggen (erlend@writing.exchange)'s status on Monday, 25-Mar-2024 10:21:25 JST Erlend Sogge Heggen

     in reply to

     • Aumetra Ⓐ :nonbinary: :good_boy:​

     @0x0 @hongminhee alternatively, could Kitsune modules possibly be compiled as wasm packages for fedify to import without special bindings?

   • Embed this notice
     Aumetra Ⓐ :nonbinary: :good_boy:​ (0x0@corteximplant.com)'s status on Monday, 25-Mar-2024 10:21:26 JST Aumetra Ⓐ :nonbinary: :good_boy:​

     in reply to

     • Erlend Sogge Heggen

     @erlend @hongminhee If there is interest, we can totally chat about it. I think there are some nice bridges like napi that offer a nice binding between NodeJS <-> Rust, but I'm not sure about Deno (or if having a Node.js plugin would be good enough?)

   • Embed this notice
     Erlend Sogge Heggen (erlend@writing.exchange)'s status on Monday, 25-Mar-2024 10:21:28 JST Erlend Sogge Heggen

     in reply to

     • Aumetra Ⓐ :nonbinary: :good_boy:​

     @hongminhee I wonder if fedify could rely on Kitsune-lib by @0x0 for some of its low level fundamentals, e.g. http signatures: https://github.com/kitsune-soc/kitsune/tree/main/lib/http-signatures