Skip to main content


Papa Dragon Papa Dragon wrote the following post Mon, 04 Nov 2024 23:39:56 -0800
Hi all remaining @!Streams enthusiast,

I've noticed that during the last few days my Streams website are getting a lot slower to load the Stream (and pubstream). Only unusual thing I found in the logs is this:

2024-11-05T06:59:01Z:LOG_WARNING:9515b791a8:Router.php:160:__construct: Module {1} not found.<br>2024-11-05T06:59:01Z:LOG_INFO:9515b791a8:Router.php:161:__construct: index.php: page not found: /%7B1%7D ADDRESS: 2a01:e9a:bf8:4f0:9af5:1fb1:de0b:8509 QUERY: req=/%7B1%7D<br>2024-11-05T06:59:02Z:LOG_WARNING:9515b791a8:Router.php:160:__construct: Module {1} not found.<br>2024-11-05T06:59:02Z:LOG_INFO:9515b791a8:Router.php:161:__construct: index.php: page not found: /%7B1%7D ADDRESS: 2a01:e9a:bf8:4f0:9af5:1fb1:de0b:8509 QUERY: req=/%7B1%7D<br>

The IPv6 address that appears in these lines belongs to the computer I use to visit the website. I really don't know if this could be related to the pages taking ages to load.

@Papa Dragon

in reply to Streams

Somewhere in the javascript is a "sprintf" thingy that uses numbers in parens in a template. And some browsers try to "pre-fetch" the template because it looks like a URL.

It's an annoyance, but is harmless.

in reply to Streams

Also, I noticed in my logs that some messages related to a no longer existing account keep popping:

2024-11-05T08:21:35Z:LOG_INFO:377212232f:Webfinger.php:37:exec: fetching resource: https%3A%2F%2Fmastodon.sdf.org%2Fusers%2FTomCox from mastodon.sdf.org<br>2024-11-05T08:21:36Z:LOG_INFO:377212232f:Activity.php:124:fetch: fetch: https://mastodon.sdf.org/users/TomCox<br>2024-11-05T08:21:36Z:LOG_INFO:377212232f:Activity.php:149:fetch: fetch_actual: https://mastodon.sdf.org/users/TomCox<br>2024-11-05T08:21:36Z:LOG_INFO:377212232f:Url.php:224:get: error: https://mastodon.sdf.org/users/TomCox: <br>2024-11-05T08:21:36Z:LOG_INFO:377212232f:Activity.php:210:fetch: fetch failed: https://mastodon.sdf.org/users/TomCox<br>2024-11-05T08:21:36Z:LOG_INFO:377212232f:network.php:93:http_status: inbox:403 Permission denied<br>

This comes back nearly every minute while user mastodon.sdf.org/users/TomCox does not seem to exist. Is there any way I can read of those?
in reply to Streams

Only way I know to eliminate it is to de-federate with Mastodon. I mentioned this a week or so ago. Threads does the same.
in reply to Mike Macgirvin 🖥️

It's kind of insidious because they send a signed Delete/Actor activity. Before we can process the Delete, we need to check the signature. And to check the signature we need their public key; which was deleted on their own instance along with their account.


I'm genuinely surprised it doesn't break on their side already. Or maybe it does, but nobody has noticed it yet.

in reply to Jupiter Rowland's (streams) outlet

Hi @jupiter_rowland @mikedev @streams,
if you - while processing the Delete - get a 410 on the keyId - do you think the actor is deleted (what the delete was supposed to indicate) or not?

What else do you need?

in reply to Marcus Rohrmoser 🌻

in reply to Streams

What we've typically done is grab all known location records for this identity and loop through them until we find one where the public key verifies the current signature. If we do, we'll invalidate any other records with the same hostname. If we don't, we'll fetch a fresh actor record and try again.