jsonstein@masto.deoan.org ("Jeff Sonstein") wrote:

thank you, CAPT Tully… the Union still stands

Attachments:

• a3da1412aeff9534.jpeg (remote)

Reblogged by keul@fosstodon.org ("Luca Fabbri"):

edsu@social.coop ("Ed Summers") wrote:

A good quote to start Kill it With Fire:

Attachments:

• [We build our computer systems the way we build our cities: over time, without a plan, on top of ruins.

 Ellen Ullman][5] ([remote][6])

pzmyers@octodon.social ("pzmyers 🦑") wrote:

The best Halloween spider ever.

https://freethoughtblogs.com/pharyngula/2024/09/24/the-official-spider-of-halloween/

Attachments:

• Vampire spider, Evarcha culicovora (remote)

Reblogged by cstanhope@social.coop ("Your friendly 'net denizen"):

jalefkowit@vmst.io ("Jason Lefkowitz") wrote:

In retrospect, it's kind of crazy that the two biggest developments in CPU technology over the last 20 years were "use much less power, for mobile" and "use much more power, for AI", and Intel managed to miss both of them

cstanhope@social.coop ("Your friendly 'net denizen") wrote:

Also, Adams' version of "War Machine" is worth checking out (the song he recently released). I was unaware he was involved in writing that one.

collinsworth@hachyderm.io ("Josh Collinsworth") wrote:

It just blows my mind that the abbreviation "WP" is explicitly *not* covered by copyright, and yet, Matt Mullenweg still tried to extort millions from WP Engine to "license" it.

He even updated the WordPress license page after the fact to try to throw shade on WPE and make his utterly baseless claim look better (even though *tons* of other businesses and products also use "WP").

Really sucks watching a once-respected figure in open source devolve into a petulant, borderline-criminal man-child.

cstanhope@social.coop ("Your friendly 'net denizen") wrote:

(Lapels are oddly convenient for that sort of dramatic action.)

cstanhope@social.coop ("Your friendly 'net denizen") wrote:

Kim Wilde and Bryan Adams both released new tracks recently. I found out on the same day, and I had an urge to run out into the street and grab the first person I saw by the lapel and say, "Quick! Tell me what decade is this!"

cstanhope@social.coop ("Your friendly 'net denizen") wrote:

Back when I first heard about the effort to get real-time patches upstreamed into the Linux kernel, I initially assumed it was this one:

https://www.yodaiken.com/2024/09/19/rtlinux-retrospective/

I was less interested once I realized the patches going in were more "real-time" than real-time.

Announcing Stable V8 Bindings for Rust

Rusty V8, a library that provides high-quality, zero-overhead Rust bindings to V8, is finally stable. Here's how to use it.

Continue Reading…

fromjason ("fromjason.xyz ❤️ 💻") wrote:

2010's third-wave feminism was a wild ride.

Attachments:

• Feminist Bakes Sourdough Bread Using Her Own Vaginal Yeast

Reblogged by cstanhope@social.coop ("Your friendly 'net denizen"):

mhoye wrote:

Currently listening: https://www.youtube.com/watch?v=tdHhfhLBZLw

Reblogged by kornel ("Kornel"):

Sophie@dice.camp ("Sophie 🎲🧩🏳️‍⚧️") wrote:

Ok so here’s something everyone should be aware of:

Computer mice are facing you.
The wire is the mouse’s tail, right?

That means those things you push down on aren’t buttons,

they’re buttocks.

LMB= Left Mouse Buttock
RMB = Right Mouse Buttock

Reblogged by slightlyoff@toot.cafe ("Alex Russell"):

fox@front-end.social ("karolina") wrote:

a really good piece by @polotek that nails the importance of investing in core web technologies at individual and business level.

i’ve seen epic spends of creating whole rewrite the front end teams. it didn’t solve meaningful issues.

“Companies that want to reduce the cost of their frontend tech becoming obsoleted so often should be looking to get back to fundamentals. Your teams should be working closer to the web platform with a lot less complex abstractions.”

https://polotek.net/posts/the-frontend-treadmill/

Reblogged by collinsworth@hachyderm.io ("Josh Collinsworth"):

fimion@notacult.social ("Alex Riviere") wrote:

Well, based on recent events, I'm gonna start releasing my future open source projects as GPLe, where it's copy-left but I reserve the right to extort you if you sell it better than me.

Reblogged by slightlyoff@toot.cafe ("Alex Russell"):

brucelawson@vivaldi.net ("Bruce Lawson ✅") wrote:

An Abridged History of Safari Showstoppers https://webventures.rejh.nl/blog/2024/history-of-safari-show-stoppers/ - not the mere niggles, but the absolute cesspit explosions. By @rgadellaa, who has seen things you people wouldn't believe; IndexedDBs on fire off the shoulder of Orion. Scrolling bugs glitter in the dark near the Tannhäuser Gate.

Reblogged by fromjason ("fromjason.xyz ❤️ 💻"):

ilovewebsites@social.lol ("I ❤️ Websites Club") wrote:

1991— Tim Berners-Lee, inventor of the World Wide Web, emails some thoughts on what makes for a good website "home page" design.

#OpenWeb #InternetHistory

https://lists.w3.org/Archives/Public/www-talk/1991SepOct/0005.html

xor@tech.intersects.art ("Parker Higgins") wrote:

