# 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 60337
# self = https://watcher.sour.is?uri=https://twtxt.net/user/prologic/twtxt.txt&offset=59591
# next = https://watcher.sour.is?uri=https://twtxt.net/user/prologic/twtxt.txt&offset=59691
# prev = https://watcher.sour.is?uri=https://twtxt.net/user/prologic/twtxt.txt&offset=59491
@andros I never really understood this "CLEAN" architecture... π
Can you explain it in your own words as you understand it to mean? π€
@andros I never really understood this "CLEAN" architecture... π
Can you explain it in your own words as you understand it to mean? π€
@doesnm I don't think this has anything to do with yarnd, but SSH keys in general π
@doesnm I don't think this has anything to do with yarnd, but SSH keys in general π
1. Make sure the machine is off. β
(_confirmed via remote IPMI_)
1. Unplug the power cables.
1. Unrack the machine.
1. Bring to office bench.
1. Unscrew the cover.
1. Plug in a new SATA DOM on a spare SATA cable.
1. Boot a bootable Live Linux Rescue system
1. Login and confirm both SATA DOM(s) are visible
1. Use dd to copy the contents of the old SATA DOM to the New.
1. Power off
1. Remove old SATA DOM
1. Confirm the machine comes back in it's original state.
1. Make sure the machine is off. β
(_confirmed via remote IPMI_)
1. Unplug the power cables.
1. Unrack the machine.
1. Bring to office bench.
1. Unscrew the cover.
1. Plug in a new SATA DOM on a spare SATA cable.
1. Boot a bootable Live Linux Rescue system
1. Login and confirm both SATA DOM(s) are visible
1. Use dd to copy the contents of the old SATA DOM to the New.
1. Power off
1. Remove old SATA DOM
1. Confirm the machine comes back in it's original state.
Took today off work. My workplace has a special form of leave called "My Day" that you can take in addition to your usual Annual leave. So nice! π I'm using one of them today to take advantage of the long weekend coming up (_Australia Day_). Planning on making repairs to one of my Hypervisor nodes that is currently down and powered off for repairs. The SATA DOM (_Disk on Module_) boot disk is kind of dead and the controller refusing to take any new writes. It's about ~5 years old π€£
Plan is to take the machine out of the Rack, place it on my office desk to open it up. Plug in a new 2nd SATA DOM on another SAtA cable. Boot it back up with a Linux Rescue bootable ISO and do a dd of the old to the new. Then swap 'em around and _hope_ π€ for the best π
~
Took today off work. My workplace has a special form of leave called "My Day" that you can take in addition to your usual Annual leave. So nice! π I'm using one of them today to take advantage of the long weekend coming up (_Australia Day_). Planning on making repairs to one of my Hypervisor nodes that is currently down and powered off for repairs. The SATA DOM (_Disk on Module_) boot disk is kind of dead and the controller refusing to take any new writes. It's about ~5 years old π€£
Plan is to take the machine out of the Rack, place it on my office desk to open it up. Plug in a new 2nd SATA DOM on another SAtA cable. Boot it back up with a Linux Rescue bootable ISO and do a dd of the old to the new. Then swap 'em around and _hope_ π€ for the best π
~
@movq Docker Swarm to the rescue! π€£
@movq Docker Swarm to the rescue! π€£
@doesnm It stores it in the devices secure store, whatever that is on the device. It's different for Android and iOS.
@doesnm It stores it in the devices secure store, whatever that is on the device. It's different for Android and iOS.
@aelaraji Haha don't ask me π€£ I don't do PHP π
@aelaraji Haha don't ask me π€£ I don't do PHP π
It's nice to see we're all largely thinking along the same lines. e.g: Salty.im π
It's nice to see we're all largely thinking along the same lines. e.g: Salty.im π
@eapl.me Yeah this is true. Previously RSA and AES were more common. These days Salsa and Chacha and Curve are fairly prevalent. For example all the Wireguard stuff uses Curve25519 / Ed25519 crypto. Signal uses very similar crypto too, but with some very nice double ratcheting 3DH.
@eapl.me Yeah this is true. Previously RSA and AES were more common. These days Salsa and Chacha and Curve are fairly prevalent. For example all the Wireguard stuff uses Curve25519 / Ed25519 crypto. Signal uses very similar crypto too, but with some very nice double ratcheting 3DH.
@eapl.me I _-think_ we've gotten use to it somewhat π€£
@eapl.me I _-think_ we've gotten use to it somewhat π€£
@doesnm whilst technically true, expensive and unnecessary.
@doesnm whilst technically true, expensive and unnecessary.
ππ Reminders that this weekend our monthly Yarn.social online meetup. Who's coming? π€ Some possible topics:
- Direct Messaging for Twtxt
- @prologic 's new EdgeGuard services π€£
- What's the weather like? π
Details:
- When: 25th Jan 2025 at 12:00PM UTC (midday)
- Where: https://meet.mills.io/call/Yarn.social
ππ Reminders that this weekend our monthly Yarn.social online meetup. Who's coming? π€ Some possible topics:
- Direct Messaging for Twtxt
- @prologic 's new EdgeGuard services π€£
- What's the weather like? π
Details:
- When: 25th Jan 2025 at 12:00PM UTC (midday)
- Where: https://meet.mills.io/call/Yarn.social
@eapl.me@eapl.me actually it is easy π€£ It's now the standard for SSH keys π
@eapl.me@eapl.me actually it is easy π€£ It's now the standard for SSH keys π
@xuu Is this because there's a bug in persisting trusted peers? π€
@xuu Is this because there's a bug in persisting trusted peers? π€
@lyse This is a good point.
@lyse This is a good point.
@doesnm That's _actually_ not true, because you'd have to know the target you're interested in, in the first place. Inboxes in Salty.IM are deliberately shahed for this reason. So whilst you _may_ know your own inbox address, etc, I (_as an arbitrary bad actor_) wouldn't easily be able to guess (_let alone brute force_) my way to another inbox address of an interested party.
@doesnm That's _actually_ not true, because you'd have to know the target you're interested in, in the first place. Inboxes in Salty.IM are deliberately shahed for this reason. So whilst you _may_ know your own inbox address, etc, I (_as an arbitrary bad actor_) wouldn't easily be able to guess (_let alone brute force_) my way to another inbox address of an interested party.
@xuu Can you elaborate in textual form for the poor vision impaired developer π€£ π
@xuu Can you elaborate in textual form for the poor vision impaired developer π€£ π
It would also be great if you put up a PR against twtxt.dev π
It would also be great if you put up a PR against twtxt.dev π
@andros My only comment so far is to use Ed25519 keys for crypto.
@andros My only comment so far is to use Ed25519 keys for crypto.
@bender planning on being around in 10 years π€ π
@bender planning on being around in 10 years π€ π
@kat Do you want to stand it up on your own or use it as a service? π€π€
@kat Do you want to stand it up on your own or use it as a service? π€π€
@kat sounds intriguing π€
@kat sounds intriguing π€
EdgeGuard Update:
I am now in a position where I'm no longer having any ports open on my firewall at the Mills DC. π₯³ All services (Gopher, SMTP, IRC, SSH, HTTP) are being proxied through my edge network πͺ
EdgeGuard Update:
I am now in a position where I'm no longer having any ports open on my firewall at the Mills DC. π₯³ All services (Gopher, SMTP, IRC, SSH, HTTP) are being proxied through my edge network πͺ
@xuu Speaking of TV Shows, can anyone recommend anything good of late? Hmm π€
@xuu Speaking of TV Shows, can anyone recommend anything good of late? Hmm π€
@doesnm Hmmm yhe flow doesn't look right to me hmm π€
@doesnm Hmmm yhe flow doesn't look right to me hmm π€
@doesnm Is that implementing IndieAuth? π€
@doesnm Is that implementing IndieAuth? π€
Would anyone object to the feeds.twtxt.net service having auth soonβ’ ? π€ I'm tired of the garbage feeds that it has accumulated over tie (_spammers_) and I want to a) clean it up b) lock it down somewhat.
The idea would be that you'd login with your Yarn.social account on some pod you control/operate or share with a nice person π€£ -- For those unfamiliar, this is called IndieAuth or IndieLogin. ALL Yarn.social pods are in fact valid (_have been for years now_) IndieAuth Providers. So I can just ust that. This also technically means you _could_ login with your own domain too (_more on that later..._)
Would anyone object to the feeds.twtxt.net service having auth soonβ’ ? π€ I'm tired of the garbage feeds that it has accumulated over tie (_spammers_) and I want to a) clean it up b) lock it down somewhat.
The idea would be that you'd login with your Yarn.social account on some pod you control/operate or share with a nice person π€£ -- For those unfamiliar, this is called IndieAuth or IndieLogin. ALL Yarn.social pods are in fact valid (_have been for years now_) IndieAuth Providers. So I can just ust that. This also technically means you _could_ login with your own domain too (_more on that later..._)
@hacker-news-newest TL;DR:
> The author recounts their experience with a βno callsβ policy in enterprise sales, finding it surprisingly effective. They attribute this success to addressing common reasons for callsβlack of understanding, onboarding issues, pricing uncertainty, and trust concernsβthrough clear messaging, self-serve onboarding, transparent pricing, and robust security documentation. While acknowledging potential limitations, the author advocates for a #nocalls approach, emphasizing the benefits of efficiency and alignment with their values.
@hacker-news-newest TL;DR:
> The author recounts their experience with a βno callsβ policy in enterprise sales, finding it surprisingly effective. They attribute this success to addressing common reasons for callsβlack of understanding, onboarding issues, pricing uncertainty, and trust concernsβthrough clear messaging, self-serve onboarding, transparent pricing, and robust security documentation. While acknowledging potential limitations, the author advocates for a #nocalls approach, emphasizing the benefits of efficiency and alignment with their values.
@lyse Who does right π€£ I wonder if anyone read the ToC(s) of any Yarn pod? π€
@lyse Who does right π€£ I wonder if anyone read the ToC(s) of any Yarn pod? π€
@news-minimalist Ahh now I like to read news like this in my feed. THis is perfect! π€© Thank you @bender and so far this is such a nice quite way to be "informed" without the _noise_ and sensational crappy clickbait shitβ’
@news-minimalist Ahh now I like to read news like this in my feed. THis is perfect! π€© Thank you @bender and so far this is such a nice quite way to be "informed" without the _noise_ and sensational crappy clickbait shitβ’
@arne To be honest I don't _really_ understand why anyone would use Facebookβ’, X/Twitterβ’, TikTokβ’ Instagramβ’, etc... When it clearly states in their Terms of Conditions that the content you "enter" into _their_ systems, is NOT yours.
@arne To be honest I don't _really_ understand why anyone would use Facebookβ’, X/Twitterβ’, TikTokβ’ Instagramβ’, etc... When it clearly states in their Terms of Conditions that the content you "enter" into _their_ systems, is NOT yours.
@andros Created. Can you try logging in via Github? I had to take a stab/guess at your Email address, which is very clearly wrong, but hopefully you an just update it when you login π€£π€£
@andros Created. Can you try logging in via Github? I had to take a stab/guess at your Email address, which is very clearly wrong, but hopefully you an just update it when you login π€£π€£
Actually. it's probably fine if you just drop your Github username/profile here. They're all public info anyway π€£π€£
Actually. it's probably fine if you just drop your Github username/profile here. They're all public info anyway π€£π€£
@andros I _believe_ I disabled new registrations by default due to increase in levels of "spam accounts". If you could email me, or DM me (IRC) your Github username, I'll add an account for you that matches your Github profile and you can sign-in that way.
Respectfully, I will not move any of my projects back to Github after this blog post; hope you can understand, but I'd prefer to stick to my moral values here as much as I can π
@andros I _believe_ I disabled new registrations by default due to increase in levels of "spam accounts". If you could email me, or DM me (IRC) your Github username, I'll add an account for you that matches your Github profile and you can sign-in that way.
Respectfully, I will not move any of my projects back to Github after this blog post; hope you can understand, but I'd prefer to stick to my moral values here as much as I can π
@kat Any ideas of the volume coming out of their RSS feed? π€