Mastodon Feed: Posts

Mastodon Feed

Boosted by cstanhope@social.coop ("The Luddites were right"):
villares@ciberlandia.pt ("Alexandre B A Villares ☔🐍") wrote:

"Step inside the studio of Palestinian-American artist Samia Halaby, one of the earliest innovators of digital art."

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

via @guilhermesv

Mastodon Feed

Boosted by glyph ("Glyph"):
foone@digipres.club ("Alice Averlong🏳️‍⚧️") wrote:

not to sound too much like myself, but I was wearing my migraine blindfold for all of 10 minutes and I've designed a keyboard based on a pseudo-PS1 controller I've got.

Mastodon Feed

cwebber@social.coop ("Christine Lemmer-Webber") wrote:

Friends, it has never been easier to be vegetarian. You could even go mostly vegetarian. Vegetarian food is everywhere and you don't even need to give up most of the flavors you love. This is very different than when I first became vegetarian approx a couple decades ago.

Friends, it has never been easier to not voluntarily use datacenter-hosted genAI. You can just... not!

Mastodon Feed

cwebber@social.coop ("Christine Lemmer-Webber") wrote:

Is this about AI usage? Or is this about meat consumption?

Yes.

Mastodon Feed

cwebber@social.coop ("Christine Lemmer-Webber") wrote:

If your response to "an activity we all could easily just not do which is accelerating the death of our habitable planet" is "well there is a version of this where in theory it doesn't cook us so fast, I'm just not doing it" you might want to reconsider your actions

Mastodon Feed

cwebber@social.coop ("Christine Lemmer-Webber") wrote:

broiling the oceans

Mastodon Feed

Boosted by cwebber@social.coop ("Christine Lemmer-Webber"):
pvonhellermannn@mastodon.green ("Pauline von Hellermann") wrote:

#ClimateDiary “Above is a fictional weather forecast for August 18, 2050, broadcast by French television in 2014, intended to warn against the disastrous consequences of global warming.

Below is the weather forecast for June 22, 2026.”

(By @jakubwiech on unmentionable)

This brings out super starkly how #ClimateChange has accelerated so much more quickly than we thought even just 12 years ago.

Two photos of weather forecasts, showing maps of France, above one imagined in 2014 of a 2050 forecast of temperatures of high 30s, occasional 40-42, overall more orange; below actual forecast yesterday showing majority red and over 40s across France.

Mastodon Feed

pzmyers@freethought.online ("pzmyers 🕷") wrote:

That strange feeling I'm getting is the dread of impending doom.

https://freethoughtblogs.com/pharyngula/2026/06/23/ive-got-to-avoid-ed-zitron-in-the-morning/

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

Mastodon Feed

Boosted by brib@bribstodon.xyz ("brib :neofox_floof:​ :Nonbinary:"):
brib@bribstodon.xyz ("brib :neofox_floof:​ :Nonbinary:") wrote:

Coding up a #GoToSocial deleter was less intimidating than I expected.

If anyone wants to use the code, it is here: ~~https://codeberg.org/brib/brib-gts-cleaner~~ https://codeberg.org/brib/toot-delete-inator

Mastodon Feed

fribbledom ("muesli") wrote:

"Just one more feature" is the software equivalent of "just one more drink".

Mastodon Feed

brib@bribstodon.xyz ("brib :neofox_floof:​ :Nonbinary:") wrote:

guess who ✨ sent some emails ✨

please appreciate my peak productivity :neocat_cool_fingerguns:​

Mastodon Feed

dysfun@treehouse.systems ("gaytabase") wrote:

my nodes have a tightly packed structure to keep the size down. and part of the node is aligned to a cacheline. except the metadata that should go before it is variably sized. the metadata before it is needed to know the size of the various things in the node.

the metadata that should go after it can be split to fill the hole but this is quite tedious.

but there's nothing to say that a pointer has to point to the start of a region of memory, right? it could just point within it. they're not even real pointers, they're offsets within the file. it makes accounting a little more tedious, but we can trivially achieve optimal packing always by simply adding some small integers to the fixed size 'header' (which could be in the middle, immediately after the simd data.)

Mastodon Feed

sky@schub.social ("Sky Schubert") wrote:

okay who forgot to turn off the space heater again? we need to start naming and shaming, I'm way too hot

Mastodon Feed

Boosted by sky@schub.social ("Sky Schubert"):
jer@hachyderm.io ("jan-erik") wrote:

Last year: OMG, SUPPLY CHAIN RISKS EVERYWHERE.

This year: "hey parrot, please fix these CI failures and then auto-merge the code, kthxbye."

Mastodon Feed

dysfun@treehouse.systems ("gaytabase") wrote:

i've just concocted the most ludicrous trick ever that couldn't possibly work.

except i think it'll work.

scared now 😬

Mastodon Feed

Boosted by baldur@toot.cafe ("Baldur Bjarnason"):
jasongorman@mastodon.cloud ("Jason Gorman") wrote:

In some organisations, it just doesn't matter what dev teams do, and they can absorb a *lot* of *big* failures - like the IT disasters we read about in the public sector, except theirs rarely make the news.

(2/2)

Mastodon Feed

Boosted by baldur@toot.cafe ("Baldur Bjarnason"):
jasongorman@mastodon.cloud ("Jason Gorman") wrote:

