Comment on @ Hubzilla Support Forum These errors are thrown from the jsonld library ( l
@Harald Eilertsen Thanks for your reply.
The stack trace mentioned a part of an address:
I could identify the invoker in the server log as
First off, blocking infoseek.exchange under admin->security didn't seem to work. I had to block it via the .htaccess file. Then I recognized the trailing '/' as part of the host name! Adding this, Hubzilla's blocking works; the errors disappear. Up to now, it seems to be solved.
BTW, I apologize for the double post. Obviously my subscription to this channel is broken. I no longer see any forum posts in my stream. Needs to be repaired as well.
The stack trace mentioned a part of an address:
#8 /extend/addon/hzaddons/pubcrawl/Mod_Inbox.php(93): Zotlabs\Lib\ActivityStreams->__construct('{"@context":["h...', 'https://infosec...')I could identify the invoker in the server log as
2a01:4f8:2b03:ba1::3 - - [08/Jul/2026:21:51:58 +0200] "POST /inbox HTTP/1.1" 500 3676 "-" "Mastodon/4.7.0-alpha.1+glitch (http.rb/5.3.1; +https://infosec.exchange/)"First off, blocking infoseek.exchange under admin->security didn't seem to work. I had to block it via the .htaccess file. Then I recognized the trailing '/' as part of the host name! Adding this, Hubzilla's blocking works; the errors disappear. Up to now, it seems to be solved.
BTW, I apologize for the double post. Obviously my subscription to this channel is broken. I no longer see any forum posts in my stream. Needs to be repaired as well.
That seems like a bug to me. We should be able to match against only the domain name.
I had that happen to me to at some point. I think somebody with admin rights to this channel needs to go in and see if you're marked as unreachable or something.
Either Mastodon 4.7 dev is breaking cross-application federation, or Glitch is doing so by bolting out-of-whack stuff onto Mastodon 4.7 dev.
Knowing where these payloads come from may help debug the issue, but not sure if it's worth it if it's only from this site and it's using unstable software.
More specifically, infosec.exchange is running Glitch-soc based on the Mastodon 4.7.0 Alpha development version.
Glitch has been known to act up in combination with Mastodon, but not in this way. It'd be interesting to know if the same things happen in interactions with mastodon.online which is running vanilla Mastodon 4.7.0 Alpha.