YGGverse
ufmПомнится я писал, что #nostr - очень удобная, распределённая (и в результате - отказоустойчивая) хранилка данных. Например для каких-то конфигов. Или как база для какого-то софта. И удивлялся, почему никто не пользуется.
Не. Оказалось - я ни разу не самый умный. Пользуются. Как пример - #FIPS. Это еще одна, очередная, бурно развивающаяся #mesh сеть. И каждая нода (как я понимаю - по желанию) хранит инфу про себя в ностре.
nak req -k 37195 wss://relay.damus.io wss://nos.lol wss://offchain.pub wss://temp.iris.to|wc -l
connecting to relay.damus.io... ok.
connecting to nos.lol... ok.
connecting to offchain.pub... ok.
connecting to temp.iris.to... ok.
619
И 619 узлов для буквально недавно радившеся сети, я-бы сказал - не мало. Кто все эти люди?
p.s. а еще они не стали заморачиваться, и работают прям с ключами nostr. Т.е. например @a58c5b71 - это прямо адрес ноды. И из него получается ip адрес. Прикольно...
gary@leblueelephant @jerry i have faith something will work out - I may have to get another email somewhere #fips compliant #fido #open source yubi forks
bot
ferricoxideAutomating the installation of a #Windows package that is really not designed for multi-user installation is decidedly un-fun. It's especially unfun when:
1. The
2. The
Ultimately had to kludge around the limitations by leveraging temporary #NTFS filesystem-junctions (what we, who normally only dick with #Linux, might call "symbolic links").
1. Create junction
2. Point the
3. Once the
4. Update the registry-entries that tell Windows where to find the application's uninstaller
The #Linux installation wasn't great, either, but the "installer" limitations were marginally less-kludgey to work around. The software doesn't come as an #RPM, so, it didn't come with any #SELinux rules (on the plus side of not being an RPM, I didn't have to worry if it used a signature or file-digest algorithms that weren't FIPS-compatible). Since the installation-targets are SELinux (and #FIPS!) enabled, had to add further logic to the automation to set up the proper SELinux contexts. We'll see how well that works, once the whitelist daemon is activated…
But still, "ugh. I hate Windows".
1. The
setup.exe doesn't prompt for a multi-user vs "self" install2. The
setup.exe absolutely refuses to install to paths with spaces in their name (you know, like C:\Program Files\<APPLICATION_NAME>Ultimately had to kludge around the limitations by leveraging temporary #NTFS filesystem-junctions (what we, who normally only dick with #Linux, might call "symbolic links").
1. Create junction
2. Point the
setup.exe at the junction-path3. Once the
setup.exe completes, nuke the junction-path4. Update the registry-entries that tell Windows where to find the application's uninstaller
The #Linux installation wasn't great, either, but the "installer" limitations were marginally less-kludgey to work around. The software doesn't come as an #RPM, so, it didn't come with any #SELinux rules (on the plus side of not being an RPM, I didn't have to worry if it used a signature or file-digest algorithms that weren't FIPS-compatible). Since the installation-targets are SELinux (and #FIPS!) enabled, had to add further logic to the automation to set up the proper SELinux contexts. We'll see how well that works, once the whitelist daemon is activated…
But still, "ugh. I hate Windows".
iRODSiRODS Development Update: May 2026
https://irods.org/2026/05/irods-development-update-may-2026/
i don't want to be a curmudgeon, some of that attitude is warranted but you still have to produce and try some things. I am working on basic 5 page site template but also bigger efforts, addressing smb mkt not just local break/fix mkt. maybe the bootable nvme idea (hardened deb) with persistence and enc - a must for the road warrior but good for anyone who values security and privacy #fido #fips #extras #working drivers #vetted #pentoo #ventoy
iRODS Development Update: April 2026
- Policy Composition
- Logical Quotas
- S3 Trailing Checksums
- FIPS Compliance
https://irods.org/2026/04/irods-development-update-april-2026/
AllpointsI'm trying to understand why I would choose a regular AWS endpoint over FIPS. I know why and when I have to use FIPS. Given that I have a subset of customers that require it, why not just use it for all customers? One would hope if the ciphers in FIPS are good enough for the government, they're good enough for regular use.
LachgasStecke im Bus, vor einem Einsatz mit blau blinkenden Lichtern und Drehleiter am Bahnhof in Schlierbach.
Dabei musste doch nur kurz eine Sendung auf der Post holen.
Hin bin ich mit #Fips (der Haltepunkt war bisschen meh). Erneut für einen Fahrer "die Erste in Heidelberg", aber er hatte schon einmal jemanden in Mannheim mit Rollstuhl. "Wenn Sie öfter mit uns fahren können die anderen lernen"
Dabei musste doch nur kurz eine Sendung auf der Post holen.
Hin bin ich mit #Fips (der Haltepunkt war bisschen meh). Erneut für einen Fahrer "die Erste in Heidelberg", aber er hatte schon einmal jemanden in Mannheim mit Rollstuhl. "Wenn Sie öfter mit uns fahren können die anderen lernen"