# I am the Watcher. I am your guide through this vast new twtiverse.
#
# Usage:
# https://watcher.sour.is/api/plain/users View list of users and latest twt date.
# https://watcher.sour.is/api/plain/twt View all twts.
# https://watcher.sour.is/api/plain/mentions?uri=:uri View all mentions for uri.
# https://watcher.sour.is/api/plain/conv/:hash View all twts for a conversation subject.
#
# Options:
# uri Filter to show a specific users twts.
# offset Start index for quey.
# limit Count of items to return (going back in time).
#
# twt range = 1 17
# self = https://watcher.sour.is/conv/neho6la
Given that @lukas's pod mentano has been down for a while and unavailable and listed as a Multi-user pod on Yarn.social and we've been unable to reach him or get his attention -- Do you think we should make it a requirement that you list at least one way (_internally with us_) of contacting a pod operator of a multi-user pod? 🤔
Given that @lukas's pod mentano has been down for a while and unavailable and listed as a Multi-user pod on Yarn.social and we've been unable to reach him or get his attention -- Do you think we should make it a requirement that you list at least one way (_internally with us_) of contacting a pod operator of a multi-user pod? 🤔
Why is there a need to contact someone running a pod? If a pod comes up, fine. If it goes away, fine too. Decentralised, and on free will. No worries, no issues.
You guys are slightly missing the point and focusing on the wrong thing 😳
Let’s forget about the “contact” part for now, I just always try to put a human touch on things, but maybe let’s focus instead on the “technical problem” first? 🤔
You guys are slightly missing the point and focusing on the wrong thing 😳
Let’s forget about the “contact” part for now, I just always try to put a human touch on things, but maybe let’s focus instead on the “technical problem” first? 🤔
Let me restate the problem:
- Mentano is offline
- It is listed on Yarn.social as a multi-user pod
- Users cannot join it, it is offline / broken; but there is no way to know until you try.
Let me restate the problem:
- Mentano is offline
- It is listed on Yarn.social as a multi-user pod
- Users cannot join it, it is offline / broken; but there is no way to know until you try.
I suppose on the Yarn page you could have a live (or almost live) status next to the listing, and maybe even a health status based on how long its been out, similar to whem viewing a list of Invidious instances etc.
Obvious downside is this requires AJAX/JS and extra pinging of Pods? Anyway its one idea.
@eldersnake Not a bad idea, I thought about this too, since Yarn.social's landing page is s static page though, yeah it would have to be done with some client-side JS 😅
@eldersnake Not a bad idea, I thought about this too, since Yarn.social's landing page is s static page though, yeah it would have to be done with some client-side JS 😅