@davidaugust@mastodon.online2025-11-24 16:09:07
“‘We had to destroy the village to save it’ is not a new American rationalization, and the imperial boomerang can and will, if we don’t stop it, bring it to bear on the American populace.”
https://stuff.davidaugust.com/local-law-enforceme…
@pre@boing.world2025-11-23 12:15:10
Not sure what the difference between a panel and a"fireside chat" is. There is no fire.
But here's a fireside chat on what nostr is.
Nostr is freedom for Identity. Accounts without hosts. Publishing without publidhers. Censorship resistance without platforms deciding who gets to say what.
It's not a silo in which you can be tapped as the service enshitifies, since it's a protocol with accounts you control, you can't switch clients or relays without loosing social graph or contacts.
Nostr is notes and Other Stuff, what other stuff? the panel is working on an audiobook publishing system with perhaps a required payment and affiliate revenue share. E-commerce, video publishing, zap stream for live video with zap payments.
Onboarding can be tricky with private key management needing to be understood and such a range of options of clients and what relays are. Can we make it easier?
Perhaps by abstracting away the fact it's nostr at all. Devine users don't even know they are using nostr. But this robs users of the understanding they may need to move clients or use the same account for video and notes, say.
Perhaps by making a private messagnger, the panel thinks people are used to using multiple messenger apps. Though I find they hate that, and that's why they refuse to install signal. They feel they don't need it since they already have WhatsApp with a bigger network.
In the end it's education. We have to teach literacy so people can read and write, we have to teach public keys encryption so people can do so securely.
#bitfest #nostr
@mgorny@social.treehouse.systems2025-12-23 13:11:20
I'm building webkit-gtk right now. It's one of these messy packages where a few source files need a lot of memory to compile, and ninja can randomly order jobs so that all of them suddenly start compiling simultaneously. So to keep things going smoothly without OOM-ing, I've been dynamically adjusting the available job count via steve the #jobserver.
While doing that, I've noticed that ninja isn't taking new jobs immediately after I increased the job count. So I've started debugging steve, and couldn't find out anything wrong with it. Finally, I've looked into ninja and realized how lazy their code is.
So, there are two main approaches to acquiring job tokens. Either you do blocking reads, and therefore wait for a token to become available, or you use polling to get noticed when it becomes available. Ninja instead does non-blocking reads, and if there are no more tokens available… it waits till one of its own jobs finish.
This roughly means that as other processes release tokens, ninja won't take them until one of its own jobs finish. And if ninja didn't manage to acquire any job tokens to begin with, it is just running a single process via implicit slot, and that process finishing provides it with the only chance to acquire additional tokens. So realistically speaking, as long as there are other build jobs running in parallel, ninja is going to need to be incredibly lucky to ever get a job token, since all other processes will grab the available tokens immediately.
This isn't something that steve can fix.
#Gentoo #NinjaBuild
@aral@mastodon.ar.al2025-11-25 07:26:43
It was ten years ago that the person in charge of protecting kids online in Europe was telling to me apologise to Lord whateverhisnameis from Facebook for saying they shouldn’t be in schools. (Spoiler alert: they were informed in no uncertain terms exactly where they could stuff their not-forthcoming apology.)
https://
@cdarwin@c.im2026-01-23 13:05:57
“They took her, they took her, they took her.”
Those were some of the words Cora Muñoz, the Wilbur Cross high school assistant principal, could discern while on the phone with the guardian of one of her students.
As the caller sobbed and struggled to speak, Muñoz realized that immigration enforcement agents had detained a kid from Wilbur Cross, the high school she helps lead.
Again.
There was a reason why Muñoz was a go-to contact for the student and her guardian:
@Techmeme@techhub.social2026-01-24 06:55:51
Memo: TikTok CEO Shou Chew hailed the establishment of the TikTok USDS JV as "great news", and said the app is used by 200M US users and 7.5M US businesses (Dan Whateley/Business Insider)
https://www.businessinsider.com/read-tiktok-ceo-memo-cl…
@pavelasamsonov@mastodon.social2025-11-24 14:54:33
When a user doesn't understand your product, they can't use it. But when the team doesn't understand their own product, then NO ONE can.
We neglected the conceptual layer of software development, and products have devolved from a coherent experience into Proper Noun soup. To unwind this self-inflicted problem, we must stop "optimizing" for just one part of the job.
Here's how.
(this is a much deeper problem than "just UX vs UI")
@timbray@cosocial.ca2025-12-23 22:27:51
Running pre-Christmas errands, a relative who likes cannabis wanted to stop at the dispo. I strolled in too, and at the checkout counter I noticed a sign about Tuesdays. Couldn’t resist, told the relative to consider this part of their Christmas present and pulled out my credit card.
Just so I could say I got the Senior Citizens discount on a bag of weed.
Best of the season to everyone.
@cdarwin@c.im2025-11-23 17:24:49
In the US, men who smoke are around 21 times more likely to die from lung cancer than men who have never smoked.
But the damage doesn’t stop there:
smoking also increases the risk of other cancers,
including mouth, throat, bladder and pancreatic cancer,
in addition to other health conditions such as chronic obstructive pulmonary disease (COPD),
heart disease, and diabetes.
Why does one habit harm so many organs?
Cigarettes carry a mixture of carcinoge…
@pre@boing.world2025-11-23 16:11:28
Thomas voegtlin talks about nostr spam. It's very censorship resistance means spam can't be stopped by moderators.
One way to stop spam is require proof of work before your client accepts a message. A large difficult hash.
But big hashing machines are more available to spammers than people.
Can't use likes or zaps cuz they can be faked with sybil attacks.
Instead: notaries and proveably burned satoshis.
Your public messages are classified as ham rather than spam if you burn enough money.
Nostr event types to prove it are suggested. Including burning to upvote others messages
Don't think I like deliberately burning the money, and seems to me a web of trust might work without doing that? Pay to post also peanizes there poor.
But it isn't really burned here, it's shaed out to miners to continue a subsidy when the block rewards run out. So paying miners and these notaries rather than really burning. Okay. Maybe better, but still makes messages mostly for the rich?
#bitfest #bitcoin #nostr
