@django@social.coop sounds like I'll have to implement it sooner rather than later!

@jonny @julian

i have no idea why nobody uses them or works on them

There is a FEP in the works:

Cookie monster!

(codeberg.org)

@akavel@merveilles.town thanks for your response

Did you manage to get to the bottom of it? From the description of the error it sounds like your certificate may be broken? Can you access the blog index from a normal browser? Do you perhaps have a split-domain situation (link != activitypub_link) but the certificate only applies to one?

@julian@fietkau.social @liaizon@wake.st it's all live, let me know if it works

@fabio @liaizon New quote test, wooo!

Madblog: A Markdown Folder That Federates Everywhere

Fabio's Blog

Fabio Manganiello (blog.fabiomanganiello.com)

@fabio I didn't investigate further as I had no idea how.

Which link specifically do you mean by "blog index"?

As to domain/instance I mean this one I'm writing from - I don't control it, sorry I see I wrote it in a confusing way, I'm just a plain citizen here.

Seeing you mention certs I will try on a laptop then, not on phone, to compare. Or could it be that the instance I'm on has some certs problems internally?

@silverpill@mitra.social @django@social.coop @hongminhee@hollo.social Okay, I implemented user outboxes for posts, votes, and shares (post edits are a little harder )

https://activitypub.space/uid/1/outbox

Hopefully I did it ok, had to re-invent some collection logic because I couldn't re-use the helper I wrote before, as that relies on a pagination cursor, which, long story short, is not at all scalable when navigating through a user inbox.

Group outboxes to follow, but just hoping for a sanity check for now.

@julian I can read the outbox and activities

There is a minor problem with Like activities, which don't have a to field (this means nobody should be able to see them).

And while we're at it: when NodeBB sends a signed GET request, does it add a Digest header? I see warnings in my log due to invalid header value.

@django @hongminhee

@akavel@merveilles.town I mean if you open the home page of your blog from a normal browser (any browser, mobile or desktop) do you still see the certificate error? If that's not the case and you have a split domain configuration (so your blog is on a URL and your federated domain is on another) then double-check that both the certificates are valid.

@fabio Oh I didn't install your blog on my host yet! For now I wanted to comment/fave in _your_ blog and I couldn't do that - this is my problem...

@akavel@merveilles.town oh I see, that sounds weird though, many other people could interact already...could it be that you're in a MITM configuration with some corporate or private VPN injecting SSL certificates at runtime? I have similar issues when I browse from my corporate VPN domains that my VPN hasn't whitelisted yet - then it'll try to inject an invalid certificate

@fabio I _think_ I might need to ask the admins of the instance I'm on - assuming they'll have time and will to debug this. Maybe there's some quarrell between that server and your server. (Which one's at fault is a different matter - may be neither ;P)

@akavel@merveilles.town oh I think I see a potential issue here: https://merveilles.town/@fabio@manganiello.blog

I used to use WriteFreely on that ActivityPub domains before but now it's on Madblog, of course with a different signing key.

I see that your instance still cached some old posts of mine from the time the blog was on WriteFreely, but I can't search for new URLs.

I think that something off is happening on your instance because I can see that the cached version of my blog profile has now the updated profile fields (so it accepted the updates from my blog), but the latest cached post is from 2024 (and I've written more since then, both on WriteFreely and Madblog) and it can't find new ones.