# 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 27
# self = https://watcher.sour.is/conv/klh22ja
Huh! My Rust toy project (a simple "ls") indicates whether a file has some xattrs. Unlike the real "ls", my program shows a "+" sign if there is *any* xattr. The real "ls" only shows a "+" if ACL stuff is stored in those xattrs. And so, by accident, I found out that one of my files (so far) has an xattr called user.xdg.origin.url, which apparently shows the URL this file was downloaded from. 🤔
Huh! My Rust toy project (a simple "ls") indicates whether a file has some xattrs. Unlike the real "ls", my program shows a "+" sign if there is *any* xattr. The real "ls" only shows a "+" if ACL stuff is stored in those xattrs. And so, by accident, I found out that one of my files (so far) has an xattr called user.xdg.origin.url, which apparently shows the URL this file was downloaded from. 🤔
Huh! My Rust toy project (a simple "ls") indicates whether a file has some xattrs. Unlike the real "ls", my program shows a "+" sign if there is *any* xattr. The real "ls" only shows a "+" if ACL stuff is stored in those xattrs. And so, by accident, I found out that one of my files (so far) has an xattr called user.xdg.origin.url, which apparently shows the URL this file was downloaded from. 🤔
Haha, at least WebKit is still doing it (writing xattrs). It’s just that my standard download directory is on a Linux tmpfs, which apparently does not support xattrs?! I wasn’t aware of this. Also, copying a file using "cp -a" from a file system that does support them to a tmpfs silently drops the xattrs. "strace" shows that "fsetxattr()" is called, but it returns EOPNOTSUPP – and "cp" just ignores that, no warning. Great.
Haha, at least WebKit is still doing it (writing xattrs). It’s just that my standard download directory is on a Linux tmpfs, which apparently does not support xattrs?! I wasn’t aware of this. Also, copying a file using "cp -a" from a file system that does support them to a tmpfs silently drops the xattrs. "strace" shows that "fsetxattr()" is called, but it returns EOPNOTSUPP – and "cp" just ignores that, no warning. Great.
Haha, at least WebKit is still doing it (writing xattrs). It’s just that my standard download directory is on a Linux tmpfs, which apparently does not support xattrs?! I wasn’t aware of this. Also, copying a file using "cp -a" from a file system that does support them to a tmpfs silently drops the xattrs. "strace" shows that "fsetxattr()" is called, but it returns EOPNOTSUPP – and "cp" just ignores that, no warning. Great.
@movq Yeah, might be a privacy issues I remember I also considering storing my downloads on a tmpfs but I actually always go back to that directory for some files. That's a "everything is allowed here" kinda of directory.
@movq Yeah, might be a privacy issue I remember I was also considering storing my downloads on a tmpfs but I actually always go back to that directory for some files. That's a "everything is allowed here" kinda of directory.
@movq Yeah, might be a privacy issue I remember I was also considering storing my downloads on a tmpfs but I actually always go back to that directory for some files. That's a "everything is allowed here" kinda of directory.
Interestimg find there @movq I wasn’t aware of this xattr feature either
Interestimg find there @movq I wasn’t aware of this xattr feature either
@lyse They’re a super hidden feature, unfortunately, and not particularly portable. OpenBSD has no concept of xattrs, for example. ZFS needs special tuning or it will store xattrs in hidden directories (as normal files), which is extremely slow. I once added xattrs to *all* my files (the xattr contained a checksum of the file – the point was to detect silent bitrot, I can elaborate if needed), which worked fine on ext4 – but I send all my backups to a NAS with ZFS and that turned out to be extremely slow now. 😢
@lyse They’re a super hidden feature, unfortunately, and not particularly portable. OpenBSD has no concept of xattrs, for example. ZFS needs special tuning or it will store xattrs in hidden directories (as normal files), which is extremely slow. I once added xattrs to *all* my files (the xattr contained a checksum of the file – the point was to detect silent bitrot, I can elaborate if needed), which worked fine on ext4 – but I send all my backups to a NAS with ZFS and that turned out to be extremely slow now. 😢
@lyse They’re a super hidden feature, unfortunately, and not particularly portable. OpenBSD has no concept of xattrs, for example. ZFS needs special tuning or it will store xattrs in hidden directories (as normal files), which is extremely slow. I once added xattrs to *all* my files (the xattr contained a checksum of the file – the point was to detect silent bitrot, I can elaborate if needed), which worked fine on ext4 – but I send all my backups to a NAS with ZFS and that turned out to be extremely slow now. 😢
@movq Conclusion: don't do backups anymore. :-P
@lyse That’s one option 🤣
@lyse That’s one option 🤣
@lyse That’s one option 🤣
@adi I love the borrow checker and the fact that there’s no garbage collection. I also like that Rust makes it hard for you to ignore or miss errors. On the other hand, the language has too many language features (too much syntax), which makes it super hard to learn. I’m still a total newbie, though, so my opinion might very well change in the future. 😁
@adi I love the borrow checker and the fact that there’s no garbage collection. I also like that Rust makes it hard for you to ignore or miss errors. On the other hand, the language has too many language features (too much syntax), which makes it super hard to learn. I’m still a total newbie, though, so my opinion might very well change in the future. 😁
@adi I love the borrow checker and the fact that there’s no garbage collection. I also like that Rust makes it hard for you to ignore or miss errors. On the other hand, the language has too many language features (too much syntax), which makes it super hard to learn. I’m still a total newbie, though, so my opinion might very well change in the future. 😁