# 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 8
# self = https://watcher.sour.is/conv/vmlx2dq
Chris’ Wiki: Monitoring if our wireless network is actually working in locations
Oh dear. Wifi monitoring is really hard. We have the same problem. We tried to do what he proposes (setting up Raspberry Pis as “wifi probes”, setting up entire laptops, you name it, …), but we hardly gained any insights.
The nasty thing about wifi is that it’s not enough to know whether a device is connected or not. Yes, sure, if all your wifi probes in one area suddenly disconnect, then you have a problem. But how do you test for roaming? How do you test for client behaviour, like “wifi chip $a behaves ever so slightly different than chip $b”? How many probes do you deploy, one per room? That adds up quickly.
At the end of the day, many of our users are dissatisfied with our wifi – and we admins can’t reproduce their problems, because we don’t use the exact same configuration that they do. 😢
(We recently switched to offering Ethernet by default again. That’s much more convenient these days, because many laptops have USB-C: Users connect one cable and get everything – power, monitor, Ethernet, USB hub. Not all workplaces have such a setup, though.)
Chris’ Wiki: Monitoring if our wireless network is actually working in locations
Oh dear. Wifi monitoring is really hard. We have the same problem. We tried to do what he proposes (setting up Raspberry Pis as “wifi probes”, setting up entire laptops, you name it, …), but we hardly gained any insights.
The nasty thing about wifi is that it’s not enough to know whether a device is connected or not. Yes, sure, if all your wifi probes in one area suddenly disconnect, then you have a problem. But how do you test for roaming? How do you test for client behaviour, like “wifi chip $a behaves ever so slightly different than chip $b”? How many probes do you deploy, one per room? That adds up quickly.
At the end of the day, many of our users are dissatisfied with our wifi – and we admins can’t reproduce their problems, because we don’t use the exact same configuration that they do. 😢
(We recently switched to offering Ethernet by default again. That’s much more convenient these days, because many laptops have USB-C: Users connect one cable and get everything – power, monitor, Ethernet, USB hub. Not all workplaces have such a setup, though.)
Chris’ Wiki: Monitoring if our wireless network is actually working in locations
Oh dear. Wifi monitoring is really hard. We have the same problem. We tried to do what he proposes (setting up Raspberry Pis as “wifi probes”, setting up entire laptops, you name it, …), but we hardly gained any insights.
The nasty thing about wifi is that it’s not enough to know whether a device is connected or not. Yes, sure, if all your wifi probes in one area suddenly disconnect, then you have a problem. But how do you test for roaming? How do you test for client behaviour, like “wifi chip $a behaves ever so slightly different than chip $b”? How many probes do you deploy, one per room? That adds up quickly.
At the end of the day, many of our users are dissatisfied with our wifi – and we admins can’t reproduce their problems, because we don’t use the exact same configuration that they do. 😢
(We recently switched to offering Ethernet by default again. That’s much more convenient these days, because many laptops have USB-C: Users connect one cable and get everything – power, monitor, Ethernet, USB hub. Not all workplaces have such a setup, though.)
@movq I swear on cable whenever possible.
@lyse Yeah, most tech people do. Most non-tech people don’t, hence the drama. 😅
@lyse Yeah, most tech people do. Most non-tech people don’t, hence the drama. 😅
@lyse Yeah, most tech people do. Most non-tech people don’t, hence the drama. 😅
@lyse Yeah, most tech people do. Most non-tech people don’t, hence the drama. 😅