Aspiring fantasy author and geek, retired due to a bunch of chronic illnesses. The Last Philosopher is my first book under the subtitle, Nothing is Everything. It's been called imaginative, funny, and unique. People have even gone so far as to compare it to #DouglasAdams and #TerryPratchett. My response to that comparison, is to go hide under the covers for a week with embarrassment. Posts about books, nature, and geekstuff. #Writing #Author #Indie #Fantasy #Comedy #Satire #NoAI #fedi22
Developer of ActivityPub-based micro-blogging and content subscription platform Mitra. I help maintain the FEP repository and write my own FEPs too. Currently working on ActivityPub Next.
My understanding from a reading of the relevant section from fe34 suggests a claim of A → B is reciprocal if there is an inverse claim B → A.
Yes, and in my understanding these claims are:
- This actor is authorized to delete/update this object.
- This object is hosted on the server where this actor is an administrator.
But I don’t insist on importing this concept.
I would want to point out that keeping with prior art has the benefit of making this FEP much easier to adopt by threadiverse implementors.
I consider myself a threadiverse implementer too, and I don’t really like the idea of dealing with ambiguous properties :)
At the very least, could you add inbox and outbox properties to the Application actor example? https://codeberg.org/devnull/feps/src/branch/instance-admins/fep/baf5/fep-baf5.md#instance-actor-and-application-actor
Nothing personnal. My name meaning "Can make you loose teeth". Post are mine , like/boosts doesn't mean endorse. If you feel offended that's because I wrote with you specifically in mind.
Nothing personnal. My name meaning "Can make you loose teeth". Post are mine , like/boosts doesn't mean endorse. If you feel offended that's because I wrote with you specifically in mind.
You've seen all posts