@helge that’s a dev environment, if the site is set up as a “live” one the stack gets removed, you only get the top error displayed.
PS. Everything is a very large mess right now when it comes to brutalinks because alternative development done to the underlying ActivityPub stack (the federated.id server) have messed the assumptions that it used to work with.
@helge also the replies fails to resolve due to the changes I made to the underlying storage that I complained about a couple of days ago. Apparently the migration script that was supposed to create the missing collections didn’t work properly. :D
So by messing around on brutalinks.tech. I failed at replying and when I tried to fetch the replies collection via
http https://federated.id/objects/d42e2802-e99f-4390-8701-14c968dce179/replies accept:application/jsonI get a fantastic go stack trace encoded in json-ld. It makes me happy and I thought I share.
@helge that’s a dev environment, if the site is set up as a “live” one the stack gets removed, you only get the top error displayed.
PS. Everything is a very large mess right now when it comes to brutalinks because alternative development done to the underlying ActivityPub stack (the federated.id server) have messed the assumptions that it used to work with.
@ajsadauskas@aus.social @ajsadauskas@lemmy.ml @tchambers @atomicpoet @LemmyDev
@helge also the replies fails to resolve due to the changes I made to the underlying storage that I complained about a couple of days ago. Apparently the migration script that was supposed to create the missing collections didn’t work properly. :D
@ajsadauskas@aus.social @ajsadauskas@lemmy.ml @tchambers @atomicpoet @LemmyDev