@andrewblasco Hello, we also use Stripe at https://joinvernissage.org/#donate. Translations are available in Crowdin at https://crowdin.com/project/vernissageweb. If you wish, create an account and I will grant the appropriate permissions.
@ajroach42 I've got bluetooth headphones with a 3.5mm trrs hole!
They still don't work unless charged 😑
@ifixcoinops I have a pair like that and it's somehow the worst of all worlds.
This is what is happening without copyeditors. They left off a zero.
Trump has long wanted to lose 15 pounds. Physicians wish he would. https://www.washingtonpost.com/politics/2026/08/23/doctors-say-trump-weight-poses-significant-health-risk/
@jeffjarvis You mean being old AND fat might be risky?
down with the white supremacist free software culture imo
Are you a content creator on #YouTube, blog using self-hosted CMS like #Wordpress? And do you have to deal with online harassment in the comments section?
At @show we've been helping @shirewood test out a new system that reduces creator exposure to targeted hate, be it racism, homophobia, transphobia, or xenophobia. It's a software program written by LGBTQIA+ folk designed to protect our own and other harassed folk.
Would you like to test it? Would you be interested in it as a service? And what would you pay for it?
@aminorjourney @show @shirewood I'd be interested in testing, especially for accessibility as I'm a blind user, building a site against HIV stigma. So harassment would be easy to come. Payment? I don't talk about it because I'd like to test it before, being probably made by sighted only, I doubt accessibility has been considered from the beginning. And I won't pay something that won't fit my accessibility needs/accomodations. My structure is WordPress - no youtube or other commercials.
You are given limited access to the Gearworks of Reality. You may delete one of these from human civilization.
@mttaggart I really was the guy with 2 buttons meme on this one. I ended up picking gambling because *damage over the entire history* but it's also the easier one to regulate.
Trump suggerisce di poter usare l’esercito sui mercati obbligazionari: ‘Se dobbiamo usarlo, lo faremo’
Venerdì il presidente psicopatico ha suggerito che potrebbe usare l'esercito per organizzare un "intervento sui mercati obbligazionari" mentre rispondeva in modo confuso a un giornalista che chiedeva informazioni sugli sforzi del Segretario al Tesoro Scott Bessent per abbassare i rendimenti alle stelle
https://www.yahoo.com/news/politics/articles/trump-suggests-military-bond-markets-222513278.html
@informapirata @politica
ho l'impressione che la cosa di maggior valore che quell'uomo ha in testa sia la forfora.
@quixoticgeek @alice is that the Hohenzollern bridge in Cologne?
Every Friday Stretch - Episode 6 - Hamstrings
Publications feed
Due to need for 'absolute success,' China delays critical Moon launch to 2027
"The Chang’e 7 mission does not meet the conditions for launch."
https://arstechnica.com/space/2026/08/due-to-need-for-absolute-success-china-delays-critical-moon-launch-to-2027/?utm_brand=arstechnica&utm_social-type=owned&utm_source=mastodon&utm_medium=social
@arstechnica 5 years from now China will own the moon uncontested
Which would you rather do? The 1% make more profit from the top photo...
@freediverx @dschaub Not quite. When Verizon installs their fiber service, they remove the old copper lines.
The POTS phone jack is powered by the fiber terminal and transmitted digitally over the fiber.
There's a small backup battery in the terminal for exactly this reason, but it's not made to last through extended outages. And if the fiber is "out" enough, the phone won't work, either.
For.. reasons.. I am making a wealth inequality playlist. I want songs that aren't TOO aggro and could be background-ish at an event, catchy, topical, without making themselves the center of attention. Here's what I have so far. Please parse this list and suggest along these lines, if you like.
- The O’Jays - For the Love of Money
- The Flying Lizards - Money (That’s What I Want)
- Pink Floyd - Money
- Pulp - Common People
- William Shatner / Ben Folds - Common People
- Stevie Wonder – Living For The City
- Marvin Gaye – Inner City Blues (Make Me Wanna Holler)
- Kareem Rahma – Really Rich Parents
- They Might Be Giants – Minimum Wage
- Lorde – Royals
- Pet Shop Boys – Opportunities (Let’s Make Lots of Money)
- Depeche Mode – Everything Counts
- The Police - Driven To Tears
- Hozier - Eat Your Young
- Tennessee Ernie Ford - Sixteen Tons
- Dolly Parton - 9 to 5
- Tracy Chapman - Talkin’ bout a Revolution
- Pete Seeger – Banks of Marble
- James McMurtry – We Can’t Make It Here
- Prince - Sign O’ The Times
- Patty Loveless - You’ll Never Leave Harlan Alive
- Travis Tritt - Lord Have Mercy on the Working Man
@codinghorror NOFX - The Irrationality Of Rationality
NOFX - Perfect Government
TIL the Netherlands hides massive rubbish bins underground so their streets stay clean 🤯
@TheBreadmonkey They're only closed on Kings Day, then all the trash is on the streets.
@barubary and here's what i sent to coreutils about the backdoor in linux crypto/
Hello coreutils,
I was hoping to open a discussion about implementing the BLAKE3 algorithm, the project's understanding of length extension attacks, and how an archive format might be able to take advantage of features of tree hashes of this variety in concert with an implementation such as coreutils.
I would love nothing more than to engage in this, but I happened to be made aware of a new section in the kernel config through what seems to have been "luck" on Friday and a lot of facially broken changes are being added at an incredible clip.
So that you can quickly determine if I am wasting your time: if you have a local checkout, the following abbreviated refs modify what I believe to be precisely an area coreutils builds using the `--with-linux-crypto` configure script would subsequently become affected by. These are from two engineers, one David Howells from Red Hat / IBM, and Eric Biggers of Google.
965e9a2cf23b066d8bdeb690dff9cd7089c5f667 pkcs7: Change a pr_warn() to pr_warn_once()
91db696adea4d76017b1e1f45915a5cbf04e8da3 pkcs7: Allow authenticatedAttributes for ML-DSA
0ad9a71933e73c8a2af101d28e9a1dc35bae02d5 modsign: Enable ML-DSA module signing
8bbdeb7a25b4cd3d829136a2e12982b8ee7d7991 pkcs7, x509: Add ML-DSA support
f3eccecd782dbaf33d5ad0d1fd22ea277300acdb pkcs7: Allow the signing algo to do whatever digestion it wants itself
f728074f1f577565c97e465652c3d4afb0964013 pkcs7, x509: Rename ->digest to ->m
2c62068ac86bdd917a12eef49ba82ec8b091208b x509: Separately calculate sha256 for blacklist
fbfeca74043777b48add294089cd4c4f68ed3377 lib/crypto: aes: Drop 'volatile' from aes_sbox and aes_inv_sbox
9ddfabcc1ed884ef47bcca317e77596c797bef83 lib/crypto: sha1: Remove low-level functions from API
5023479627e3e85a97807f612bea2eddbf202e1d ipv6: Switch to higher-level SHA-1 functions
20d6f07004d639967dcb00994d56ce6d16118e9e lib/crypto: tests: Add a .kunitconfig file
4478e8eeb87120c11e90041864c2233238b2155a lib/crypto: tests: Depend on library options rather than selecting them
beeebffc807531f69445356180238500f56951cc lib/crypto: powerpc/aes: Fix rndkey_from_vsx() on big endian CPUs
ffd42b6d0420c4be97cc28fd1bb5f4c29e286e98 lib/crypto: mldsa: Clarify the documentation for mldsa_verify() slightly
This is my checkout of Linus's checkout:
https://codeberg.org/cosmicexplorer/linux/src/branch/master
This is Linus's checkout:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/
c369299895a591d96745d6492d4888259b004a9e
In particular, there was:
- ML-DSA module signing added with this openly broken config section:
config PKCS7_WAIVE_AUTHATTRS_REJECTION_FOR_MLDSA
+ bool "Waive rejection of authenticatedAttributes for ML-DSA"
+ depends on PKCS7_MESSAGE_PARSER
+ depends on CRYPTO_MLDSA
+ help
+ Due to use of CMS_NOATTR with ML-DSA not being supported in
+ OpenSSL < 4.0 (and thus any released version), enabling this
+ allows authenticatedAttributes to be used with ML-DSA for
+ module signing. Use of authenticatedAttributes in this
+ context is normally rejected.
- wide-ranging changes to cryptographic APIs (I was under the impression `include/crypto/public_key.h` is shared with dependents such as coreutils)
- finally, there is this new directory `scripts/livepatch`, with two files of significance:
1. fix-patch-lines, which pretty openly states that its goal is to create patch files that work after nontrivial modifications
2. klp-build, which will modify and update the kernel configuration so that it the above is not exposed.
I had been looking to type a more general document at some length and continued to find further and further issues and thought this might at least be sufficient for your purposes. I will note that david howells in particular had performed a hard reset of some variety on his fork last night, and lwn had multiple articles online over the weekend which mentioned his name:
https://lwn.net/Articles/1012946/
https://lwn.net/Articles/525592/
I do apologize for introducing this and would like to contribute and to learn from your team further under better circumstances. I happened to be working on packaging coreutils in the spack package manager (where it is already packaged, but not quite as nicely as it could be), and I was relieved to no end to hear that coreutils checksumming remains distinct from the torrent of real harm that linux users will likely face.
binutils was also mentioned in an faddr2line script but not in the way a library dependency might be concerned about.
Thanks, and sorry,
d@nny
@barubary and here's what i sent to coreutils about the backdoor in linux crypto/
Hello coreutils,
I was hoping to open a discussion about implementing the BLAKE3 algorithm, the project's understanding of length extension attacks, and how an archive format might be able to take advantage of features of tree hashes of this variety in concert with an implementation such as coreutils.
I would love nothing more than to engage in this, but I happened to be made aware of a new section in the kernel config through what seems to have been "luck" on Friday and a lot of facially broken changes are being added at an incredible clip.
So that you can quickly determine if I am wasting your time: if you have a local checkout, the following abbreviated refs modify what I believe to be precisely an area coreutils builds using the `--with-linux-crypto` configure script would subsequently become affected by. These are from two engineers, one David Howells from Red Hat / IBM, and Eric Biggers of Google.
965e9a2cf23b066d8bdeb690dff9cd7089c5f667 pkcs7: Change a pr_warn() to pr_warn_once()
91db696adea4d76017b1e1f45915a5cbf04e8da3 pkcs7: Allow authenticatedAttributes for ML-DSA
0ad9a71933e73c8a2af101d28e9a1dc35bae02d5 modsign: Enable ML-DSA module signing
8bbdeb7a25b4cd3d829136a2e12982b8ee7d7991 pkcs7, x509: Add ML-DSA support
f3eccecd782dbaf33d5ad0d1fd22ea277300acdb pkcs7: Allow the signing algo to do whatever digestion it wants itself
f728074f1f577565c97e465652c3d4afb0964013 pkcs7, x509: Rename ->digest to ->m
2c62068ac86bdd917a12eef49ba82ec8b091208b x509: Separately calculate sha256 for blacklist
fbfeca74043777b48add294089cd4c4f68ed3377 lib/crypto: aes: Drop 'volatile' from aes_sbox and aes_inv_sbox
9ddfabcc1ed884ef47bcca317e77596c797bef83 lib/crypto: sha1: Remove low-level functions from API
5023479627e3e85a97807f612bea2eddbf202e1d ipv6: Switch to higher-level SHA-1 functions
20d6f07004d639967dcb00994d56ce6d16118e9e lib/crypto: tests: Add a .kunitconfig file
4478e8eeb87120c11e90041864c2233238b2155a lib/crypto: tests: Depend on library options rather than selecting them
beeebffc807531f69445356180238500f56951cc lib/crypto: powerpc/aes: Fix rndkey_from_vsx() on big endian CPUs
ffd42b6d0420c4be97cc28fd1bb5f4c29e286e98 lib/crypto: mldsa: Clarify the documentation for mldsa_verify() slightly
This is my checkout of Linus's checkout:
https://codeberg.org/cosmicexplorer/linux/src/branch/master
This is Linus's checkout:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/
c369299895a591d96745d6492d4888259b004a9e
In particular, there was:
- ML-DSA module signing added with this openly broken config section:
config PKCS7_WAIVE_AUTHATTRS_REJECTION_FOR_MLDSA
+ bool "Waive rejection of authenticatedAttributes for ML-DSA"
+ depends on PKCS7_MESSAGE_PARSER
+ depends on CRYPTO_MLDSA
+ help
+ Due to use of CMS_NOATTR with ML-DSA not being supported in
+ OpenSSL < 4.0 (and thus any released version), enabling this
+ allows authenticatedAttributes to be used with ML-DSA for
+ module signing. Use of authenticatedAttributes in this
+ context is normally rejected.
- wide-ranging changes to cryptographic APIs (I was under the impression `include/crypto/public_key.h` is shared with dependents such as coreutils)
- finally, there is this new directory `scripts/livepatch`, with two files of significance:
1. fix-patch-lines, which pretty openly states that its goal is to create patch files that work after nontrivial modifications
2. klp-build, which will modify and update the kernel configuration so that it the above is not exposed.
I had been looking to type a more general document at some length and continued to find further and further issues and thought this might at least be sufficient for your purposes. I will note that david howells in particular had performed a hard reset of some variety on his fork last night, and lwn had multiple articles online over the weekend which mentioned his name:
https://lwn.net/Articles/1012946/
https://lwn.net/Articles/525592/
I do apologize for introducing this and would like to contribute and to learn from your team further under better circumstances. I happened to be working on packaging coreutils in the spack package manager (where it is already packaged, but not quite as nicely as it could be), and I was relieved to no end to hear that coreutils checksumming remains distinct from the torrent of real harm that linux users will likely face.
binutils was also mentioned in an faddr2line script but not in the way a library dependency might be concerned about.
Thanks, and sorry,
d@nny
@barubary i have so many more vulns from march
Tails up!
Okay, *bonus* slug of rye: I totally did *not* respond to that community email about using NVC to resolve a conflict.
I am like a bright star, shooting across the night sky of conversational restraint.
Hit me.
@GeePawHill You don't like NVC?
(Like many things, I studied it and totally failed to master it. I still occasionally use some of the tools though.)