Cory J Slep
Cory J Slep
That layout *might* be possible in go. Cyclical dependencies are not allowed, which is why golang usually has all data types in the same package so that they can reference...
Sorry that I've been busy. I see that #4 has been merged. I also see I've needed to catch up here. :) I'll try to consolidate everything into this post......
Thanks! Also, it's OK to file the website issues here. But the site's repository is also available (and monitored) at: https://github.com/go-fed/site
> **Please Describe The Expected Behavior** > > When there is only one item in the ordered items it still renders as an array. Ah, man. So the root issue...
Thanks Rob for reaching out! Summarizing our video call, for you & posterity to see: * Best place to start is ActivityStreams manipulation: `go-fed/activity/streams`, for example passing an ActivityStream JSON...
Update: `v1.0.0` has now been released. :) If you would like advice with integrating into gitea, let me know.
I'm going to leave this open, but I want to note that I am hesitant to add the `sharedInbox` optimization at this time.
Sure, it's simple: `sharedInbox` is the only* ActivityPub feature that breaks the Actor model. When you look at any `Activity`, its addressing (`to`, `bto`, `cc`, `bcc`, `audience`) does not align...
You're correct, the `GetInbox` and `GetOutbox` on the database is for its own `SetInbox` and `SetOutbox`. `go-fed` will prepend any IRIs to any existing `orderedItems` property. If you return an...
Thanks for identifying this issue. I'll take a look at fixing this soon.