Biomedical Engineering, Medicine, Public Health, Open Source, Structural Solutions
16137 stories
·
228 followers

A 1973 Fiat Pickup Truck

1 Comment

Have you ever wondered what an Italian pickup truck would look like? Well, here's your answer:

It's even got a sunroof:

Apparently in the 20th century, a handful of Italian motorists with quirky tastes hired coachbuilders to convert their Fiat 500s into pickup trucks. This example, first commissioned in 1973, was recently restored by French company Parfait Etat.

Check out the speedometer:

I imagine it was used as an ultra-efficient fish hauler. And that's not a dig; if I had an opportunity to own one of these, I'd snap it up and find some fish to haul.




Read the whole story
satadru
28 minutes ago
reply
OMFG.
New York, NY
Share this story
Delete

SF Democratic Party loves Flock:

jwz
1 Comment
The SF Democratic Party [sic] voted on Wednesday to continue its support for Flock surveillance cameras:

Two major resolutions were in front of the party's 31 members -- 13 of whom were absent -- on Wednesday. One, written by former District 4 supervisor Gordon Mar, called for the city to impose increased guardrails for Flock's automated license-plate readers, and to consider suspension of its contract with the city.

The other, written by committee chair Nancy Tung and District 6 supervisor and former police spokesperson Matt Dorsey, asked the group to affirm its trust in the city's existing use of Flock cameras. [...]

At Wednesday's San Francisco Democratic County Central Committee meeting, a majority voted to reject Mar's resolution and pass Dorsey's. Dorsey's measure received 11 votes in favor, 4 votes abstaining, and only 3 against. [...]

Both sides acknowledged that the city's Flock camera data was illegally accessed more than 1.6 million times in 2024 and 2025, with lots of those searches reaching out-of-state agencies like Immigration and Customs Enforcement. And, more recently, the San Francisco Police Department admitted around 300 out-of-state illegal searches had happened in the last year. [...]

Mar raised another concern: Two of the committee's current members -- Lily Ho and Trevor Chandler -- work for Flock. Last month, the San Francisco Standard reported that a prior version of Mar's resolution was removed from the party's agenda by a subcommittee chaired by Ho.

Neither Ho nor Chandler offered to abstain from voting on Wednesday. The committee does not have rules related to conflicts of interest for issues like this one, Tung told Mar. They then proceeded to count both Ho and Chandler's votes.

Previously, previously, previously, previously, previously.

Read the whole story
satadru
34 minutes ago
reply
Lol...
New York, NY
Share this story
Delete

It's not illegal if you buy new laws

jwz
2 Shares
Lyft has to pay out $272 million for the fraud they perpetrated on their employees from 2016 through 2020!

But then in 2020, they spent $200 million to make that fraud legal, so now they won't have to pay that again in the future!

According to methane-breathing money-ghouls who run our world, this was a great investment: they could have just spent an additional $50M/year on salaries, but now they legalized an across-the-board salary reduction that pays itself back in only 4 years. Half that, actually, because they went halfsies on it with Uber! Someone's getting a raise.

This goes way beyond "a fine is a price".

Lyft is set to pay a historic $272.5 million settlement to resolve allegations around misclassifying its drivers as independent contractors instead of employees:

("allegations")

San Francisco City Attorney David Chiu said it was "the largest wage-and-hour settlement in California history." [...]

That's a time before voters approved Proposition 22, an Uber- and Lyft-funded ballot measure that classified ride-hail drivers as independent contractors, meaning they would not receive the benefits and wage protections afforded to other workers. The gig companies spent more than $200 million on the measure.

Previously, previously, previously, previously, previously, previously, previously, previously, previously, previously, previously, previously, previously, previously, previously, previously, previously.

Read the whole story
satadru
34 minutes ago
reply
New York, NY
acdha
5 hours ago
reply
Washington, DC
Share this story
Delete

Social Media Bans Aren’t Enough to Make Children Safe

1 Comment


Even before France approved legislation banning social media for children under 15 last January, 13-year-old Benjamin was already wondering what life without social media would look like. “If we want to play football, we won’t be able to organize it. What will we do? Send letters instead?” he joked in an interview for Le Monde.

His reaction captured the central challenge behind the growing wave of youth social media bans: Removing access is one thing; understanding what those platforms mean in children’s lives is another.

Within weeks of Australia’s similar ban, the country’s eSafety Commissioner reported that platforms had restricted access to 4.7 million under-16 accounts. Two months later, though, one in five Australian teenagers under 16 was still using TikTok and Snapchat, according to a parental-control data company. But even if all children’s social media accounts were to disappear, do such bans actually make children safer online?

