Reblogged by jsonstein@masto.deoan.org ("Jeff Sonstein"):
dgar@aus.social ("Dgar") wrote:
Reblogged by jsonstein@masto.deoan.org ("Jeff Sonstein"):
dgar@aus.social ("Dgar") wrote:
Reblogged by jsonstein@masto.deoan.org ("Jeff Sonstein"):
wdlindsy@toad.social ("William Lindsey :toad:") wrote:
Greg Sargent talks with Jess McIntosh about the scam Trump is now engaged in, trying to soft-peddle the Republican position on abortion and same-sex marriage to appeal to undecided voters and suburban women — when the voters driving the party, its white Christian nationalist base, have no intention of letting the party soften its positions on these issues.
Reblogged by jsonstein@masto.deoan.org ("Jeff Sonstein"):
futurebird@sauropods.win ("myrmepropagandist") wrote:
I explained to her why I was upset about the beef jerky, but look at her face? Do you think any of it got through?
Is this the face of remorse?
Reblogged by jsonstein@masto.deoan.org ("Jeff Sonstein"):
Mer__edith@mastodon.world ("Meredith Whittaker") wrote:
There’s been some chatter about Signal desktop recently, so let’s clear the air. Three points:
1. The reported issues rely on an attacker already having *full access to your device* — either physically, through a malware compromise, or via a malicious application running on the same device. This is not something that Signal, or any other app, can fully protect against. Nor do we ever claim to.
Reblogged by jsonstein@masto.deoan.org ("Jeff Sonstein"):
toolsontech@pkm.social ("Bas (Tools on Tech) :verified:") wrote:
@Mer__edith After reading "trust me I'm lying" asking for this feels like asking water to not be wet. Anyone that knows security would realize that an exploit that requires full system access isn't really an exploit but non-news. So it feels like emotional click farming, with no regards whatsoever for actual fact checking.
Reblogged by jsonstein@masto.deoan.org ("Jeff Sonstein"):
glennpegden@infosec.exchange ("Glenn Pegden :donor:") wrote:
So if we* organise** a "UK Hackers" meet up at
@Defcon
who might be tempted to turn up?[ Boosts encouraged ]
·
* If you're the kind of person that I normally rely on to enable my daft ideas, that "we" means you :)** It won't be organised. It'll just be a named time and place. Turn up, or don't. No qualifying, or disqualifying requirements. It'll just be a public bar. There will be no food, no plan, no insurance, no CPEs, no expectations.
It's like a super casual flashmob.
Reblogged by jsonstein@masto.deoan.org ("Jeff Sonstein"):
w3c@w3c.social ("World Wide Web Consortium") wrote:
Did you know, our Nu HTML validator checks:
~3 documents every second
~10,000+ documents every hour
~250,000+ documents a day
~2 million documents a week
~8 million documents a month
~100 million documents a year
~1 billion documents over the last 10 years
Reblogged by jsonstein@masto.deoan.org ("Jeff Sonstein"):
it_was_inevitable_slow@botsin.space ("Sentient Dwarf Fortress 🕑") wrote:
I had a drink. I'm very content.
— Minkot Mengngalák, chief medical dwarf
slightlyoff@toot.cafe ("Alex Russell") wrote:
HOW can we change that dynamic? How can we create the sort of pressure that will allow @carlana's hopes to materialise in a reasonable time-frame?
Competition.
*This* is why the work of @owa is so foundational to the future of web development. They are making *enormous* progress on the most important root-cause problem on the web today. Just the *threat* of competition has already upped Apple's pace, and true engine choice will do much more.
slightlyoff@toot.cafe ("Alex Russell") wrote:
So, if you care about the web, either as a developer or as a user, now's the time to go support @owa and get involved with their work.
Now, more than ever, they need friends and allies that can help inform regulators and legislators and (most importantly) the staffs of implementing organisations about how browser engine progress unlocks better outcomes for everyone.
slightlyoff@toot.cafe ("Alex Russell") wrote:
Apple (enabled, sadly, by Mozilla) are now working behind the scenes to keep regulatory scrutiny from "forcing" them to deliver many features that developers are clamoring for in a timely way.
We should not be confused: the things on Carlana's list won't happen any faster than the things we've *already* shipped over objection and delay until the underlying dynamic changes:
slightlyoff@toot.cafe ("Alex Russell") wrote:
What doesn't parse as cleanly is the "view from nowhere" that assumes that browser progress is *vis major* and happens at some natural rate that only needs to be redirected. The reality is much messier, but folks inside the room don't often tell the truth about it for fear of reducing an already depressing slog towards progress:
https://infrequently.org/2023/02/safari-16-4-is-an-admission/#fn-u-turns-1
Apple's unwillingness to engage in V0 design was a major factor behind the Blink fork. Post-fork antipathy toward cooperation followed.
slightlyoff@toot.cafe ("Alex Russell") wrote:
The specific list of items in Carlana's list is constructive and good. I'd add data cascade, SVG extensibility, declarative component definitions, HTML modules, and much else. But the limiting factor on all of these *incredibly* obvious additions is the same as it has been for a decade: Apple's foot-dragging.
Until and unless we contend with the underlying force dragging us down, we will not progress at anything like a useful rate.
slightlyoff@toot.cafe ("Alex Russell") wrote:
First, this sort of focus on what developers are struggling to express is *exactly* what led us to try to build Web Components in the first place. We did a ton of study of what was then the dominant strain of component construction challenge at the time, and did not imagine we'd end up unable to deliver on a reasonable timeline. But things happened; some of the recap is in this talk:
https://youtu.be/y-8Lmg5Gobw?si=UEuOyRoN4RSNc42i
So I'm absolutely on board with the intuitions of this post.
slightlyoff@toot.cafe ("Alex Russell") wrote:
I'd missed this post from late last year by @carlana, and it's good enough that I think it deserves a response:
https://blog.carlana.net/post/2023/web-component-alternative-futures/
(short thread)
collinsworth@hachyderm.io ("Josh Collinsworth") wrote:
I assume it's probably like this for users who have more than one 2FA method, so they can choose between them at that point. But it's a really lousy experience for users who don't.
collinsworth@hachyderm.io ("Josh Collinsworth") wrote:
Pet peeve: 2FA flows where you have to click a button before they send you the 2FA code.
Just send me the code! Don't make me click another button.
fromjason ("fromjason.xyz 🖤") wrote:
There appears to be a lot of paid political ads on #TikTok which is weird because such content is against the app's terms of service.
I think this is the biggest story no ones talking about, so I gathered up all the relevant reporting on the topic and published to my wiki.
slightlyoff@toot.cafe ("Alex Russell") wrote:
This is so much fun; particular props for making everything forkable in codesandbox:
https://dgerrells.com/blog/how-fast-is-javascript-simulating-20-000-000-particles
collinsworth@hachyderm.io ("Josh Collinsworth") wrote:
Nothing makes me feel more like an out-of-touch old man than Discord prompts to unlock stuff.
Sir, this is a chat app. I ain't doing no quests.
Reblogged by nadim@infosec.exchange ("Nadim Kobeissi"):
Hi Meredith, let me address your points:
- The issue we highlighted does not require “full” access to the device. Signal desktop stores the chat database in an unprotected area of the file system that’s accessible by any user process. This would allow any program without any special permissions or user prompts to access the database in full. This can be solved by sandboxing, which relies on the OS to prevent any process from accessing data within the sandbox.
… 🧵 1/4
slightlyoff@toot.cafe ("Alex Russell") wrote:
I'm (finally) catching up on the details of the WPT licensing change from a few years back; this is a good overview of a switch to a license that looks, frankly, sketchy:
Reblogged by cstanhope@social.coop ("Your friendly 'net denizen"):
lmorchard@hackers.town ("Les Orchard") wrote:
Shower thoughts time: Some days I feel like I'm from an alien species. I don't want power. I don't want to compete or win. I don't want attention, recognition, or praise. Any apparent understanding or enactment I have of these things is a clumsy simulation I've been forced into by others.
I want to learn, play, tinker, share, build, and repair in a mutually beneficial world. Maybe make a few connections with folks - but not too many. I want to hang out with animals. And I want everybody to be okay.
There's a scene in Darwin's Children by Greg Bear that I think about a lot, where a character says "It hurts to make others fail". She sounds like my people. Except, in the story, she's the result of a strange genetic mutation. So 🤷♂️
Reblogged by slightlyoff@toot.cafe ("Alex Russell"):
baldur@toot.cafe ("Baldur Bjarnason") wrote:
“Open Source Software: The $9 Trillion Resource Companies Take for Granted - HBS Working Knowledge”
> Many companies build their businesses on open source software
All of them. Not "many". ALL of them are built on Free/Open Source. It's just a question of degree. Pretty much all of software is built on looting the commons.
pzmyers@octodon.social ("pzmyers 🦑") wrote:
Looking young and happy.
https://freethoughtblogs.com/pharyngula/2024/07/09/if-youre-wondering-where-im-at/
slightlyoff@toot.cafe ("Alex Russell") wrote:
TIL: https://pixelambacht.nl/2021/wakamai-fondue-command-line/
Reblogged by jsonstein@masto.deoan.org ("Jeff Sonstein"):
xahteiwi ("Florian Haas") wrote:
Which of the following is an appropriate response to a statement of fact, or to a disprovable hypothesis?
(Boosts OK)
Reblogged by jsonstein@masto.deoan.org ("Jeff Sonstein"):
mike@chinwag.org ("Mike, First of his Name") wrote:
NBD just a successful test of a 2MB RAM expansion for a Commodore 64. Just everyday things.
Reblogged by collinsworth@hachyderm.io ("Josh Collinsworth"):
IanDSmith@mastodonapp.uk ("Ian Smith") wrote:
slightlyoff@toot.cafe ("Alex Russell") wrote:
Hot damn!
https://sfstandard.com/2024/07/01/san-francisco-housing-permit-sb423-development/