(pls ignore, testing a #tailscale thing)

WebAssembly targets: change in default target-features

The Rust compiler has recently upgraded to using LLVM 19 and this change accompanies some updates to the default set of target features enabled for WebAssembly targets of the Rust compiler. Beta Rust today, which will become Rust 1.82 on 2024-10-17, reflects all of these changes and can be used for testing.

WebAssembly is an evolving standard where extensions are being added over time through a proposals process. WebAssembly proposals reach maturity, get merged into the specification itself, get implemented in engines, and remain this way for quite some time before producer toolchains (e.g. LLVM) update to enable these sufficiently-mature proposals by default. In LLVM 19 this has happened with the multi-value and reference-types proposals for the LLVM/Rust target features multivalue andreference-types. These are now enabled by default in LLVM and transitively means that it's enabled by default for Rust as well.

WebAssembly targets for Rust now have improved documentation about WebAssembly proposals and their corresponding target features. This post is going to review these changes and go into depth about what's changing in LLVM.

WebAssembly Proposals and Compiler Target Features

WebAssembly proposals are the formal means by which the WebAssembly standard itself is evolved over time. Most proposals need toolchain integration in one form or another, for example new flags in LLVM or the Rust compiler. The-Ctarget-feature=... mechanism is used to implement this today. This is a signal to LLVM and the Rust compiler which WebAssembly proposals are enabled or disabled.

There is a loose coupling between the name of a proposal (often the name of the github repository of the proposal) and the feature name LLVM/Rust use. For example there is the multi-value proposal but a multivaluefeature.

The lifecycle of the implementation of a feature in Rust/LLVM typically looks like:

1. A new WebAssembly proposal is created in a new repository, for example WebAssembly/foo.
2. Eventually Rust/LLVM implement the proposal under -Ctarget-feature=+foo
3. Eventually the upstream proposal is merged into the specification, and WebAssembly/foo becomes an archived repository
4. Rust/LLVM enable the -Ctarget-feature=+foo feature by default but typically retain the ability to disable it as well.

The reference-types and multivalue target features in Rust are at step (4) here now and this post is explaining the consequences of doing so.

Enabling Reference Types by Default

The reference-types proposal to WebAssembly introduced a few new concepts to WebAssembly, notably the externref type which is a host-defined GC resource that WebAssembly cannot access but can pass around. Rust does not have support for the WebAssembly externref type and LLVM 19 does not change that. WebAssembly modules produced from Rust will continue to not use the externref type nor have a means of being able to do so. This may be enabled in the future (e.g. a hypothetical core::arch::wasm32::Externref type or similar), but it will mostly likely only be done on an opt-in basis and will not affect preexisting code by default.

Also included in the reference-types proposal, however, was the ability to have multiple WebAssembly tables in a single module. In the original version of the WebAssembly specification only a single table was allowed and this restriction was relaxed with the reference-types proposal. WebAssembly tables are used by LLVM and Rust to implement indirect function calls. For example function pointers in WebAssembly are actually table indices and indirect function calls are a WebAssembly call_indirect instruction with this table index.

With the reference-types proposal the binary encoding of call_indirectinstructions was updated. Prior to the reference-types proposal call_indirectwas encoded with a fixed zero byte in its instruction (required to be exactly 0x00). This fixed zero byte was relaxed to a 32-bit LEB to indicate which table the call_indirect instruction was using. For those unfamiliar LEB is a way of encoding multi-byte integers in a smaller number of bytes for smaller integers. For example the 32-bit integer 0 can be encoded as 0x00 with aLEB. LEBs are flexible to additionally allow "overlong" encodings so the integer 0 can additionally be encoded as 0x80 0x00.

LLVM's support of separate compilation of source code to a WebAssembly binary means that when an object file is emitted it does not know the final index of the table that is going to be used in the final binary. Before reference-types there was only one option, table 0, so 0x00 was always used when encodingcall_indirect instructions. After reference-types, however, LLVM will emit an over-long LEB of the form 0x80 0x80 0x80 0x80 0x00 which is the maximal length of a 32-bit LEB. This LEB is then filled in by the linker with a relocation to the actual table index that is used by the final module.

When putting all of this together, it means that with LLVM 19, which has the reference-types feature enabled by default, any WebAssembly module with an indirect function call (which is almost always the case for Rust code) will produce a WebAssembly binary that cannot be decoded by engines and tooling that do not support the reference-types proposal. It is expected that this change will have a low impact due to the age of the reference-types proposal and breadth of implementation in engines. Given the multitude of WebAssembly engines, however, it's recommended that any WebAssembly users test out Rust 1.82 beta and see if the produced module still runs on their engine of choice.

LLVM, Rust, and Multiple Tables

One interesting point worth mentioning is that despite the reference-types proposal enabling multiple tables in WebAssembly modules this is not actually taken advantage of at this time by either LLVM or Rust. WebAssembly modules emitted will still have at most one table of functions. This means that the over-long 5-byte encoding of index 0 as 0x80 0x80 0x80 0x80 0x00 is not actually necessary at this time. LLD, LLVM's linker for WebAssembly, wants to process all LEB relocations in a similar manner which currently forces this 5-byte encoding of zero. For example when a function calls another function thecall instruction encodes the target function index as a 5-byte LEB which is filled in by the linker. There is quite often more than one function so the 5-byte encoding enables all possible function indices to be encoded.

In the future LLVM might start using multiple tables as well. For example LLVM may have a mode in the future where there's a table-per-function type instead of a single heterogenous table. This can enable engines to implementcall_indirect more efficiently. This is not implemented at this time, however.

For users who want a minimally-sized WebAssembly module (e.g. if you're in a web context and sending bytes over the wire) it's recommended to use an optimization tool such as wasm-opt to shrink the size of the output of LLVM. Even before this change with reference-types it's recommended to do this as wasm-opt can typically optimize LLVM's default output even further. When optimizing a module through wasm-opt these 5-byte encodings of index 0 are all shrunk to a single byte.

Enabling Multi-Value by Default

The second feature enabled by default in LLVM 19 is multivalue. Themulti-value proposal to WebAssembly enables functions to have more than one return value for example. WebAssembly instructions are additionally allowed to have more than one return value as well. This proposal is one of the first to get merged into the WebAssembly specification after the original MVP and has been implemented in many engines for quite some time.

The consequences of enabling this feature by default in LLVM are more minor for Rust, however, than enabling the reference-types feature by default. LLVM's default C ABI for WebAssembly code is not changing even when multivalue is enabled. Additionally Rust's extern "C" ABI for WebAssembly is not changing either and continues to match LLVM's (or strives to, differences to LLVM are considered bugs to fix). Despite this though the change has the possibility of still affecting Rust users.

Rust for some time has supported an extern "wasm" ABI on Nightly which was an experimental means of exposing the ability of defining a function in Rust which returned multiple values (e.g. used the multi-value proposal). Due to infrastructural changes and refactorings in LLVM itself this feature of Rust hasbeen removed and is no longer supported on Nightly at all. As a result there is no longer any possible method of writing a function in Rust that returns multiple values at the WebAssembly function type level.

In summary this change is expected to not affect any Rust code in the wild unless you were using the Nightly feature of extern "wasm" in which case you'll be forced to drop support for that and use extern "C" instead. Supporting WebAssembly multi-return functions in Rust is a broader topic than this post can cover, but at this time it's an area that's ripe for contribution from suitably motivated contributors.

Aside: ABI Stability and WebAssembly

While on the topic of ABIs and the multivalue feature it's perhaps worth also going over a bit what ABIs mean for WebAssembly. The current definition of the extern "C" ABI for WebAssembly is documented in the tool-conventions repositoryand this is what Clang implements for C code as well. LLVM implements enough support for lowering to WebAssembly as well to support all of this. The extern "Rust ABI is not stable on WebAssembly, as is the case for all Rust targets, and is subject to change over time. There is no reference documentation at this time for what extern "Rust" is on WebAssembly.

The extern "C" ABI, what C code uses by default as well, is difficult to change because stability is often required across different compiler versions. For example WebAssembly code compiled with LLVM 18 might be expected to work with code compiled by LLVM 20. This means that changing the ABI is a daunting task that requires version fields, explicit markers, etc, to help prevent mismatches.

The extern "Rust" ABI, however, is subject to change over time. A great example of this could be that when the multivalue feature is enabled theextern "Rust" ABI could be redefined to use the multiple-return-values that WebAssembly would then support. This would enable much more efficient returns of values larger than 64-bits. Implementing this would require support in LLVM though which is not currently present.

This all means that actually using multiple-returns in functions, or the WebAssembly feature that the multivalue enables, is still out on the horizon and not implemented. First LLVM will need to implement complete lowering support to generate WebAssembly functions with multiple returns, and then extern "Rust" can be change to use this when fully supported. In the yet-further-still future C code might be able to change, but that will take quite some time due to its cross-version-compatibility story.

Enabling Future Proposals to WebAssembly

This is not the first time that a WebAssembly proposal has gone from off-by-default to on-by-default in LLVM, nor will it be the last. For example LLVM already enables the sign-extension proposal by default which MVP WebAssembly did not have. It's expected that in the not-too-distant future thenontrapping-fp-to-intproposal will likely be enabled by default. These changes are currently not made with strict criteria in mind (e.g. N engines must have this implemented for M years), and there may be breakage that happens.

If you're using a WebAssembly engine that does not support the modules emitted by Rust 1.82 beta and LLVM 19 then your options are:

• Try seeing if the engine you're using has any updates available to it. You might be using an older version which didn't support a feature but a newer version supports the feature.
• Open an issue to raise awareness that a change is causing breakage. This could either be done on your engine's repository, the Rust repository, or the WebAssemblytool-conventionsrepository. It's recommended to first search to confirm there isn't already an open issue though.
• Recompile your code with features disabled, more on this in the next section.

The general assumption behind enabling new features by default is that it's a relatively hassle-free operation for end users while bringing performance benefits for everyone (e.g. nontrapping-fp-to-int will make float-to-int conversions more optimal). If updates end up causing hassle it's best to flag that early on so rollout plans can be adjusted if needed.

Disabling on-by-default WebAssembly proposals

For a variety of reasons you might be motivated to disable on-by-default WebAssembly features: for example maybe your engine is difficult to update or doesn't support a new feature. Disabling on-by-default features is unfortunately not the easiest task. It is notably not sufficient to use-Ctarget-features=-sign-ext to disable a feature for just your own project's compilation because the Rust standard library, shipped in precompiled form, is still compiled with the feature enabled.

To disable on-by-default WebAssembly proposal it's required that you use Cargo's-Zbuild-stdfeature. For example:

$ export RUSTFLAGS=-Ctarget-cpu=mvp
$ cargo +nightly build -Zbuild-std=panic_abort,std --target wasm32-unknown-unknown

This will recompiled the Rust standard library in addition to your own code with the "MVP CPU" which is LLVM's placeholder for all WebAssembly proposals disabled. This will disable sign-ext, reference-types, multi-value, etc.

Continue Reading…

Reblogged by fromjason ("fromjason.xyz ❤️ 💻"):

ilovewebsites@social.lol ("I ❤️ Websites Club") wrote:

🧊 If you're looking for a rabbit hole to fall into tonight, start here.

The Cursed Computer Iceberg Meme is a masterfully curated list of programming-related links that progressively become weirder the further down the iceberg you go.

#openweb

https://suricrasia.online/iceberg/

Reblogged by kornel ("Kornel"):

lucylikeayourface@tech.lgbt ("~/Lucyyy 💙") wrote:

@Dee

Attachments:

• Nintendo DS system menu displaying the message: Generating new private key… Please use stylus to draw an elliptic curve now: (remote)

Reblogged by slightlyoff@toot.cafe ("Alex Russell"):

owa ("Open Web Advocacy") wrote:

The Register: "Apple accused of hoodwinking UK antitrust cops"

Apple claims they aren't being anti-competitive, but there isn't really any plausible deniability for that UI decision, so that might explain why they are trying to pretend it never existed.

https://www.theregister.com/2024/09/05/apple_safari_uk_cma/

Reblogged by jsonstein@masto.deoan.org ("Jeff Sonstein"):

kellyromanych ("KellyAnn Romanych (she/her)") wrote:

We've swung from triple digits, to 10 below average, and now back up into the 90s.

Planting perennials is a lifeline for pollinators.

Today, the rosemary is hosting skippers, metallic green bees, leafcutter bees, and honey bees.

Don't give up on urban #bees and #butterflies

#gardening

Attachments:

• A metallic green sweat bee stands in profile on rosemary blossom. The bee is just about the same size as the bloom. She's all green except for the yellow hairs on legs. Even her beautiful mosaic eye is green.

jsonstein@masto.deoan.org ("Jeff Sonstein") wrote:

“The number of women in Texas who died while pregnant, during labor or soon after childbirth skyrocketed following the state’s 2021 ban on abortion care — far outpacing a slower rise in maternal mortality across the nation, a new investigation of federal public health data finds.

From 2019 to 2022, the rate of maternal mortality cases in Texas rose by 56%, compared with just 11% nationwide during the same time period”

https://www.nbcnews.com/health/womens-health/texas-abortion-ban-deaths-pregnant-women-sb8-analysis-rcna171631

slightlyoff@toot.cafe ("Alex Russell") wrote:

@rgadellaa /cc @pluralistic @owa

jsonstein@masto.deoan.org ("Jeff Sonstein") wrote:

our country has far too many politicians like this

https://www.nytimes.com/2024/09/23/nyregion/anthony-desposito-affair-congress.html?smid=nytcore-ios-share&referringSource=articleShare&ngrp=mnp&pvid=B595F56E-475F-4E31-8F64-F5F07C71FE34

slightlyoff@toot.cafe ("Alex Russell") wrote:

This is an incredibly important piece by @rgadellaa; it digs deep and outlines why the multiplicative effects of an unbelievable litany of showstopping WebKit bugs combines with Apple's prohibition on iOA browser choice to single-handedly destroy an interoperable competitor to the App Store. Every regulator needs to read it:

https://webventures.rejh.nl/blog/2024/history-of-safari-show-stoppers/

Reblogged by cstanhope@social.coop ("Your friendly 'net denizen"):

ParadeGrotesque@mastodon.sdf.org ("Parade du Grotesque 💀") wrote:

Fellow geeks! Question time!

Anyone has got experience with StarLabs Linux laptops? Happy? Unhappy? Would you order again?

See here: https://starlabs.systems

(Boost very much appreciated) 🔁

fromjason ("fromjason.xyz ❤️ 💻") wrote:

I consider curating the web as my real job that my bank account doesn't know about yet.

pzmyers@octodon.social ("pzmyers 🦑") wrote:

They make such a delightful couple.

https://freethoughtblogs.com/pharyngula/2024/09/23/only-a-fool-would-be-fooled-by-jared-taylor/

Attachments:

• Jared Taylor (remote)
• Amy Wax (remote)

Reblogged by cstanhope@social.coop ("Your friendly 'net denizen"):

kenshirriff@oldbytes.space ("Ken Shirriff") wrote:

Ferroelectric RAM (FRAM) is an unusual type of memory. It is fast and can store data for decades without power. I opened up a FRAM chip to reveal the tiny cubes of PZT, the ferroelectric material that holds the bits.

Attachments:

• A closeup of the die of a FRAM chip showing the PZT cubes, transistors, and plates that hold the data. (remote)

cstanhope@social.coop ("Your friendly 'net denizen") wrote:

TFW you look for a song from 2007, go to youtube to find a link to pass to others, see results that say "14 years ago", and you think, "Well, it can't be those. That's too far back." And then you remember.

cstanhope@social.coop ("Your friendly 'net denizen") wrote:

Anyway, after you've exhausted yourself working, perhaps you'll have scraped together enough cash to splurge for a "Staycation":

https://www.youtube.com/watch?v=oc4zXfLe4DY

cstanhope@social.coop ("Your friendly 'net denizen") wrote:

Heard this song on my run this morning from some radio program, or maybe podcast, I've never heard of and isn't listed on the radio station's schedule. Anyway, this song is what got me thinking of songs about work, but it took me a while to track it down based on what little I could remember. Amerie's "Gotta Work":

https://www.youtube.com/watch?v=ZA3n-KUe3j0

(I've listened to the song, but I haven't watched the video. So CW for unknown content that passes YouTube's low bar of available to the general public.)

Reblogged by cstanhope@social.coop ("Your friendly 'net denizen"):

djsundog@toot-lab.reclaim.technology ("DJ Sundog - from the toot-lab") wrote:

Somebody dare us to make this one project

Attachments:

• A photo of two books, covers up, side by side. The book on the left is "Build Your Own Mini FM Transmitter" by libi rose striegl and Lori Emerson. The book on the right is "Run Your Own Mail Server" by Michael W Lucas. (remote)

Reblogged by cstanhope@social.coop ("Your friendly 'net denizen"):

brianbilston@mastodon.online ("Brian Bilston") wrote:

To celebrate the first day of autumn, here’s a poem called ‘The Problem of Writing Poems in the Shape of Deciduous Trees’.

Attachments:

• [The poem has been written in the shape of a deciduous tree with letters (or ‘leaves’) missing from the text]: comm n pr ble whe writin p ems in the shape of decid o s trees is t at once t ere ar ives the fir t sti rings of he new aut mn breeze, he oems will begi to shake hemselves ge tly ntil their letters loos n like leaves, an they d start to float down then [The missing letters from the tree have landed on the last line to form the phrase] turntomushuponthegroun [The final ‘d’ is floating down to complete the phrase.] (remote)

cstanhope@social.coop ("Your friendly 'net denizen") wrote:

Let's go for some genre whiplash. Marie Davidson's "Work It" off her album "Working Class Woman":

https://mariedavidson.bandcamp.com/track/work-it

Reblogged by cstanhope@social.coop ("Your friendly 'net denizen"):

nasa@social.beachcom.org ("NASA") wrote:

Comet Tsuchinshan-ATLAS Approaches https://apod.nasa.gov/apod/ap240923.html #APOD

Attachments:

• dd990f83f1f72110.jpeg (remote)

Reblogged by cstanhope@social.coop ("Your friendly 'net denizen"):

amoroso@fosstodon.org ("Paolo Amoroso") wrote:

These days coding for retro computer system is a recreational and learning activity. But sometimes it's essential for maintaining mission critical legacy software, like in this case of writing a new x86 C compiler for Windows CE.

https://building.enlyze.com/posts/a-new-windows-ce-x86-compiler-in-2024

#WindowsCE #windows #retrocomputing

Reblogged by jsonstein@masto.deoan.org ("Jeff Sonstein"):

analog_cafe@mas.to ("Dmitri ☕️") wrote:

Hey #believeinfilm friends,

The easiest way to start developing film at home is C-41.

Today, I'm publishing my completely rewritten guide for colour-negative film development, it's now better than ever:

https://www.analog.cafe/r/developing-colour-film-as-an-absolute-beginner-n3q4

The guide includes a complete shopping list, and the entire process, from mixing the chemicals to scanning and archiving the film. Plus 10 pro tips.

Dare I say, it may be the best of its kind on the internet!

#filmphotography #analogphotography #photography

Attachments:

• A collage of 3 photos, one of chemicals being poured into Paterson tank, one is of a colour negative (stylized) and one more of hanging film strip (remote)
• A jug of water being filled with dry chemical powder in a bathroom (remote)
• Film chemicals warming in a tub of water (remote)
• Chemicals poured into Paterson development tank (remote)

Reblogged by jsonstein@masto.deoan.org ("Jeff Sonstein"):

gruber ("John Gruber") wrote:

“Halide, a camera app that you downloaded and are at this very moment attempting to use, requires access to the camera in order to capture photographs.”
https://mastodon.social/@sandofsky/113181384256449181

Reblogged by jsonstein@masto.deoan.org ("Jeff Sonstein"):

fsf@hostux.social ("Free Software Foundation") wrote:

Assigning your copyright to the FSF helps defend the GPL and keep software free. Thanks to Kristofer Hjelmtorp, Christopher Floess, and Seyed Sajad Kahani for assigning their copyright to the FSF! #GCC #Emacs More: https://u.fsf.org/3ht #CopyrightAssignments

Reblogged by jsonstein@masto.deoan.org ("Jeff Sonstein"):

TexasObserver@texasobserver.social ("Texas Observer") wrote:

Update: On September 20, 2024, the U.S. Department of Justice announced that David Bloyed, who is identified in this article, had been criminally charged with “threatening to lynch and kill” the district attorney in Nashville, Tennessee.
https://www.texasobserver.org/unmasking-texas-neo-nazis/

#politics #USpol #extremism #news #Nashville #Tennessee

Reblogged by jsonstein@masto.deoan.org ("Jeff Sonstein"):

BleepingComputer@infosec.exchange wrote:

Starting Thursday, Kaspersky deleted its anti-malware software from computers across the United States and replaced it with UltraAV's antivirus solution without warning.

https://www.bleepingcomputer.com/news/security/kaspersky-deletes-itself-installs-ultraav-antivirus-without-warning/

Reblogged by jsonstein@masto.deoan.org ("Jeff Sonstein"):

Yogiomm@toad.social ("Fight Fascism #VoteBlue") wrote:

Eggs Recalled After 65 People Across Nine States Report Getting Sick - Food Network

https://apple.news/AhbSlIYbMSl6RJC7t_g2x-Q

jsonstein@masto.deoan.org ("Jeff Sonstein") wrote:

Today in History: Bruce Springsteen born in Freehold, New Jersey, 1949

jsonstein@masto.deoan.org ("Jeff Sonstein") wrote:

Today in History: US Vice President Nixon denies campaign fund fraud with his "Checkers" speech, 1952

jsonstein@masto.deoan.org ("Jeff Sonstein") wrote:

Today in History: Philippine President Ferdinand Marcos declares martial law, 1972

jsonstein@masto.deoan.org ("Jeff Sonstein") wrote:

Today in History: Euripides born in Salamis, Greece, 480 BC

jsonstein@masto.deoan.org ("Jeff Sonstein") wrote:

Today in History: Augustus (Gaius Octavius) Caesar born in Rome, 63 BC

fromjason ("fromjason.xyz ❤️ 💻") wrote:

A small step forward :) #openweb

https://social.lol/@ilovewebsites/113187840275764919

Reblogged by fromjason ("fromjason.xyz ❤️ 💻"):

ilovewebsites@social.lol ("I ❤️ Websites Club") wrote:

Want to start exploring the great web beyond our algorithms but feel overwhelmed?

Start here.

The I ❤️ Websites Club helps us discover great writers, artists, game masters, and other weirdos with websites, to help you build up your RSS feeds and bookmarks.

We'll get started shortly, so follow us here, now, to stay updated.

Account managed by @fromjason

#openweb #ilovewebsites

Reblogged by slightlyoff@toot.cafe ("Alex Russell"):

rgadellaa ("Roderick Gadellaa") wrote:

🪲 An Abridged History of Safari Showstoppers

TL;DR: iOS Safari is more than an inconvenience for developers, it's the fundamental reason interoperability has been stymied in mobile ecosystems; frequent showstopping bugs, a large patch gap, and lack of competing engines ensures the web is not a credible competitor to native. Here are the receipts to prove it.

10 yrs of Safari showstopper bugs.

🙏 @slightlyoff for help drafting & edits

https://webventures.rejh.nl/blog/2024/history-of-safari-show-stoppers/

fribbledom ("muesli") wrote:

Paralysis by analysis

bcantrill ("Bryan Cantrill") wrote:

RTO or GTFO? Last week, Amazon announced that starting in 2025, all employees will be in a physical office 5 days a week. While putatively to strengthen culture (as "the world's largest startup"), this is proving unpopular with many. Will other companies follow suit? On today's episode, @ahl and I are going to talk about remote work, RTO mandates -- and the physicality of both innovation and organization. Join us and share your perspective, 5p Pacific!

https://discord.gg/QrcKGTTPrF?event=1287787453599584327

collinsworth@hachyderm.io ("Josh Collinsworth") wrote:

My wife and I have been going to the gym together a few times a week for a little over a month now.

I'm reluctant to report the rumors are true: it actually really does help. My mental health and general outlook are both the best they've been in a very long time. I feel completely different than I did a month or two ago.

Not all mental health is related to physical health, but if one suffers when the other's neglected, that might be a good signal to follow.

pzmyers@octodon.social ("pzmyers 🦑") wrote:

I think I'm getting too old for everything. Also, I'm 67 -- shouldn't I have outgrown imposter syndrome by now?

https://freethoughtblogs.com/pharyngula/2024/09/23/weekend-whats-that/

Attachments:

• college students partying (remote)

fromjason ("fromjason.xyz ❤️ 💻") wrote:

Is the answer to every yes-or-no posed on the Internet "no?"

Reblogged by fromjason ("fromjason.xyz ❤️ 💻"):

esther@strangeobject.space ("Esther is looking for a server") wrote:

I have said this several times but it bears repeating now:

A very large portion of the Fediverse values tone over substance. "Politeness" and "civility" over what people are actually saying.

This leads to a constant background noise of just rancid replies that are all phrased in a superficially "nice" tone.

Justified anger and non-diplomatic push-back however is heavily policed and dismissed as "bad habits" brought over from elsewhere.

Unless this fundamentally changes, it will never be a place that's safe for marginalized people who have to stand up for themselves and face a constant stream of condescension, dismissiveness, and outright hostility.

A lot of the time it absolutely does live up to its reputation as a place where middle aged white cis men tell you how your perspective and expertise don't matter, and where you better watch your mouth when talking back to them.

cstanhope@social.coop ("Your friendly 'net denizen") wrote:

"The Legend Of John Henry's Hammer" from Johnny Cash:

https://www.youtube.com/watch?v=Ppa__7ZLAU8

pzmyers@octodon.social ("pzmyers 🦑") wrote:

It's all blasphemy, all the way through. Good.

https://freethoughtblogs.com/pharyngula/2024/09/23/incest-is-a-touchy-subject-for-ken-ham/

Attachments:

• Gutsick Gibbon said the 'god' word (remote)

Reblogged by fromjason ("fromjason.xyz ❤️ 💻"):

remoquete@hachyderm.io ("Fabrizio Ferri-Benedetti") wrote:

There you go. A robots.txt that blocks all known AIs. Hopefully it's not ignored... https://github.com/ai-robots-txt/ai.robots.txt/blob/main/robots.txt

cstanhope@social.coop ("Your friendly 'net denizen") wrote:

Tennessee Ernie Ford's "Sixteen Tons":

https://www.youtube.com/watch?v=B9j91-18Kb4

cstanhope@social.coop ("Your friendly 'net denizen") wrote:

Dolly Parton's classic "9 To 5":

https://www.youtube.com/watch?v=UbxUSsFXYo4

cstanhope@social.coop ("Your friendly 'net denizen") wrote:

It's Monday. Time for some motivating music. "Work to Do" by the Isley Brothers:

https://www.youtube.com/watch?v=w28W4Nh9tJM

fromjason ("fromjason.xyz ❤️ 💻") wrote:

This thought popped into my head after watching a TikTok where a creator posed the question "which nepo baby deserves their fame?" and I immediately said "none."

There is no level of talent deserving of generational opportunity in a system built on exclusion.

And yeah, actually, I'm a blast at parties. Lol

Reblogged by fromjason ("fromjason.xyz ❤️ 💻"):

trochee@dair-community.social ("Jeremy Kahn") wrote:

@fromjason

Yes, and conversely, how many of the fabulously wealthy attribute that wealth to talent rather than luck (often luck in choosing your parents!)

If elon¹-grade talent was enough to make one a billionaire, then half of everyone's high-school class should own private islands

Wealth is not correlated with talent!

¹ dude is _made_ of mid

Reblogged by fromjason ("fromjason.xyz ❤️ 💻"):

paninid@mastodon.world ("Sampath Pāṇini ®") wrote:

@fromjason

"I am, somehow, less interested in the weight and convolutions of Einstein’s brain than in the near certainty that people of equal talent have lived and died in cotton fields and sweatshops.”

- #StephenJayGould

fromjason ("fromjason.xyz ❤️ 💻") wrote:

The older I get the more I realize just how common talent is in the world. Knowing that doesn't make talent any less impressive, just that it makes you appreciate how rare opportunity is.

fromjason ("fromjason.xyz ❤️ 💻") wrote:

The Bitter Lesson:

"We want AI agents that can discover like we can, not which contain what we have discovered. Building in our discoveries only makes it harder to see how the discovering process can be done." http://www.incompleteideas.net/IncIdeas/BitterLesson.html

September Project Goals Update

The Rust project is currently working towards a slate of 26 project goals, with 3 of them designed as Flagship Goals. This post provides selected updates on our progress towards these goals (or, in some cases, lack thereof). The full details for any particular goal are available in its associated tracking issue on the rust-project-goals repository.

Flagship goals

Prepare Rust 2024 Edition (tracked in #117)

The Rust 2024 edition is on track to be stabilized on Nightly by Nov 28 and to reach stable as part of Rust v1.85, to be released Feb 20, 2025.

Over the last month, all the "lang team priority items" have landed and are fully ready for release, including migrations and chapters in the Nightly version of the edition guide:

• Changes to support new impl Trait defaults (#117587, #123432; read more here)
• Changes to support generators (#123904).
• Changes to support stabilizing the "never type (!) (#123748).

Overall:

• 13 items are fully ready for Rust 2024.
• 10 items are fully implemented but still require documentation.
• 6 items still need implementation work.

Keep in mind, there will be items that are currently tracked for the edition that will not make it. That's OK, and we still plan to ship the edition on time and without those items.

Async Rust Parity (tracked in #105)

We are generally on track with our marquee features:

1. Support for async closures is available on Nightly and the lang team arrived at a tentative consensus to keep the existing syntax (written rationale and formal decision are in progress). We issued a call for testing as well which has so far uncovered no issues.
2. Partial support for return-type notation is available on Nightly with the remainder under review.

In addition, dynamic dispatch for async functions and experimental async drop work both made implementation progress. Async WG reorganization has made no progress.

Read the full details on the tracking issue.

Stabilize features needed by Rust for Linux (tracked in #116)

We have stabilized extended offset_of syntax and agreed to stabilize Pointers to Statics in Constants. Credit to @dingxiangfei2009 for driving these forward. 💜

Implementation work proceeds for arbitrary self types v2, derive smart pointer, and sanitizer support.

RFL on Rust CI is implemented but still waiting on documented policy. The first breakage was detected (and fixed) in #129416. This is the mechanism working as intended, although it would also be useful to better define what to do when breakage occurs.

Selected updates

Begin resolving cargo-semver-checks blockers for merging into cargo (tracked in #104)

@obi1kenobi has been working on laying the groundwork to enable manifest linting in their project. They have set up the ability to test how CLI invocations are interpreted internally, and can now snapshot the output of any CLI invocation over a given workspace. They have also designed the expansion of the CLI and the necessary Trustfall schema changes to support manifest linting. As of the latest update, they have a working prototype of manifest querying, which enables SemVer lints such as detecting the accidental removal of features between releases. This work is not blocked on anything, and while there are no immediate opportunities to contribute, they indicate there will be some in future updates.

Expose experimental LLVM features for automatic differentiation and GPU offloading (tracked in #109)

@ZuseZ4 has been focusing on automatic differentiation in Rust, with their first two upstreaming PRs for the rustc frontend and backend merged, and a third PR covering changes to rustc_codegen_llvm currently under review. They are especially proud of getting a detailed LLVM-IR reproducer from a Rust developer for an Enzyme core issue, which will help with debugging. On the GPU side, @ZuseZ4 is taking advantage of recent LLVM updates to rustc that enable more GPU/offloading work. @ZuseZ4 also had a talk about "When unsafe code is slow - Automatic Differentiation in Rust" accepted for the upcoming LLVM dev meeting, where they'll present benchmarks and analysis comparing Rust-Enzyme to the C++ Enzyme frontend.

Extend pubgrub to match cargo's dependency resolution (tracked in #110)

@Eh2406 has achieved the milestone of having the new PubGrub resolver and the existing Cargo resolver accept each other's solutions for all crate versions on crates.io, which involved fixing many bugs related to optional dependencies. Significant progress has also been made in speeding up the resolution process, with over 30% improvements to the average performance of the new resolver, and important changes to allow the existing Cargo resolver to run in parallel. They have also addressed some corner cases where the existing resolver would not accept certain records, and added a check for cyclic dependencies. The latest updates focus on further performance improvements, with the new resolver now taking around 3 hours to process all of crates.io, down from 4.3 hours previously, and a 27% improvement in verifying lock files for non-pathological cases.

Optimizing Clippy & linting

@blyxyas has been working on improving Clippy, the Rust linting tool, with a focus on performance. They have completed a medium-sized objective to use ControlFlow in more places, and have integrated a performance-related issue into their project. A performance-focused PR has also been merged, and they are remaking their benchmarking tool (benchv2) to help with ongoing efforts. The main focus has been on resolving rust-lang/rust#125116, which is now all green after some work. Going forward, they are working on moving the declare_clippy_lint macro to a macro_rules implementation, and have one open proposal-level issue with the performance project label. There are currently no blockers to their work.

Completed goals

The following goals have been completed:

• Implement "merged doctests" to save doctest time

Stalled or orphaned goals

Several goals appear to have stalled or not received updates:

• Associated type position impl trait made significant progress but was not able to reach a stabilizable state before its owner had to scale back their activity. We expect to revisit this in 2025H1.
• Make Rustdoc Search easier to learn has had no updates.
• Use annotate-snippets for rustc diagnostic output has had no updates.

One goal is still waiting for an owner:

• User-wide build cache

Conclusion

This is a brief summary of the progress towards our a subset of the 2024 project goals. There is a lot more information available on the website, including the motivation for each goal, as well as detailed status updates. If you'd like more detail, please do check it out! You can also subscribe to individual tracking issues (or the entire rust-project-goals repo) to get regular updates.

The current set of goals target the second half of 2024 (2024H2). Next month we also expect to begin soliciting goals for the first half of 2025 (2025H1).

Continue Reading…

slightlyoff@toot.cafe ("Alex Russell") wrote:

Back in '22, regulators started peering over their glasses at Apple's indefensible [1][2] claim that forced monoculture was Good For Users, Actually.

To deflect, Apple introduced "Rapid Security Responses":

https://www.macobserver.com/news/apple-launches-rapid-security-response-a-new-feature-for-applying-security-updates-on-the-fly/

How's that going?

LOL.

Apple tried one (1) RSR in '23, [3] and* never again*.[4] Prolly because **it didn't work**:

https://arstechnica.com/security/2023/07/apple-releases-quickly-pulls-rapid-security-response-update-for-0-day-webkit-bug/

[1]: https://www.theregister.com/2021/05/27/safari_webkit_bug/
[2]: https://googleprojectzero.blogspot.com/2022/02/a-walk-through-project-zero-metrics.html#h.4ajnbffcm6lj
[3]: https://support.apple.com/en-us/121012
[4]: https://support.apple.com/en-us/100100

Attachments:

• Apple's WebKit/Safari patch gap has historically sucked by comparison to other vendors, not so much because they're slower to accept patches, but because bundling the browser with the OS is a terrible idea, but one Cupertino can't shake. And it turns out, "Rapid Security Response" didn't work, either. The answer is obvious -- decouple, and spend what it takes to make security a priority -- but that's not The FruitCo Way. (remote)

Reblogged by fromjason ("fromjason.xyz ❤️ 💻"):

hn50@social.lansky.name ("Hacker News 50") wrote:

Uber charges more if you have credits in your account

Link: https://viewfromthewing.com/uber-caught-overcharging-how-having-credits-in-your-account-might-be-costing-you/
Discussion: https://news.ycombinator.com/item?id=41620304

Reblogged by slightlyoff@toot.cafe ("Alex Russell"):

dbaron@w3c.social ("L. David Baron") wrote:

Should this instance be renamed to w3c.socal for the week, for TPAC? 🤣

https://www.w3.org/wiki/TPAC/2024

slightlyoff@toot.cafe ("Alex Russell") wrote:

I know I've fanboy'd about this before, but hot damn, color.io is incredibly well done. This is what 250KB of JS *for a good reason* looks like. If your site is slinging that much code but isn't attempting 3D color space conversions over images and video, doesn't work offline, and isn't basically instant every time you tap a button...maybe re-evaluate what's possible.

Reblogged by cstanhope@social.coop ("Your friendly 'net denizen"):

redoak@social.coop ("Red Oak") wrote:

*tips cap* m'shroom

Reblogged by slightlyoff@toot.cafe ("Alex Russell"):

janl@narrativ.es ("Jan Lehnardt :couchdb:") wrote:

This is perfect and we should start using these immediately.
https://glasgow.social/@sue/113182808818755906

slightlyoff@toot.cafe ("Alex Russell") wrote:

App Stores are a great idea that have no downsides and we should absolutely trust the future of computing to proprietary, unaccountable gatekeepers:

https://mastodon.social/@sandofsky/113181384256449181

Reblogged by collinsworth@hachyderm.io ("Josh Collinsworth"):

are0h@h-i.social ("Gorgeous Killer") wrote:

So basically, the state of Missouri is planning to carry out the public lynching of a brother that has been proven innocent.

This is an example of why I call the US a death cult. This is a straight up human sacrifice to white supremacy.

https://innocenceproject.org/petitions/stop-the-execution-of-marcellus-williams-an-innocent-man/

fromjason ("fromjason.xyz ❤️ 💻") wrote:

Sometimes, all I need is the air I breathe and a little treat

Reblogged by isagalaev ("Ivan Sagalaev :flag_wbw:"):

mattblaze@federate.social ("Matt Blaze") wrote:

Crowdfunded effort (led by the awesome Cards Against Humanity folks) bought a tract of pristine land in Texas near the Mexican border a few years ago to prevent development (such as a border wall), and to leave it in a natural state.

This year, Space X unilaterally started building on the tract, without anyone's permission, causing irreparable harm to the natural state of the land. Not cool, says the owner.

Hilarity currently en-suing. https://www.cahsuesmusk.com/

Reblogged by jsonstein@masto.deoan.org ("Jeff Sonstein"):

Phaethon wrote:

@arstechnica
NASA's first 4k video from the Lunar surface...

Attachments:

• 8005ed209e78449c.mp4

Reblogged by jsonstein@masto.deoan.org ("Jeff Sonstein"):

Phaethon wrote:

@jsonstein @TexasObserver
From the archives: Jan. 2021

How it started. How it's going

Attachments:

• aa09e53d3dde513a.jpg

Reblogged by jsonstein@masto.deoan.org ("Jeff Sonstein"):

markmetz@sfba.social ("🐝Mr.Mark🐝") wrote:

“Even if you don’t care about climate change, solar energy has become one of the cheapest, fastest ways to sate your appetite for electrons. Texas, the biggest oil and gas producer in the country, is also the national leader in adding solar power to its grid, surpassing California.”

https://www.vox.com/climate/372852/solar-power-energy-growth-record-us-climate-china

Reblogged by jsonstein@masto.deoan.org ("Jeff Sonstein"):

samlitzinger@journa.host ("Sam Litzinger") wrote:

“As Taliban starts restricting men too, some regret not speaking up sooner
> Beside imposing severe rules on women, new laws require men to grow fist-length beards and bar them from imitating non-Muslims in appearance or behavior.”

“Gosh, we didn’t think the face-eating leopards we helped put back in power would eat OUR faces!!”

https://www.washingtonpost.com/world/2024/09/22/afghanistan-taliban-restrictions-men-beards/

jsonstein@masto.deoan.org ("Jeff Sonstein") wrote:

Alexander Edwards: “When you have that level of hubris, you do and say the dumbest things. And I would say that Trump and Elon are very similar. They do and say some of the dumbest things… If Elon continues on this path, he’s going to find himself without a company in the U.S.”

https://www.hollywoodreporter.com/lifestyle/lifestyle-news/tesla-robotaxi-warner-bros-reveal-hollywood-rejection-elon-musk-1236007945/

jsonstein@masto.deoan.org ("Jeff Sonstein") wrote:

from https://www.texasobserver.org/
spot on, as usual @TexasObserver

Attachments:

• 920d3d70dacddad4.png (remote)

Reblogged by kornel ("Kornel"):

carnage4life@mas.to ("Dare Obasanjo") wrote:

A reminder that even the best ideas struggle to be considered if they are too divergent from the status quo. It’s hard for many to tell the difference between a bad idea and one that is too different from the established order.

Attachments:

• e8cefd3fa594f4ab.png (remote)

Reblogged by kornel ("Kornel"):

oglaf@socel.net ("Oglaf") wrote:

New Oglaf:
https://www.oglaf.com/ladders/

fromjason ("fromjason.xyz ❤️ 💻") wrote:

Republican or Democrat, all cops are bastards.

Attachments:

• Threads post: "are there democratic cops? do those even exist? every cop *i* have met/know are all republican"

fromjason ("fromjason.xyz ❤️ 💻") wrote:

Digital communities are groups of people who cultivate a shared experience on the web.

Digital markets are communities experiencing extraction. 

collinsworth@hachyderm.io ("Josh Collinsworth") wrote:

Apparently it's surprising to some people when big "family values" figures turn out to be deviant hypocrites?

It's not surprising to those of us who grew up evangelical.

We're never surprised.

jsonstein@masto.deoan.org ("Jeff Sonstein") wrote:

also http://mir-algorithm.libmir.org/index.html

jsonstein@masto.deoan.org ("Jeff Sonstein") wrote:

yum!

“Mir - Dlang Core Libraries · GitHub”

https://github.com/libmir

Reblogged by jakedel@mamot.fr ("S. Delafond"):

freexian@hachyderm.io ("Freexian :debian:") wrote:

With an extra fee, that support can be extended to an unsupported Debian/Ubuntu release.

You can explore the package availability, the features offered, the support tiers and pricing in detail at https://www.freexian.com/lts/php/

Reblogged by jakedel@mamot.fr ("S. Delafond"):

freexian@hachyderm.io ("Freexian :debian:") wrote:

Today, we are sharing more about the PHP Long Term Support offered by #Freexian with the help of @ondrej

The #PHP LTS service is for organizations needing alternate PHP releases which are not shipped by #Debian and the service is offered for multiple Debian/Ubuntu releases.

Funding a PHP release or PECL extension makes it available on upstream-supported Debian/Ubuntu releases for all customers and ensures its security support.

Reblogged by rmrenner ("The Old Gay Gristle Fest"):

ann3nova@corteximplant.com ("anne.💫") wrote:

For the 40th Anniversary of "Elite", Ian Bell has released the source codes for the Apple, Atari, C64, and NES versions of the game for free.

He also released the source for the unfinished SNES and BBC ports. A very cool gift for such a pioneering space sim.

http://www.elitehomepage.org/fourty/index.htm
http://www.elitehomepage.org/archive/index.htm

Attachments:

• The title screen for Elite (remote)

collinsworth@hachyderm.io ("Josh Collinsworth") wrote:

(Yes, this is a Matt Mullenweg subtoot)

collinsworth@hachyderm.io ("Josh Collinsworth") wrote:

We need to stop being surprised when people who are given massive power over a single community inevitably turn toxic.

Reblogged by fromjason ("fromjason.xyz ❤️ 💻"):

Raoued ("Raoued Jebali") wrote:

"There's only one solution: Intifada revolution" 🇵🇸✌🏻

Massive crowds rallied in Vancouver, #Canada to support #Palestine and Lebanon, protesting against the Israeli occupation and its brutal crimes against civilians.

#freepalestine #BreakingNews #BREAKING #news #GazaGenocide

Attachments:

• a495a937ad7a7321.mp4