Governments are moving ahead without answering that question as they follow Australia’s lead. Indonesia’s child-safety framework, which took effect in March, bars children under 16 from holding accounts on “high-risk” platforms. The U.K. government has announced plans to ban social media for under-16s, add default overnight social media curfews for 16- and 17-year-olds, and extend child-safety rules to cover risky AI features. And on 17 September, the European Commission proposed the EU KIDS Act, which would bar children under 13 from social media, set 15 as the EU-wide minimum age for opening an account independently, and require platforms to show that their services are age appropriate and safe by design.

But based on my experience working on Child Online Protection initiatives with the International Telecommunication Union (ITU) across Southeast Asia and the Pacific, I know the bans don’t address the real problems. Instead, we should be paying more attention to the systems that generate harm in the first place—namely, recommender algorithms, engagement-maximizing design, opaque moderation, and extractive data practices.

Account removals are not the same as online child safety

My experience working on protecting children’s online safety has taught me three main lessons:

First, the public institutions responsible for child online protection often lack the staff, budget, or technical capacity to enforce complex online safety policies.

Indonesia is illustrative. A 2026 UNICEF evaluation found capacity constraints among service providers, long-term funding uncertainty, and a need for specialized personnel. At the local level, some staff lacked digital skills, while budget constraints left some areas reliant on external support.

Second, many children, and often their parents, lack the digital literacy and critical thinking skills needed to navigate online risks safely. My policy research on child online protection in Indonesia, published earlier this year in Digital Society, found substantial gaps that account removals cannot repair: Many children lacked guidance on navigating the internet safely, and large numbers did not know how to report harmful experiences.

And third, the platforms have limited independent oversight as they identify underage users, design age-verification systems, and report their own compliance. In Indonesia, platforms themselves are responsible for carrying out age verification, while the Ministry of Communication and Digital Affairs oversees compliance. TikTok’s appeals process for users flagged as underage, for instance, can require a government-issued ID and selfies, which is a problem because it involves collecting the additional personal data on an ID card, beyond that needed to confirm age. Will government regulators ensure that TikTok handles that data responsibly?

The privacy paradox of proving age

Every age-based ban creates an engineering problem: How can a platform reliably determine that a user is old enough, without intruding on other information? Governments and companies may use identity documents, parental authorization, app-store checks, or facial age estimation. Each approach has trade-offs among accuracy, privacy, accessibility, and resistance to circumvention.

There are also technical issues. One tool, facial age estimation, draws on enormous databases but it is probabilistic, not exact, because people vary so much. It’s also been shown to misclassify both children and adults.

The challenge should not merely be to “verify age.” It should be to prove that someone is above a threshold, without disclosing their identity, birth date, or other information third parties might use to create a marketing profile. The European Commission’s age-verification blueprint challenges companies to verify ages without collecting all that additional information.

Privacy-preserving technologies offer promising ways to achieve this. Zero-Knowledge Proofs (ZKPs) can confirm that someone meets an age threshold without revealing their identity or exact date of birth. W3C Verifiable Credentials are cryptographically verifiable digital claims that can disclose only the information needed, such as “over 16.” And device-based age signals can allow a phone or app store to share an age range without revealing a user’s exact birth date. But these methods still require rigorous security testing, common standards, independent oversight, and clear limits on data retention. Otherwise, poorly designed child-safety policies risk creating permanent identity infrastructures in which businesses, not people, control personal data.

Where connection goes when a platform closes

Blocking access to a platform redirects some young people, but not always where expected. Early anecdotal reports in Australia pointed to teenagers migrating to smaller, less-regulated platforms like Yope, a pattern the Cato Institute flagged as a “whack-a-mole” problem for regulators. But industry data collected two months later found no broad-based shift of that kind, aside from a small uptick in WhatsApp use. Many teens simply found a way to stay on the banned platforms.

This points to a deeper gap in current society: the erosion of youth “third places“ physical spaces where young people have room to socialize and build identity outside home and school. As those spaces have diminished, commercial communications platforms have absorbed that role.

For many teenagers, social media workarounds are merely inconvenient. But for isolated, marginalized, disabled, or LGBTQ+ youth who depend on online communities for support that’s otherwise unavailable, displacement can mean losing certain kinds of belonging, or having to move to a platform with even weaker oversight.

How to design safer online systems for children

If blanket social media bans don’t work, then what will? The platforms have created many of the conditions that governments are now trying to contain: engagement-optimized recommenders, intrusive data practices, weak safeguards against unwanted contact, and features such as infinite scroll, autoplay, streaks, and persistent notifications.

