# 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 37
# self = https://watcher.sour.is/conv/vjc33kq
(Yes, this is my crappy rendition of the pinky/ring finger excercise I posted recently. I hear like a million mistakes, but I hope you don’t. 🥴 Let’s see how it improves over time.)
(Yes, this is my crappy rendition of the pinky/ring finger excercise I posted recently. I hear like a million mistakes, but I hope you don’t. 🥴 Let’s see how it improves over time.)
(Yes, this is my crappy rendition of the pinky/ring finger excercise I posted recently. I hear like a million mistakes, but I hope you don’t. 🥴 Let’s see how it improves over time.)
@movq Wow, great! Quite up to speed, too, hats off! I don't hear a single mistake, but I'm also pretty bad at spotting them. :-) Carry on, happy practicing, mate!
@lyse Heh, thanks. 😁 (I intentionally played it at a lower pitch, because I thought it fit the slower speed better … 🤷)
@lyse Heh, thanks. 😁 (I intentionally played it at a lower pitch, because I thought it fit the slower speed better … 🤷)
@lyse Heh, thanks. 😁 (I intentionally played it at a lower pitch, because I thought it fit the slower speed better … 🤷)
@movq Sounding good there mate 👌 Looks like you’re practicing that piece quite well 😂
@movq Sounding good there mate 👌 Looks like you’re practicing that piece quite well 😂
@movq Don't forget to btrfs scrub e.g. once a week.
I'm using btrfs scrub -B /dev/xyz and mail the result to myself.
@stackeffect Once a *week*? That’s a lot. 🤔 There’s 2 TB on it, that’s going to take a while. 🤔
@stackeffect Once a *week*? That’s a lot. 🤔 There’s 2 TB on it, that’s going to take a while. 🤔
@stackeffect Once a *week*? That’s a lot. 🤔 There’s 2 TB on it, that’s going to take a while. 🤔
@stackeffect Let me rephrase: Is there a btrfs-specific reason to do regular scrubs? Or was it just general advice?
@stackeffect Let me rephrase: Is there a btrfs-specific reason to do regular scrubs? Or was it just general advice?
@stackeffect Let me rephrase: Is there a btrfs-specific reason to do regular scrubs? Or was it just general advice?
@movq I scrub my ZFS pool once a month and it’s sitting around ~12TB and only takes ~20m or so. I should do this once per week I think 🤔
@movq I scrub my ZFS pool once a month and it’s sitting around ~12TB and only takes ~20m or so. I should do this once per week I think 🤔
@prologic Isn’t a scrub supposed to read *everything*? So, reading 12 TB in 20 minutes would be, what, 10 GB per second? That’s a lot. 😲
@prologic Isn’t a scrub supposed to read *everything*? So, reading 12 TB in 20 minutes would be, what, 10 GB per second? That’s a lot. 😲
@prologic Isn’t a scrub supposed to read *everything*? So, reading 12 TB in 20 minutes would be, what, 10 GB per second? That’s a lot. 😲
@movq Good question. I’ll have to refer to the ZFS docs on that one 🤔
@movq Good question. I’ll have to refer to the ZFS docs on that one 🤔
@movq Manpage says
> The user is supposed to run it manually or via a periodic system
> service. The recommended period is a month but could be less.
So me doing it weekly is a bit over cautious. It's often overseen by users that they are supposed to perform this task regularly.
@stackeffect What I don’t understand here: *Why* am I supposed to do this? Does btrfs *require* this, i.e. it can cause real issues if I don’t do it (or not often enough)? Or is the purpose to try to catch hardware errors early on?
The manpage doesn’t state any reason. They simply added that section (“the user is supposed …”) at some point without further explanation. 🤔
@stackeffect What I don’t understand here: *Why* am I supposed to do this? Does btrfs *require* this, i.e. it can cause real issues if I don’t do it (or not often enough)? Or is the purpose to try to catch hardware errors early on?
The manpage doesn’t state any reason. They simply added that section (“the user is supposed …”) at some point without further explanation. 🤔
@stackeffect What I don’t understand here: *Why* am I supposed to do this? Does btrfs *require* this, i.e. it can cause real issues if I don’t do it (or not often enough)? Or is the purpose to try to catch hardware errors early on?
The manpage doesn’t state any reason. They simply added that section (“the user is supposed …”) at some point without further explanation. 🤔
@movq I always understood it as good practice to early catch hardware errors.