Expert mode of "Inspect queue"
I can understand your concerns regarding the expert mode of "Inspect queue", @Mario Vavti .I do think, however, that an admin should know what they’re doing when they delete entries from outq. A warning to that effect could certainly be included in the template, if it seems necessary.
In my view, automatically flagging a hub as offline if it has been unreachable for a long time seems a bit unreliable. For example, zotlabs.org has been permanently (!) unreachable for more than half a year now. Nevertheless, entries for zotlabs.org kept appearing in my queue, only to disappear again after a few delivery attempts. However, the hub was not marked as permanently offline (DB: `site` WHERE site_dead = 1), and entries for that hub kept reappearing. It was only by explicitly marking it using the button in expert mode that the value was entered into field 1.
The fundamental question (regardless of whether a hub is marked as permanently offline automatically after a certain period, or by explicitly marking it in expert mode) is: what happens if such a hub becomes accessible again after a long period of time? Is it, if necessary, marked as available again in some way? Otherwise, I would say there ought to be a module for the admin that displays the hubs marked as offline and, if necessary, allows them to be removed from this list.
We have had a different experience, hence the expert mode.
In this case we should make it reliable. zotlabs.org is a special case because it never ever returns a HTTP code.
AFAIK it will be marked alive again as soon as we get a message from it.
That sounds good! Then I won’t have to waste any more time thinking about it.
OK, let's leave it at that then.
But it does time out when trying over https. There's no reason we should ever contact it directly via HTTP is it?