These design patterns increasingly face regulatory scrutiny, including what’s required under the European Union’s Digital Services Act. A 2026 study from the 5Rights Foundation that tracked children’s device use minute by minute found that the user interfaces shape children’s attention, sleep, and well-being in real time.

A more durable response would regulate those interfaces directly, treating children as legitimate users whose privacy, agency, and well-being are required protections, not afterthoughts. That means designing for safety from the outset. One example would be for children’s apps to have high-privacy defaults, such as private accounts and location sharing switched off for minors. They could also have recommender systems that explain the main factors shaping a feed and give young users more control over personalization. The European Commission has published age-appropriate interaction guidelines that limit unsolicited contact and prevent minors from being added to groups without consent. Rules could also prohibit engagement-maximizing features that demand users’ attention, such as autoplay, infinite scroll, usage streaks, read receipts, and push notifications, by disabling or limiting them by default.

Governments should define measurable outcomes and fund independent evaluation, platforms should give researchers meaningful data access, and engineers should audit age-assurance systems for bias and data leakage. Schools, parents, and children themselves need a seat in designing the technology that’s designed to protect children.

If policymakers still decide to remove an infrastructure for youth connection, they should offer something better in return. Social media bans may reduce some forms of exposure to harmful content and may be justified for particular ages, services, or risks. But they are just one tool, not a comprehensive substitute for safer design, accountable platforms, digital literacy, institutional capacity, and noncommercial digital “third places”—moderated communities, creative spaces, and public-interest platforms designed for youth participation rather than profit.

The first wave of social media restrictions isn’t enough to keep children safe. Governments are still measuring what’s easiest to count, while neglecting harder-to-measure outcomes such as children’s access to safe third places and meaningful social connection, both online and offline. Until governments can show evidence that harm has actually declined, they will keep mistaking account removal for safety.

Read the whole story
satadru
6 days ago
reply
This was a great synopsis of the issue.
New York, NY
Share this story
Delete

First version of Word for Windows ported to modern 64bit Windows

1 Comment

Back in 2014, Microsoft released the source code to the first Windows version of Word, version 1.1a. Now, Justin Marshall has ported this code to modern versions of Windows, so you can run it as if it were any other modern application.

This project is a fully working native Windows x64 port of Microsoft Word for Windows 1.1a, whose historical codename was Opus. It builds the original Word source and resources together with modern replacements for the 16-bit assembly, segmented-memory, and Win16 platform boundaries.

The result is the original Word application and user experience running as a 64-bit Windows executable. This is not an emulator or a reimplementation using a modern editor control.

↫ Justin Marshall

Neat endeavour.

Read the whole story
satadru
34 days ago
reply
I would love to see the classic mac version of Word 5.1a ported to, well, anything...
New York, NY
Share this story
Delete

Google hammers another, extremely petty nail in the Android Open Source Project’s coffin

1 Comment

The slow but steady march to the grave for the Android Open Source Project continues. Every few months Google hammers another big nail in the coffin of Android as an open source effort, and I’ve documented them all here on OSNews (nail, nail, nail, nail, nail), coming to the conclusion long ago that for all intents and purposes, Android is no longer an open source operating system.

The latest move, however, is just petty.

According to GrapheneOS on [Twitter], Google has apparently replaced public, instant code downloads for Pixel phone drivers with a manual request form. Instead of publishing code directly to open developer platforms where anyone can grab it, Google now requires developers to fill out a Google Form and wait for someone to send them a Google Drive link.

What used to take a couple of hours is now taking weeks.

↫ Hillary Keverenge at Android Authority

I’m perhaps misremembering, but I vaguely recall discussions decades ago about what, exactly, it meant to “make source code available”, as open source licenses state in a variety of words. Would mailing a paper print-out by classic post satisfy such requirements? Could you write the source code on a brick and throw it through the user’s window? Could you hire a church choir to sing it? These are all silly examples, but before everyone had internet access, this was a relevant question.

The widespread availability of the internet and software like git solved these issues, which makes it all the more petty that Google now requires an actual application process, waiting times, and Google Drive dumps just to get access to the source code for Pixel drivers. Google is clearly trying to kill whatever’s left of the Android Open Source Project’s rotting corpse, only barely technically complying with any license requirements only because they’re obligated to.

The Android team at Google must be a hoot at parties.

Read the whole story
satadru
34 days ago
reply
I've committed to no longer buying any hardware from Google ...
New York, NY
Share this story
Delete
Next Page of Stories