Pere פרא

@kalle,

• ForgeFed continues to be based on ActivityPub,

• The hypothetic ForgeFed-v2 will be based on actor programming,

• But on top of actor programming we can have an ActivityPub compatibility layer! And therefore still be compatible :)

• We will use the donations, waiting for the right moment to use them <3

@boud ForgeFed's funding source has been NLNet indeed! I've documented the grant application and the whole the email exchange until the recent approval: https://socialhub.activitypub.rocks/t/forgefed-nlnet-grant-application/2598 (huge thanks to @dachary for advocating radical transparency)

@genofire @forgefed @RyunoKi @team https://news.ycombinator.com/item?id=39201453

@trwnh I'm trying to keep it in line with ActivityPub and the current Fediverse. I do intend to use something RPC-like, in a different project and a different name. Does that answer your question? / Do you have a proposal?

@aka_dude @forgefed The transaction stuff is inspired by Spritely Goblins, check out their docs: https://spritely.institute/files/docs/guile-goblins/0.11.0/Transactions-make-errors-survivable.html In my case it means using DB to persist all actor state, including message queues. I've though of wrapping it in STM, Idk yet if it's necessary, will see :) I assume you mean run the LMDB transaction in a separate thread that sets a TVar/TMVar after the transaction, and/or get the input data via a TVar, and other threads can then use LMBD via STM?

@rtn 👍 I opened an issue about it to keep track, and hoping that someone (maybe me eventually) will make a PR