#rafgment 🤦♂️
#fragment 🤦♂️
#fragment 🤦♂️
- Event: Yarn.social Online Meetup
- When: 25th May 2024 at 12:00pm UTC (midday)
- Where: Mills Meet : Yarn.social
- Cadence: 4th Saturday of every Month
Agenda:
> Anything we want to talk about. Twtxt, Yarn, self hosting, cool stuff you've been working on. chit-chat, whatever 😅
#Yarn.social #Meetup
- Event: Yarn.social Online Meetup
- When: 25th May 2024 at 12:00pm UTC (midday)
- Where: Mills Meet : Yarn.social
- Cadence: 4th Saturday of every Month
#Yarn.social #Meetup
- Event: Yarn.social Online Meetup
- When: 25th May 2024 at 12:00pm UTC (midday)
- Where: Mills Meet : Yarn.social
- Cadence: 4th Saturday of every Month
Agenda:
> Anything we want to talk about. Twtxt, Yarn, self hosting, cool stuff you've been working on. chit-chat, whatever 😅
#Yarn.social #Meetup
https://calendar.google.com/calendar/event?action=TEMPLATE&tmeid=MDJuM2hzNThvaWsydTdoa3B2ODl0dGxlZzFfMjAyNDA1MjVUMTIwMDAwWiBwcm9sb2dpY0BzaG9ydGNpcmN1aXQubmV0LmF1&tmsrc=prologic%40shortcircuit.net.au&scp=ALL">
$ curl -qssL https://twtxt.net/ | grep -E 'In-reply-to' | head
<a href="https://twtxt.net/conv/2tjsjuq?p=1#rlsxhsq" title="Show conversation for #2tjsjuq">In-reply-to</a>
<a href="https://twtxt.net/conv/bghmkra?p=1#dfnrbyq" title="Show conversation for #bghmkra">In-reply-to</a>
<a href="https://twtxt.net/conv/e24exeq?p=1#itft6wa" title="Show conversation for #e24exeq">In-reply-to</a>
For some reason the latest version of Chrome is stripped
#fragment(s) from the HTML body being served.da fuq?! When did this change, in what version? Did we (W3C and the community) agree that this behavior should change?! 😱 Fark'n hell Google™ Chrome 🤬
$ curl -qssL https://twtxt.net/ | grep -E 'In-reply-to' | head
<a href="https://twtxt.net/conv/2tjsjuq?p=1#rlsxhsq" title="Show conversation for #2tjsjuq">In-reply-to</a>
<a href="https://twtxt.net/conv/bghmkra?p=1#dfnrbyq" title="Show conversation for #bghmkra">In-reply-to</a>
<a href="https://twtxt.net/conv/e24exeq?p=1#itft6wa" title="Show conversation for #e24exeq">In-reply-to</a>
For some reason the latest version of Chrome is stripped
#fragment(s) from the HTML body being served.da fuq?! When did this change, in what version? Did we (W3C and the community) agree that this behavior should change?! 😱 Fark'n hell Google™ Chrome 🤬
psh, was supposed to be base but the damn heat and humidity really brought that heart rate up. the last mile i felt it and was done w/ only three minutes left on the timer.
#running
psh, was supposed to be a base but the damn heat and humidity really brought that HR up. the last mile i felt it and was done with only three minutes left on the timer.
#running
psh, was supposed to be a base but the damn heat and humidity really brought that HR up. the last mile i felt it and was done with only three minutes left on the timer.
#running
psh, was supposed to be a base but the damn heat and humidity really brought that HR up. the last mile i felt it and was done with only three minutes left on the timer.
#running
jenny -l. 🤔 Currently it only shows the last successful retrieval time.)
jenny -l. 🤔 Currently it only shows the last successful retrieval time.)
jenny -l. 🤔 Currently it only shows the last successful retrieval time.)
jenny -l. 🤔 Currently it only shows the last successful retrieval time.)
BUIDL thing. Was it always suppose to be the commit timestamp? 🤔
BUIDL thing. Was it always suppose to be the commit timestamp? 🤔
twtxt client right? 🤔
twtxt client right? 🤔
yarnd; I haven't really noticed when it happens. But I went and had a look just now, looks like it "just works"™ and no-one notices 🤣
$ dke -t f3fe6f03902e /bin/sh
/ # cd /data/feeds
/data/feeds # ls -lah prologic*
-rw-r--r-- 1 yarnd yarnd 7.9K May 7 05:16 prologic
-rw-r--r-- 1 yarnd yarnd 877.8K May 3 23:32 prologic.1
-rw-r--r-- 1 yarnd yarnd 515.1K Mar 24 2023 prologic.2
-rw-r--r-- 1 yarnd yarnd 963.7K Nov 19 2022 prologic.3
-rw-r--r-- 1 yarnd yarnd 995.6K Mar 10 2022 prologic.4
-rw-r--r-- 1 yarnd yarnd 1.9M Nov 7 2021 prologic.5
yarnd; I haven't really noticed when it happens. But I went and had a look just now, looks like it "just works"™ and no-one notices 🤣
$ dke -t f3fe6f03902e /bin/sh
/ # cd /data/feeds
/data/feeds # ls -lah prologic*
-rw-r--r-- 1 yarnd yarnd 7.9K May 7 05:16 prologic
-rw-r--r-- 1 yarnd yarnd 877.8K May 3 23:32 prologic.1
-rw-r--r-- 1 yarnd yarnd 515.1K Mar 24 2023 prologic.2
-rw-r--r-- 1 yarnd yarnd 963.7K Nov 19 2022 prologic.3
-rw-r--r-- 1 yarnd yarnd 995.6K Mar 10 2022 prologic.4
-rw-r--r-- 1 yarnd yarnd 1.9M Nov 7 2021 prologic.5
git show -s --pretty=format:%cI
Otherwise, I'm just exploring new tty stuff ... Anything I should try?
Otherwise, I'm just exploring new tty stuff ... Anything I should try?
Don't think it has any kind of e2e encryption though? 🤔
Don't think it has any kind of e2e encryption though? 🤔
date -Is, which doesn’t exist on OpenBSD. Not sure how relevant this platform is for you, though. 😅I haven’t come up with a portable solution yet.
date '+%FT%T%z' is the closest approximation that works on both GNU and OpenBSD, but it doesn’t include a colon in the time zone offset, so it’s 0200 instead of 02:00. 🤦 I’m not sure if this is ISO8601 compliant. And it’s still not POSIX. 🤦 Well, I tried. 😂
date -Is, which doesn’t exist on OpenBSD. Not sure how relevant this platform is for you, though. 😅I haven’t come up with a portable solution yet.
date '+%FT%T%z' is the closest approximation that works on both GNU and OpenBSD, but it doesn’t include a colon in the time zone offset, so it’s 0200 instead of 02:00. 🤦 I’m not sure if this is ISO8601 compliant. And it’s still not POSIX. 🤦 Well, I tried. 😂
date -Is, which doesn’t exist on OpenBSD. Not sure how relevant this platform is for you, though. 😅I haven’t come up with a portable solution yet.
date '+%FT%T%z' is the closest approximation that works on both GNU and OpenBSD, but it doesn’t include a colon in the time zone offset, so it’s 0200 instead of 02:00. 🤦 I’m not sure if this is ISO8601 compliant. And it’s still not POSIX. 🤦 Well, I tried. 😂
date -Is, which doesn’t exist on OpenBSD. Not sure how relevant this platform is for you, though. 😅I haven’t come up with a portable solution yet.
date '+%FT%T%z' is the closest approximation that works on both GNU and OpenBSD, but it doesn’t include a colon in the time zone offset, so it’s 0200 instead of 02:00. 🤦 I’m not sure if this is ISO8601 compliant. And it’s still not POSIX. 🤦 Well, I tried. 😂
~/go/bin to your $PATH, at least I did. I’m not sure what to do about it, though. 🤔 This doesn’t really belong into Yarn’s setup guide and it’s mentioned as one of the first things in the Arch wiki, for example, but still … To newcomers this might look a bit like a broken build process:
openbsd$ gmake server
/bin/sh: minify: not found
/bin/sh: minify: not found
/bin/sh: minify: not found
gmake: *** [Makefile:84: generate] Error 127
Maybe extend Yarn’s guide just a *little* bit, like: “… be sure to have Go installed and set up properly, e.g. env vars are set …”? Maybe that could point readers into the right direction. 🤔
~/go/bin to your $PATH, at least I did. I’m not sure what to do about it, though. 🤔 This doesn’t really belong into Yarn’s setup guide and it’s mentioned as one of the first things in the Arch wiki, for example, but still … To newcomers this might look a bit like a broken build process:
openbsd$ gmake server
/bin/sh: minify: not found
/bin/sh: minify: not found
/bin/sh: minify: not found
gmake: *** [Makefile:84: generate] Error 127
Maybe extend Yarn’s guide just a *little* bit, like: “… be sure to have Go installed and set up properly, e.g. env vars are set …”? Maybe that could point readers into the right direction. 🤔
~/go/bin to your $PATH, at least I did. I’m not sure what to do about it, though. 🤔 This doesn’t really belong into Yarn’s setup guide and it’s mentioned as one of the first things in the Arch wiki, for example, but still … To newcomers this might look a bit like a broken build process:
openbsd$ gmake server
/bin/sh: minify: not found
/bin/sh: minify: not found
/bin/sh: minify: not found
gmake: *** [Makefile:84: generate] Error 127
Maybe extend Yarn’s guide just a *little* bit, like: “… be sure to have Go installed and set up properly, e.g. env vars are set …”? Maybe that could point readers into the right direction. 🤔
~/go/bin to your $PATH, at least I did. I’m not sure what to do about it, though. 🤔 This doesn’t really belong into Yarn’s setup guide and it’s mentioned as one of the first things in the Arch wiki, for example, but still … To newcomers this might look a bit like a broken build process:
openbsd$ gmake server
/bin/sh: minify: not found
/bin/sh: minify: not found
/bin/sh: minify: not found
gmake: *** [Makefile:84: generate] Error 127
Maybe extend Yarn’s guide just a *little* bit, like: “… be sure to have Go installed and set up properly, e.g. env vars are set …”? Maybe that could point readers into the right direction. 🤔
The backup run from my main workstation onto the NAS took 2.5 hours. The one from my laptop to the NAS took 1.75 hours (hmm, why the difference?). (Those two ran one after the other, not at the same time.)
The backup run from my NAS onto one of the USBs disks is still running, I started it 5.5 hours ago. I hope it’ll finish within the next 2 hours.
Most of this is CPU-bound, because I’m using full disk encryption everywhere and that NAS only has a tiny AMD C-60 CPU from ~2011 which runs at 1 GHz and doesn’t even have a CPU fan. I guess I could upgrade this box, but it’s still *working*, just slow, so I won’t throw it in the trash – and what do I do with it then? Can’t sell it, can’t gift it to anyone. So I’ll keep using it.~
The backup run from my main workstation onto the NAS took 2.5 hours. The one from my laptop to the NAS took 1.75 hours (hmm, why the difference?). (Those two ran one after the other, not at the same time.)
The backup run from my NAS onto one of the USBs disks is still running, I started it 5.5 hours ago. I hope it’ll finish within the next 2 hours.
Most of this is CPU-bound, because I’m using full disk encryption everywhere and that NAS only has a tiny AMD C-60 CPU from ~2011 which runs at 1 GHz and doesn’t even have a CPU fan. I guess I could upgrade this box, but it’s still *working*, just slow, so I won’t throw it in the trash – and what do I do with it then? Can’t sell it, can’t gift it to anyone. So I’ll keep using it.~
The backup run from my main workstation onto the NAS took 2.5 hours. The one from my laptop to the NAS took 1.75 hours (hmm, why the difference?). (Those two ran one after the other, not at the same time.)
The backup run from my NAS onto one of the USBs disks is still running, I started it 5.5 hours ago. I hope it’ll finish within the next 2 hours.
Most of this is CPU-bound, because I’m using full disk encryption everywhere and that NAS only has a tiny AMD C-60 CPU from ~2011 which runs at 1 GHz and doesn’t even have a CPU fan. I guess I could upgrade this box, but it’s still *working*, just slow, so I won’t throw it in the trash – and what do I do with it then? Can’t sell it, can’t gift it to anyone. So I’ll keep using it.~
The backup run from my main workstation onto the NAS took 2.5 hours. The one from my laptop to the NAS took 1.75 hours (hmm, why the difference?). (Those two ran one after the other, not at the same time.)
The backup run from my NAS onto one of the USBs disks is still running, I started it 5.5 hours ago. I hope it’ll finish within the next 2 hours.
Most of this is CPU-bound, because I’m using full disk encryption everywhere and that NAS only has a tiny AMD C-60 CPU from ~2011 which runs at 1 GHz and doesn’t even have a CPU fan. I guess I could upgrade this box, but it’s still *working*, just slow, so I won’t throw it in the trash – and what do I do with it then? Can’t sell it, can’t gift it to anyone. So I’ll keep using it.~