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.~
yarnd setup is needed. š¤I followed the instructions here and they were simple enough: https://git.mills.io/yarnsocial/yarn/src/branch/main/README.md#configuring-your-pod
It needs a little polishing (for example, it says
COOKIE_SECRET is optional which it isnāt), but it was a good experience overall.Maybe itās just me, but I prefer reading installation instructions. And I believe that *not* having something like
yarnd setup nudges you (the author) into keeping those instructions short and concise. Whereas the existence of yarnd setup means that you can cram everything and the kitchen sink in there, because itās convenient. That can lead to a convoluted setup process ā and me, the user, does not really know what that command really does, which is something that I, personally, donāt like. š
yarnd setup is needed. š¤I followed the instructions here and they were simple enough: https://git.mills.io/yarnsocial/yarn/src/branch/main/README.md#configuring-your-pod
It needs a little polishing (for example, it says
COOKIE_SECRET is optional which it isnāt), but it was a good experience overall.Maybe itās just me, but I prefer reading installation instructions. And I believe that *not* having something like
yarnd setup nudges you (the author) into keeping those instructions short and concise. Whereas the existence of yarnd setup means that you can cram everything and the kitchen sink in there, because itās convenient. That can lead to a convoluted setup process ā and me, the user, does not really know what that command really does, which is something that I, personally, donāt like. š
yarnd setup is needed. š¤I followed the instructions here and they were simple enough: https://git.mills.io/yarnsocial/yarn/src/branch/main/README.md#configuring-your-pod
It needs a little polishing (for example, it says
COOKIE_SECRET is optional which it isnāt), but it was a good experience overall.Maybe itās just me, but I prefer reading installation instructions. And I believe that *not* having something like
yarnd setup nudges you (the author) into keeping those instructions short and concise. Whereas the existence of yarnd setup means that you can cram everything and the kitchen sink in there, because itās convenient. That can lead to a convoluted setup process ā and me, the user, does not really know what that command really does, which is something that I, personally, donāt like. š
yarnd setup is needed. š¤I followed the instructions here and they were simple enough: https://git.mills.io/yarnsocial/yarn/src/branch/main/README.md#configuring-your-pod
It needs a little polishing (for example, it says
COOKIE_SECRET is optional which it isnāt), but it was a good experience overall.Maybe itās just me, but I prefer reading installation instructions. And I believe that *not* having something like
yarnd setup nudges you (the author) into keeping those instructions short and concise. Whereas the existence of yarnd setup means that you can cram everything and the kitchen sink in there, because itās convenient. That can lead to a convoluted setup process ā and me, the user, does not really know what that command really does, which is something that I, personally, donāt like. š
No way of telling whatās going on, itās all encrypted ā¦
No way of telling whatās going on, itās all encrypted ā¦
No way of telling whatās going on, itās all encrypted ā¦
No way of telling whatās going on, itās all encrypted ā¦
> things we don't even know about or have any control over (_or very little_)
Thatās the thing: Itās not *apps* doing weird stuff, itās the phoneās operating system itself. I can choose which apps to run and which permissions they have, thatās all fine, but what the fuck is āImsAppā and why does it need access to GPS and my camera?! Completely untrustworthy.
> things we don't even know about or have any control over (_or very little_)
Thatās the thing: Itās not *apps* doing weird stuff, itās the phoneās operating system itself. I can choose which apps to run and which permissions they have, thatās all fine, but what the fuck is āImsAppā and why does it need access to GPS and my camera?! Completely untrustworthy.
> things we don't even know about or have any control over (_or very little_)
Thatās the thing: Itās not *apps* doing weird stuff, itās the phoneās operating system itself. I can choose which apps to run and which permissions they have, thatās all fine, but what the fuck is āImsAppā and why does it need access to GPS and my camera?! Completely untrustworthy.
> things we don't even know about or have any control over (_or very little_)
Thatās the thing: Itās not *apps* doing weird stuff, itās the phoneās operating system itself. I can choose which apps to run and which permissions they have, thatās all fine, but what the fuck is āImsAppā and why does it need access to GPS and my camera?! Completely untrustworthy.
Even just looking at the log of attempted connections is scary. This thing is talking to everything all the time. Worse, there are some system apps that regularly query the deviceās GPS location and you canāt turn that off ā¦ Shitty spy device. š
Even just looking at the log of attempted connections is scary. This thing is talking to everything all the time. Worse, there are some system apps that regularly query the deviceās GPS location and you canāt turn that off ā¦ Shitty spy device. š
Even just looking at the log of attempted connections is scary. This thing is talking to everything all the time. Worse, there are some system apps that regularly query the deviceās GPS location and you canāt turn that off ā¦ Shitty spy device. š
Even just looking at the log of attempted connections is scary. This thing is talking to everything all the time. Worse, there are some system apps that regularly query the deviceās GPS location and you canāt turn that off ā¦ Shitty spy device. š
$thing back then?ā Happens to me all the time. š³
$thing back then?ā Happens to me all the time. š³
$thing back then?ā Happens to me all the time. š³
$thing back then?ā Happens to me all the time. š³
history | wc -l
history | wc -l
history | wc -l
history | wc -l
This is so very useful when writing text / prose. Itās especially useful for German text with all those long words like āInformationssicherheitsbeauftragerā. I use this feature all time and I sorely miss it when Iām forced to use some other crappy editor. š©
https://movq.de/v/96049c4aea/s.png
This is so very useful when writing text / prose. Itās especially useful for German text with all those long words like āInformationssicherheitsbeauftragerā. I use this feature all time and I sorely miss it when Iām forced to use some other crappy editor. š©
https://movq.de/v/96049c4aea/s.png
This is so very useful when writing text / prose. Itās especially useful for German text with all those long words like āInformationssicherheitsbeauftragerā. I use this feature all time and I sorely miss it when Iām forced to use some other crappy editor. š©
https://movq.de/v/96049c4aea/s.png
This is so very useful when writing text / prose. Itās especially useful for German text with all those long words like āInformationssicherheitsbeauftragerā. I use this feature all time and I sorely miss it when Iām forced to use some other crappy editor. š©
https://movq.de/v/96049c4aea/s.png
https://www.uninformativ.de/git/jenny/commit/698c4382208c5b5eb87999a30fd657167ab5b694.html
https://www.uninformativ.de/git/jenny/commit/698c4382208c5b5eb87999a30fd657167ab5b694.html
https://www.uninformativ.de/git/jenny/commit/698c4382208c5b5eb87999a30fd657167ab5b694.html
https://www.uninformativ.de/git/jenny/commit/698c4382208c5b5eb87999a30fd657167ab5b694.html
.vimrc:au BufRead,BufNewFile jenny-posting.eml setl fo-=t wrap=
.vimrc:au BufRead,BufNewFile jenny-posting.eml setl fo-=t wrap=
.vimrc:au BufRead,BufNewFile jenny-posting.eml setl fo-=t wrap=
.vimrc:au BufRead,BufNewFile jenny-posting.eml setl fo-=t wrap=
I bought a lot of DVDs over time and many of them have become unreadable. Star Trek DS9 is among the victims, parts of TNG, parts of X-Files. Really annoying. I didnāt have the required disk space to make backups and, honestly, didnāt think they would die so quickly. When/if I buy movies these days, I either make a backup right away or I treat those DVDs as āwill die soonā. š«¤
CDs regularly die, too, although not as often as DVDs.
And of course, lots of floppy disks are dead now. šš«¤~
I bought a lot of DVDs over time and many of them have become unreadable. Star Trek DS9 is among the victims, parts of TNG, parts of X-Files. Really annoying. I didnāt have the required disk space to make backups and, honestly, didnāt think they would die so quickly. When/if I buy movies these days, I either make a backup right away or I treat those DVDs as āwill die soonā. š«¤
CDs regularly die, too, although not as often as DVDs.
And of course, lots of floppy disks are dead now. šš«¤~
I bought a lot of DVDs over time and many of them have become unreadable. Star Trek DS9 is among the victims, parts of TNG, parts of X-Files. Really annoying. I didnāt have the required disk space to make backups and, honestly, didnāt think they would die so quickly. When/if I buy movies these days, I either make a backup right away or I treat those DVDs as āwill die soonā. š«¤
CDs regularly die, too, although not as often as DVDs.
And of course, lots of floppy disks are dead now. šš«¤~