pere

@pere@micro.towards.vision

Pere Lev · Connect to the Power of Aliveness

Works with people, couples, teams and communities on challenges, relationships, collaboration and organizational systems. Helps people connect to their power, fulfillment, purpose and aliveness. Come as you are <3

פרא לב · חיבור לכוח החיים

מלווה אנשים, זוגות וקבוצות באתגרים, יחסים ושיתוף פעולה ארגוני וקהילתי. עוזר לאנשים להתחבר לעוצמה ולהגשמה שלהןם. בואו כמו שאתןם
<3

[ Header image: https://micro.towards.vision/@pere/111575525589808644 ]

This profile is from a federated server and may be incomplete. Browse more on the original instance.

RyunoKi, to random
@RyunoKi@layer8.space avatar

@pere As I mentioned my confusion with Vervis: can you parse those objects linked here?

https://mymath.rocks/objects/fcd7b2fa-c06f-4d1e-a0d6-771a4dd32450

CC @helge

Edit: moved to new post to not hijack a thread (realised it too late)

pere,

@RyunoKi

Note creation:
https://codeberg.org/ForgeFed/ForgeFed/src/branch/main/spec.bs#L556

I haven't touched the note creation code in a while, it's likely broken or needs updates, but here's an example of a Note:

https://vervis.peers.community/people/VvM9v/messages/ogbPr?prettyjson=true

The source/content thing is tricky, so far the idea is that the client generates and sends both content (used for viewing) and Markdown source (used for editing)

Is that helpful?

gvlx, to random Portuguese
@gvlx@masto.pt avatar

GITVOTE: Voting issues with your forge.

https://github.com/cncf/gitvote

It seems a good way to manage collaboration and priorities.

Are there similar projects for other forges?

@forgejo @forgefriends @forgefed @gitlab #SourceHut @sircmpwn

pere,

@gvlx Thanks for the link!

Prioritizing work is great, but I'm not sure voting is a good/just/balanced/effective way to do that. More info about voting systems:

https://ncase.me/ballot/

In the federated forge scene, I hope we will develop a tool based on needs, considerations, approvals and concerns, rather than blunt votes. Inspiration:

cc @forgejo @forgefriends @forgefed @gitlab

forgefed, to Blog
@forgefed@floss.social avatar

New ForgeFed #Blog post:

Stabilizing the Object Capability System

https://forgefed.org/blog/stabilizing-ocaps/

Where to comment: Right here on the Fediverse :)

--pere

#forge #ocaps #activitypub #forgefed #federation #haskell #fediverse #decentralization #development

pere,

@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?

pere, to random

Too exciting to keep just in Matrix chat:

Now that Vervis uses per-actor micro-DBs, I wonder:

  • What if actor DBs store issues in the git-issue format, inside a git repo?

  • What if actor DBs hold objects in the F3 format, so the data is trivial to migrate at any time? cc @dachary

  • What if Git can serve as an ACID per-actor DB, with a complete history log that can be used for time-travel debugging/revert/inspection of the whole actor system? cc @zenhack

cc @mray @smallcircles

pere, to random

(1/3)

I envision actors having public keys as their IDs, possibly with some system for updates/revocations. When actor references are passed, they're sent together with the current (or last known) network location of the actor. Each server keeps a directory mapping IDs to locations. Actors can transparently move between instances, by sending a Move notification about their new location. Anyone who misses the notification can query friends/others who did get it.

(cont...)

(1/3)

pere,

(2/3)

In actor-model programming, it's possible for each actor to have its own separate database, which makes it trivial to move actors by copying their data! Of course this would be done securely, encrypting the data with the actor's own key

Once we have such a system, we can play with network systems that manually/automatically move actors between servers, changing the shape of the network, without any impact on the application layer

(cont...)

(2/3)

pere,

(3/3)

For example, an algorithm that balances the network by moving actors from busy/slow/large instances to smaller ones?
And of course people manually moving for social/privacy/ToS/etc. reasons

Thoughts/concerns about this whole idea? 🙏

#activitypub #nomadicidentity #decentralizied

cc @strypey @forgefed

(3/3)

pere, to fediverse

@forgefed news:

I'm working on Vervis, the ForgeFed reference implementation written in Haskell. Refactoring the codebase into an actor model architecture, i.e. a system of objects that communicate by sending messages to each other's message queues.

Progress so far: I created a simple library that implements a local actor system, and plugged Vervis's #ActivityPub implementation into it, to add the network part. Started porting the Person actor to the new system.

Nothing to show yet :P

  • All
  • Subscribed
  • Moderated
  • Favorites
  • •
  • JUstTest
  • InstantRegret
  • mdbf
  • ethstaker
  • magazineikmin
  • cubers
  • rosin
  • thenastyranch
  • Youngstown
  • osvaldo12
  • slotface
  • khanakhh
  • kavyap
  • DreamBathrooms
  • provamag3
  • Durango
  • everett
  • tacticalgear
  • modclub
  • anitta
  • cisconetworking
  • tester
  • ngwrru68w68
  • GTA5RPClips
  • normalnudes
  • megavids
  • Leos
  • lostlight
  • All magazines
    •