There was a time when I didn't feel the need to debate the most wrongheaded, risky and harmful takes on software development because reality would eventually make the case for me.

I underestimated the capacity of some organisations to live with catastrophically bad outcomes if their moat's deep enough. (And, contrary to what you may read, most big business moats are things like property portfolios or rigged markets - not actual products or services.)

(1/2)

Mastodon Feed

Boosted by brib@bribstodon.xyz ("brib :neofox_floof:​ :Nonbinary:"):
Gulleko@kind.social wrote:

I took a break from sewing (I cut out the pieces for a dress last year and never got around to it) and she immediately stole the chair. I guess the sewing will have to wait. 😅

a tortoiseshell cat is curled up on a chair with a fluffy blanket on it. her head is upside down and her paws are outstretched. she is in a sunbeam coming through the window blinds.

Mastodon Feed

Boosted by brib@bribstodon.xyz ("brib :neofox_floof:​ :Nonbinary:"):
kestral@masto.hackers.town ("Kestral") wrote:

A reminder to anyone taking estradiol or other forms of hormone therapy - HRT is known to make you more prone to heatstroke, heat exhaustion, and sunburn.

We're entering the Danger Zone™ this week in the northern hemisphere. Stay safe, stay hydrated. Look after yourself.

You're brilliant. Stay brilliant.

Mastodon Feed

glyph ("Glyph") wrote:

(For fans who have been following along,, no, this is not the whole Big AI Post, but it is one of the more salient chunks of it, and maybe I will figure out ways to publish it in a form that people will actually be able to consume. To be continued…)

Mastodon Feed

Boosted by brib@bribstodon.xyz ("brib :neofox_floof:​ :Nonbinary:"):
parismarx@mastodon.online ("Paris Marx") wrote:

honestly i welcome the data center lobby just openly saying climate goals needed to be trashed so the tech industry can build ai — intense heat waves, record forest fires, worsening natural disasters be damned

https://www.politico.eu/article/europe-choose-ai-climate-goals-data-center-chief-warns/

#tech #ai #datacenters #climate #heatwave

Mastodon Feed

glyph ("Glyph") wrote:

The thing that “AIs” are the best at is turning every communication into a conflict, where the LLM user is the attacker and the person who has to consume its output is the defender. https://blog.glyph.im/2026/06/adversarial-communication.html

Mastodon Feed

Boosted by glyph ("Glyph"):
iris_meredith ("Iris") wrote:

RE: https://eigenmagic.net/@stilgherrian/116796558935290693

I think this is one that it's worth pushing on, even if it doesn't succeed. People getting fired over this is *exactly* the kind of thing that builds strong political movements, and while I don't have much to throw at this, I will support anyone who fights AI on this angle with the best writing I can muster.

Mastodon Feed

Boosted by glyph ("Glyph"):
MakhamDev@mastodon.gamedev.place wrote:

Potion #pixelcomposer

Attachments:

Mastodon Feed

dysfun@treehouse.systems ("gaytabase") wrote:

amazon composite day is here

Mastodon Feed

db@social.lol ("David Bushell 🪿") wrote:

BAH GAWD it's Andy Burnham off the top rope!

politics would be more accessible for young people (middle-aged men) if they had Jim Ross as a pundit

Mastodon Feed

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

Every word of this is correct:

https://youtu.be/LNFic3cTD4E

Mastodon Feed

Boosted by glyph ("Glyph"):
mcc wrote:

I am releasing a video game this week and I am going to attempt to include a Linux appimage. My current plan is to include only 64-bit binaries. This post is your chance to convince me that I should include 32-bit builds (in addition or exclusively, depending on how persuasive you are).

Mastodon Feed

Boosted by cstanhope@social.coop ("The Luddites were right"):
adalheidis@mastodon.art ("Lou") wrote:

Proud knight

illustration of a knight on a horse - the horse's caparison is painted with the colours of the LGBT pride flag

Mastodon Feed

Boosted by cstanhope@social.coop ("The Luddites were right"):
vv@solarpunk.moe ("vv 💫 [follow my new artist profile!]") wrote:

I have seen some posts that seem to imply that people's discomfort with code generated by AI is an matter of identity, that is, the threat that outsiders will be able to make code, and thus those in the know, the "elites" feel threatened. That the only way to move forward is to accept that coders need not be experts anymore, and that the role of the software developer will change.

But this is not how I view the practice of writing code at all. I want code to be more accessible and understandable by more people. My complaint with LLMs is that they are actually antithetical to this goal. Yes, someone who doesn't know how to code can now create an app that solves a problem stated in plain English, and it may work correctly most or all of the time. But that is not actually making code more accessible. Indeed, if everyone relies on LLMs to write software, nobody will know how the software works anymore!

As someone with over 10 years of experience coding, I know that reduced understanding of code always results in bad outcomes. There's bad performance, bad functionality, all sorts of things. People get apathetic and assume that the performance issues are inevitable. But computers are absurdly fast! Very few computations these days have any reason to take longer than an instant. The solution is knowing how to read code to find the problems! This can't be done reliably by a machine. I want more people to develop this skill, not fewer! LLMs just allow people to bypass any ability to identify issues. So my concern with them is that we will have more code to sift through, and less careful consideration at play.

This isn't about a threat to my identity, it's about a threat to the stability of all software, and the abilities of all software developers. This deskilling will only fossilize software and prevent us from developing something that is actually more democratizing.