Tootfinder

Opt-in global Mastodon full text search. Join the index!

@tiotasram@kolektiva.social
2025-08-12 09:01:39

Long post, game design
Crungle is a game designed to be a simple test of general reasoning skills that's difficult to play by rote memory, since there are many possible rule sets, but it should be easy to play if one can understand and extrapolate from rules. The game is not necessarily fair, with the first player often having an advantage or a forced win. The game is entirely deterministic, although a variant determines the rule set randomly.
This is version 0.1, and has not yet been tested at all.
Crungle is a competitive game for two players, each of whom controls a single piece on a 3x3 grid. The cells of the grid are numbered from 1 to 9, starting at the top left and proceeding across each row and then down to the next row, so the top three cells are 1, 2, and 3 from left to right, then the next three are 4, 5, and 6 and the final row is cells 7, 8, and 9.
The two players decide who shall play as purple and who shall play as orange. Purple goes first, starting the rules phase by picking one goal rule from the table of goal rules. Next, orange picks a goal rule. These two goal rules determine the two winning conditions. Then each player, starting with orange, alternate picking a movement rule until four movement rules have been selected. During this process, at most one indirect movement rule may be selected. Finally, purple picks a starting location for orange (1-9), with 5 (the center) not allowed. Then orange picks the starting location for purple, which may not be adjacent to orange's starting position.
Alternatively, the goal rules, movement rules, and starting positions may be determined randomly, or a pre-determined ruleset may be selected.
If the ruleset makes it impossible to win, the players should agree to a draw. Either player could instead "bet" their opponent. If the opponent agrees to the bet, the opponent must demonstrate a series of moves by both players that would result in a win for either player. If they can do this, they win, but if they submit an invalid demonstration or cannot submit a demonstration, the player who "bet" wins.
Now that starting positions, movement rules, and goals have been decided, the play phase proceeds with each player taking a turn, starting with purple, until one player wins by satisfying one of the two goals, or until the players agree to a draw. Note that it's possible for both players to occupy the same space.
During each player's turn, that player identifies one of the four movement rules to use and names the square they move to using that rule, then they move their piece into that square and their turn ends. Neither player may use the same movement rule twice in a row (but it's okay to use the same rule your opponent just did unless another rule disallows that). If the movement rule a player picks moves their opponent's piece, they need to state where their opponent's piece ends up. Pieces that would move off the board instead stay in place; it's okay to select a rule that causes your piece to stay in place because of this rule. However, if a rule says "pick a square" or "move to a square" with some additional criteria, but there are no squares that meet those criteria, then that rule may not be used, and a player who picks that rule must pick a different one instead.
Any player who incorrectly states a destination for either their piece or their opponent's piece, picks an invalid square, or chooses an invalid rule has made a violation, as long as their opponent objects before selecting their next move. A player who makes at least three violations immediately forfeits and their opponent wins by default. However, if a player violates a rule but their opponent does not object before picking their next move, the stated destination(s) of the invalid move still stand, and the violation does not count. If a player objects to a valid move, their objection is ignored, and if they do this at least three times, they forfeit and their opponent wins by default.
Goal rules (each player picks one; either player can win using either chosen rule):
End your turn in the same space as your opponent three turns in a row.
End at least one turn in each of the 9 cells.
End five consecutive turns in the three cells in any single row, ending at least one turn on each of the three.
End five consecutive turns in the three cells in any single column, ending at least one turn on each of the three.
Within the span of 8 consecutive turns, end at least one turn in each of cells 1, 3, 7, and 9 (the four corners of the grid).
Within the span of 8 consecutive turns at least one turn in each of cells 2, 4, 6, and 8 (the central cells on each side).
Within the span of 8 consecutive turns, end at least one turn in the cell directly above your opponent, and end at least one turn in the cell directly below your opponent (in either order).
Within the span of 8 consecutive turns at least one turn in the cell directly to the left of your opponent, and end at least one turn in the cell directly to the right of your opponent (in either order).
End 12 turns in a row without ending any of them in cell 5.
End 8 turns in a row in 8 different cells.
Movement rules (each player picks two; either player may move using any of the four):
Move to any cell on the board that's diagonally adjacent to your current position.
Move to any cell on the board that's orthogonally adjacent to your current position.
Move up one cell. Also move your opponent up one cell.
Move down one cell. Also move your opponent down one cell.
Move left one cell. Also move your opponent left one cell.
Move right one cell. Also move your opponent right one cell.
Move up one cell. Move your opponent down one cell.
Move down one cell. Move your opponent up one cell.
Move left one cell. Move your opponent right one cell.
Move right one cell. Move your opponent left one cell.
Move any pieces that aren't in square 5 clockwise around the edge of the board 1 step (for example, from 1 to 2 or 3 to 6 or 9 to 8).
Move any pieces that aren't in square 5 counter-clockwise around the edge of the board 1 step (for example, from 1 to 4 or 6 to 3 or 7 to 8).
Move to any square reachable from your current position by a knight's move in chess (in other words, a square that's in an adjacent column and two rows up or down, or that's in an adjacent row and two columns left or right).
Stay in the same place.
Swap places with your opponent's piece.
Move back to the position that you started at on your previous turn.
If you are on an odd-numbered square, move to any other odd-numbered square. Otherwise, move to any even-numbered square.
Move to any square in the same column as your current position.
Move to any square in the same row as your current position.
Move to any square in the same column as your opponent's position.
Move to any square in the same row as your opponent's position.
Pick a square that's neither in the same row as your piece nor in the same row as your opponent's piece. Move to that square.
Pick a square that's neither in the same column as your piece nor in the same column as your opponent's piece. Move to that square.
Move to one of the squares orthogonally adjacent to your opponent's piece.
Move to one of the squares diagonally adjacent to your opponent's piece.
Move to the square opposite your current position across the middle square, or stay in place if you're in the middle square.
Pick any square that's closer to your opponent's piece than the square you're in now, measured using straight-line distance between square centers (this includes the square your opponent is in). Move to that square.
Pick any square that's further from your opponent's piece than the square you're in now, measured using straight-line distance between square centers. Move to that square.
If you are on a corner square (1, 3, 7, or 9) move to any other corner square. Otherwise, move to square 5.
If you are on an edge square (2, 4, 6, or 8) move to any other edge square. Otherwise, move to square 5.
Indirect movement rules (may be chosen instead of a direct movement rule; at most one per game):
Move using one of the other three movement rules selected in your game, and in addition, your opponent may not use that rule on their next turn (nor may they select it via an indirect rule like this one).
Select two of the other three movement rules, declare them, and then move as if you had used one and then the other, applying any additional effects of both rules in order.
Move using one of the other three movement rules selected in your game, but if the move would cause your piece to move off the board, instead of staying in place move to square 5 (in the middle).
Pick one of the other three movement rules selected in your game and apply it, but move your opponent's piece instead of your own piece. If that movement rule says to move "your opponent's piece," instead apply that movement to your own piece. References to "your position" and "your opponent's position" are swapped when applying the chosen rule, as are references to "your turn" and "your opponent's turn" and do on.
#Game #GameDesign

@Techmeme@techhub.social
2025-08-20 16:18:02

Google unveils the $999 Pixel 10 Pro and $1,199 10 Pro XL, with 6.3" and 6.8" OLED displays, Tensor G5 chips, Zoned UFS storage, available on August 28 (Ben Schoon/9to5Google)
9to5google.com/2025/08/20/goog

@arXiv_condmatstatmech_bot@mastoxiv.page
2025-08-19 09:09:10

Extraction of classical ergotropy
Michele Campisi
arxiv.org/abs/2508.12797 arxiv.org/pdf/2508.12797

@sonnets@bots.krohsnest.com
2025-07-20 11:25:09

Sonnet 076 - LXXVI
Why is my verse so barren of new pride,
So far from variation or quick change?
Why with the time do I not glance aside
To new-found methods, and to compounds strange?
Why write I still all one, ever the same,
And keep invention in a noted weed,
That every word doth almost tell my name,
Showing their birth, and where they did proceed?
O! know sweet love I always write of you,
And you and love are still my argument;…

@rberger@hachyderm.io
2025-08-18 22:51:47

Q1’s –0.5% growth is already a bad look. But Apollo’s Torsten SlŸk points out that data-center construction alone added about a full percentage point. Remove it, and you’re staring at –1.5%.
Q2 looks so much healthier at 3.0%, or you would think so. Pantheon Macroeconomics sums up the first half of 2025 with some more sobriety: AI alone contributed about half a percentage point of GDP. Without it, the U.S. would be bumbling along at 1% growth. Still better than minus, but thin grass all the same.
One more stat for the better view: since 2019, investment in AI-sensitive sectors is up 53%, while everywhere else is basically flat – 0.3%.
turingpost.com/p/fod114?_bhlid

@grifferz@social.bitfolk.com
2025-07-16 20:23:21

I've got a 3am start with derpmaster Mike coming up in the next few days. He normally gets up at 5.30am so I've got a feeling there's going to be no settling him after I arrive and his regular humans all leave.
Still, hot weather will mean an early walk and breakfast and then we can both snooze!
My fourth year of looking after Michael.
#Greyhounds

A large cow pattern greyhound boy laying on his left side on a rug head and front legs closest to the camera. His eyes are closed and his tongue pokes out of the right (upper) side of his jaw.
A close up photo of the head of the same large cow pattern greyhound boy from the previous photo. His right eye and ear have a dark patch while the rest of his head is white.  In this photo he has just opened his eye slightly. His tongue has retracted a little but still peeks out of the upper (right) side of his jaw.
@tiotasram@kolektiva.social
2025-07-04 20:14:31

Long; central Massachusetts colonial history
Today on a whim I visited a site in Massachusetts marked as "Huguenot Fort Ruins" on OpenStreetMaps. I drove out with my 4-year-old through increasingly rural central Massachusetts forests & fields to end up on a narrow street near the top of a hill beside a small field. The neighboring houses had huge lawns, some with tractors.
Appropriately for this day and this moment in history, the history of the site turns out to be a microcosm of America. Across the field beyond a cross-shaped stone memorial stood an info board with a few diagrams and some text. The text of the main sign (including typos/misspellings) read:
"""
Town Is Formed
Early in the 1680's, interest began to generate to develop a town in the area west of Natick in the south central part of the Commonwealth that would be suitable for a settlement. A Mr. Hugh Campbell, a Scotch merchant of Boston petitioned the court for land for a colony. At about the same time, Joseph Dudley and William Stoughton also were desirous of obtaining land for a settlement. A claim was made for all lands west of the Blackstone River to the southern land of Massachusetts to a point northerly of the Springfield Road then running southwesterly until it joined the southern line of Massachusetts.
Associated with Dudley and Stoughton was Robert Thompson of London, England, Dr. Daniel Cox and John Blackwell, both of London and Thomas Freak of Hannington, Wiltshire, as proprietors. A stipulation in the acquisition of this land being that within four years thirty families and an orthodox minister settle in the area. An extension of this stipulation was granted at the end of the four years when no group large enough seemed to be willing to take up the opportunity.
In 1686, Robert Thompson met Gabriel Bernor and learned that he was seeking an area where his countrymen, who had fled their native France because of the Edict of Nantes, were desirous of a place to live. Their main concern was to settle in a place that would allow them freedom of worship. New Oxford, as it was the so-named, at that time included the larger part of Charlton, one-fourth of Auburn, one-fifth of Dudley and several square miles of the northeast portion of Southbridge as well as the easterly ares now known as Webster.
Joseph Dudley's assessment that the area was capable of a good settlement probably was based on the idea of the meadows already established along with the plains, ponds, brooks and rivers. Meadows were a necessity as they provided hay for animal feed and other uses by the settlers. The French River tributary books and streams provided a good source for fishing and hunting. There were open areas on the plains as customarily in November of each year, the Indians burnt over areas to keep them free of underwood and brush. It appeared then that this area was ready for settling.
The first seventy-five years of the settling of the Town of Oxford originally known as Manchaug, embraced three different cultures. The Indians were known to be here about 1656 when the Missionary, John Eliott and his partner Daniel Gookin visited in the praying towns. Thirty years later, in 1686, the Huguenots walked here from Boston under the guidance of their leader Isaac Bertrand DuTuffeau. The Huguenot's that arrived were not peasants, but were acknowledged to be the best Agriculturist, Wine Growers, Merchant's, and Manufacter's in France. There were 30 families consisting of 52 people. At the time of their first departure (10 years), due to Indian insurrection, there were 80 people in the group, and near their Meetinghouse/Church was a Cemetery that held 20 bodies. In 1699, 8 to 10 familie's made a second attempt to re-settle, failing after only four years, with the village being completely abandoned in 1704.
The English colonist made their way here in 1713 and established what has become a permanent settlement.
"""
All that was left of the fort was a crumbling stone wall that would have been the base of a higher wooden wall according to a picture of a model (I didn't think to get a shot of that myself). Only trees and brush remain where the multi-story main wooden building was.
This story has so many echoes in the present:
- The rich colonialists from Boston & London agree to settle the land, buying/taking land "rights" from the colonial British court that claimed jurisdiction without actually having control of the land. Whether the sponsors ever actually visited the land themselves I don't know. They surely profited somehow, whether from selling on the land rights later or collecting taxes/rent or whatever, by they needed poor laborers to actually do the work of developing the land (& driving out the original inhabitants, who had no say in the machinations of the Boston court).
- The land deal was on condition that there capital-holders who stood to profit would find settlers to actually do the work of colonizing. The British crown wanted more territory to be controlled in practice not just in theory, but they weren't going to be the ones to do the hard work.
- The capital-holders actually failed to find enough poor suckers to do their dirty work for 4 years, until the Huguenots, fleeing religious persecution in France, were desperate enough to accept their terms.
- Of course, the land was only so ripe for settlement because of careful tending over centuries by the natives who were eventually driven off, and whose land management practices are abandoned today. Given the mention of praying towns (& dates), this was after King Phillip's war, which resulted in at least some forced resettlement of native tribes around the area, but the descendants of those "Indians" mentioned in this sign are still around. For example, this is the site of one local band of Nipmuck, whose namesake lake is about 5 miles south of the fort site: #LandBack.

@brian_gettler@mas.to
2025-07-15 13:19:30

For years, every road trip we took began with the same song. It's been a while since we've listened to it right out of the gates, but the feeling's still there.
The Clash, "London Calling" (1979)
youtu.be/LC2WpBcdM_A

@mgorny@social.treehouse.systems
2025-09-05 13:15:19

"""
In melancholy, the spirits are carried away by an agitation, but a weak agitation that lacks power or violence, a sort of impotent upset that follows neither a particular path nor the aperta opercula [open ways], but traverses the cerebral matter constantly creating new pores. Yet the spirits do not wander far on the new paths they create, and their agitation dies down rapidly, as their strength is quickly spent and motion comes to a halt: ‘non longe perveniunt’ [they do not reach far]. A trouble of this nature, common to all delirium, does not have the power to produce on the surface of the body the violent movements or the cries to be observed in mania and frenzy. Melancholy never attains frenzy; it is a madness always at the limits of its own impotence. That paradox is explained by the secret alterations in the spirits. Ordinarily, they travel with the speed and instantaneous transparency of rays of light, but in melancholy they become weighed down with night, becoming ‘obscure, thick and dark’, and the images of things that they bring before consciousness are ‘in a shadow, or covered with darkness’. As a result they move more slowly, and are more like a dark, chemical vapour than pure light. This chemical vapour is acid in nature, rather than sulphurous or alcoholic, for in acid vapours the particles are mobile and incapable of repose, but their activity is weak and without consequence. When they are distilled, all that remains in the still is a kind of insipid phlegm. Acid vapours, therefore, are taken to have the same properties as melancholy, whereas alcoholic vapours, which are always ready to burst into flames, are more related to frenzy, and sulphurous vapours bring on mania, as they are agitated by continuous, violent movement. If the ‘formal reason and causes’ of melancholy were to be sought, it made sense to look for them in the vapours that rose up from the blood to the head, and which had degenerated into ‘an acetous or sharp distillation’. A cursory glance seems to indicate that a melancholy of spirits and a whole chemistry of humours lies behind Willis’ analyses, but in fact his guiding principle mostly reflects the immediate qualities of the melancholic illness: an impotent disorder, and the shadow that comes over the spirit with an acrid acidity that slowly corrodes the heart and the mind. The chemistry of acids is not an explanation of the symptoms, but a qualitative option: a whole phenomenology of melancholic experience.
"""
(Michel Foucault, History of Madness)

@Demirramon@cyberfurz.social
2025-09-17 17:21:55

I'm trying to use paths to make hair in Blender for the first time and it's actually easier and more fun than what I thought! I will still have to do some cleanup but I would have imploded doing this in a different way.
#3DModeling #Blender

Screenshot of the head of a 3D model of an anthro border collie with blue-ish nose and inner ears. He has cartoony white hair.
Same as the previous in wireframe mode, showing the paths that make up the hair.
@aardrian@toot.cafe
2025-09-16 18:27:53

Reality check…
In JavaScript APIs, when pressing Enter from the numpad or not, it still sends the same key code (so testing for one tests for both). It’s the location that differentiates them. Yeah?
I’m using deprecated `keyCode`, plus `key` and `location`.
codepen.io/aardrian/pen/wBKVLKd

@roelgrif@mstdn.social
2025-07-16 18:14:11

Israhell, obviously very disappointed that they still haven't succeeded in starting WWIII, just bombed Damascus (including the presidential palace).
broadcasted on live TV ...

TV host ducking away after a giant explosion occurred, visible in the background and audible on the show.
same as previous picture, half a second later
@sean@scoat.es
2025-09-16 14:38:03

Signal’s Secure Backups sounds like it uses the same mechanism that @… and I designed for completely private (yet company-stored) backups when we were at Matter.
They don’t (and we didn’t) get any of the user’s information, but they’re still able to store the backup data, opaquely, on their servers.

@simon_brooke@mastodon.scot
2025-09-09 18:09:43

Butterflies -- in total five red admirals (although I didn't get all of them into one photo), one small tortoiseshell, and two cabbage whites -- feeding on the same field thistle on my croft in yesterday's sunshine. I'd like to pretend this was a common sight, but it's not; still, it is a comfort that one can still occasionally see this many butterflies active at the same time.
There were also two dragonflies around, but I failed to photograph either.

A rather ragged thistle plant in sunlight, against a shaded hedge behind. Many of the flowers have turned to tufted white seed-heads, but on one that remains at the top of the plant, a red admiral is feeding. at the top right of the frame, a cabbage white is in flight.
Three red admirals ranged around the left and top of the thistle plant, while a cabbage white feeds centre right and a small tortoiseshell feeds lower right.
Three red admirals feeding on the thistle plant.
@Sustainable2050@mastodon.energy
2025-09-12 20:32:56

Electrification is still marginal in the Netherlands. Dutch electricity consumption in the first half of 2025 was almost exactly the same as a decade ago, in the first half of 2015 ( 0.3%).
Efficiency gains compensated for the modest shares of electric cars and heat pumps that did enter the scene.
Source:

Graph showing Dutch electricity consumption: practically flat for 10 years now.
@tiotasram@kolektiva.social
2025-09-13 23:43:29

TL;DR: what if nationalism, not anarchy, is futile?
Since I had the pleasure of seeing the "what would anarchists do against a warlord?" argument again in my timeline, I'll present again my extremely simple proposed solution:
Convince the followers of the warlord that they're better off joining you in freedom, then kill or exile the warlord once they're alone or vastly outnumbered.
Remember that even in our own historical moment where nothing close to large-scale free society has existed in living memory, the warlord's promise of "help me oppress others and you'll be richly rewarded" is a lie that many understand is historically a bad bet. Many, many people currently take that bet, for a variety of reasons, and they're enough to coerce through fear an even larger number of others. But although we imagine, just as the medieval peasants might have imagined of monarchy, that such a structure is both the natural order of things and much too strong to possibly fail, in reality it takes an enormous amount of energy, coordination, and luck for these structures to persist! Nations crumble every day, and none has survived more than a couple *hundred* years, compared to pre-nation societies which persisted for *tends of thousands of years* if not more. I'm this bubbling froth of hierarchies, the notion that hierarchy is inevitable is certainly popular, but since there's clearly a bit of an ulterior motive to make (and teach) that claim, I'm not sure we should trust it.
So what I believe could form the preconditions for future anarchist societies to avoid the "warlord problem" is merely: a widespread common sense belief that letting anyone else have authority over you is morally suspect. Given such a belief, a warlord will have a hard time building any following at all, and their opponents will have an easy time getting their supporters to defect. In fact, we're already partway there, relative to the situation a couple hundred years ago. At that time, someone could claim "you need to obey my orders and fight and die for me because the Queen was my mother" and that was actually a quite successful strategy. Nowadays, this strategy is only still working in a few isolated places, and the idea that one could *start a new monarchy* or even resurrect a defunct one seems absurd. So why can't that same transformation from "this is just how the world works" to "haha, how did anyone ever believe *that*? also happen to nationalism in general? I don't see an obvious reason why not.
Now I think one popular counterargument to this is: if you think non-state societies can win out with these tactics, why didn't they work for American tribes in the face of the European colonizers? (Or insert your favorite example of colonialism here.) I think I can imagine a variety of reasons, from the fact that many of those societies didn't try this tactic (and/or were hierarchical themselves), to the impacts of disease weakening those societies pre-contact, to the fact that with much-greater communication and education possibilities it might work better now, to the fact that most of those tribes are *still* around, and a future in which they persist longer than the colonist ideologies actually seems likely to me, despite the fact that so much cultural destruction has taken place. In fact, if the modern day descendants of the colonized tribes sow the seeds of a future society free of colonialism, that's the ultimate demonstration of the futility of hierarchical domination (I just read "Theory of Water" by Leanne Betasamosake Simpson).
I guess the TL;DR on this is: what if nationalism is actually as futile as monarchy, and we're just unfortunately living in the brief period during which it is ascendant?

@scott@carfree.city
2025-09-15 23:44:27

Ritual Coffee’s parklet has been there for over a decade, but is still considered temporary by the city. A tree planted there 10 years ago could be relatively mature with a large canopy by now. SF needs a path from parklets to permanent spot sidewalk widenings.

Ritual Coffee storefront with boat-like parklet in the parking lane, photographed today.
The same Ritual parklet in a February 2015 Google street view.
@unchartedworlds@scicomm.xyz
2025-09-10 09:46:57
Content warning: Twitter & Fedi

Thinking about this post:
#FediMeta #Twitter #news

@stefan@gardenstate.social
2025-07-14 20:34:55

I see many people argue that it doesn't matter if it is cruelty or good intention if the end result is the same.
I'm still of the opinion good intentions matter.

@nobodyinperson@fosstodon.org
2025-07-11 04:10:28

Wow, the new #Mastodon 4.4.1 webinterface has some weird behaviour:
- browser back button (sometimes) yeets you to the top of the timeline, losing that precious scroll position
- same for the UI back button, which is now so high up you can't reach it with the right-hand thumb
- switching away from the post editor (e.g. to find the Mastodon version) (still?) drops the entire po…

@jamesthebard@social.linux.pizza
2025-07-08 17:02:45

Opened up YouTube, got nerd sniped with a math problem. After a bad morning, it was the perfect thing to take a break working on. Still haven't watched the actual video, just the thumbnail...will do that once I get off of work to see if we got to the answer the same way (well, the proof that is). #math

The problem is: given 3 does not divide "a" and 3 does not divide "b", prove that 9 divides "a^6 - b^6"
@paulbusch@mstdn.ca
2025-07-16 00:16:38

I'm impressed with designers that create flat packed furniture. Crafting a jigsaw puzzle of wood and hardware that assembles into fashionable and sturdy furniture ranks right up there with aerospace engineering.
And then there's this. A shoe cabinet that my wife ordered to fit in our sunroom to hide our hideous footwear that we slip on when we go in the backyard. It came in 18 pieces, plus 8 separate tiny bags of hardware and minimal instructions. Two hours of assembly later, it's virtually the same size in volume as the shipping carton it arrived in. I know there are reasons why it's not shipped complete, but it's still a little irritating.
#things_that_make_me_go_hmmm

@benthos@mastodon.sdf.org
2025-08-10 22:10:57

I watched "Sorcerer" (1977, dir. William Friedkin) for the first time. The 4k transfer looks terrific. It's based on the Arnaud novel, which was made into a film of the same name in 1953 by HG Clouzot. Roy Scheider is terrific. It's hard to fathom that this was a critical and box office failure.

Still from the film "Sorcerer" (1977).  A large truck is leaning precariously on a rickety wooden bridge in a jungle, during a downpour.  A man is on the bridge holding himself up, with his legs in a large hole in the bridge.
@arXiv_statME_bot@mastoxiv.page
2025-07-14 08:50:12

Robust inference under Benford's law
Lucio Barabesi, Andrea Cerioli, Andrea Cerasa, Domenico Perrotta
arxiv.org/abs/2507.08650

@kurtsh@mastodon.social
2025-07-14 15:22:55

Dialing a phone number in the same area code as your own yet still getting charged long distance fees because the number was an exception & outside of your local zone.
Heck, long distance charges for domestic calling in it of itself is probably a foreign concept to Millennials & GenZ.

@qurlyjoe@mstdn.social
2025-07-04 15:11:20

This is from a blog entry posted in 2014. Plus ça change…. People make a lot of noise about the 2nd Amendment, and still some noise about the 1st, but it’s the 4th we should be making noise about, lately, and the other 7 are worth taking a look at today, too, while you’re enjoying your beers and brats on the bbq.

Iconic portrait of George Washington.
I led the founding of a republic that gives you constitutional rights, a democratic means for obtaining peaceful change, and competitive elections so those who govern do so at your consent.
You make fun of protesters, re-elect the same bastards over and over, let the rich turn your elected officials into their pawns, and as long as you have a new pair of Nikes and a Big Mac and a coke you couldn’t care less that your own government is selling your future jo…
@marcel@waldvogel.family
2025-09-06 14:02:21

Some programming wisdom from 40 years ago. Exciting to see how many of them are still important advice today.
(aka: @… 's aphorism collection 🦆)

@mgorny@social.treehouse.systems
2025-08-12 18:12:44

I was trying to package #FlexiBLAS for #Gentoo, and to be honest, it doesn't look that good.
The first red flag is lack of an open bug tracker. Apparently, there is the tracker on GitLab that's limited to "members of their group and selected external contributors", but it doesn't seem to be used much. So it's "send us an email", and wonder how many people sent us the same bug report before.
The git repository is currently at something tagged 3.4.80 that seems to be prerelease, and its build system is quite broken. Not exactly the best path to verify that the bugs you are hitting are still there.
Now, upstream seems to insist on either using vendored netlib #LAPACK, or statically linking to the system library (we don't install the static libraries). Apparently I can specify the shared libraries instead, but it doesn't work — and it's unclear to me whether it doesn't work because I'm using the shared libraries, or because it doesn't support my LAPACK version. If I build LAPACK without deprecated symbols, it refuses to load it at runtime because of missing symbols. And if I build it with deprecated symbols, it fails to find some symbols at CMake time.
Honestly, I feel like I've spent too much time on this project already, especially given that its future is entirely unclear to me — the current git is quite broken, I have no clue how many issues were reported already and whether my bug reports will receive any reply. It definitely doesn't fare well for a package that we might start to rely heavily on. We don't want a cathedral there.
mpi-magdeburg.mpg.de/projects/
gitlab.mpi-magdeburg.mpg.de/so

@ErikJonker@mastodon.social
2025-08-11 13:53:53

a good blog but the most relevant line is "GPT-5 may be a moderate quantitative improvement (and it may be cheaper) but it still fails in all the same qualitative ways as its predecessors" , very true but indeed now using it a few days and i notice those moderate improvements.. And i was already aware of all it's failings.
For me in day-to-day use it is better and that is wat counts for me at least. Oh and always (yes always) check outcomes before you use them.

@tiotasram@kolektiva.social
2025-08-04 15:49:00

Should we teach vibe coding? Here's why not.
Should AI coding be taught in undergrad CS education?
1/2
I teach undergraduate computer science labs, including for intro and more-advanced core courses. I don't publish (non-negligible) scholarly work in the area, but I've got years of craft expertise in course design, and I do follow the academic literature to some degree. In other words, In not the world's leading expert, but I have spent a lot of time thinking about course design, and consider myself competent at it, with plenty of direct experience in what knowledge & skills I can expect from students as they move through the curriculum.
I'm also strongly against most uses of what's called "AI" these days (specifically, generative deep neutral networks as supplied by our current cadre of techbro). There are a surprising number of completely orthogonal reasons to oppose the use of these systems, and a very limited number of reasonable exceptions (overcoming accessibility barriers is an example). On the grounds of environmental and digital-commons-pollution costs alone, using specifically the largest/newest models is unethical in most cases.
But as any good teacher should, I constantly question these evaluations, because I worry about the impact on my students should I eschew teaching relevant tech for bad reasons (and even for his reasons). I also want to make my reasoning clear to students, who should absolutely question me on this. That inspired me to ask a simple question: ignoring for one moment the ethical objections (which we shouldn't, of course; they're very stark), at what level in the CS major could I expect to teach a course about programming with AI assistance, and expect students to succeed at a more technically demanding final project than a course at the same level where students were banned from using AI? In other words, at what level would I expect students to actually benefit from AI coding "assistance?"
To be clear, I'm assuming that students aren't using AI in other aspects of coursework: the topic of using AI to "help you study" is a separate one (TL;DR it's gross value is not negative, but it's mostly not worth the harm to your metacognitive abilities, which AI-induced changes to the digital commons are making more important than ever).
So what's my answer to this question?
If I'm being incredibly optimistic, senior year. Slightly less optimistic, second year of a masters program. Realistic? Maybe never.
The interesting bit for you-the-reader is: why is this my answer? (Especially given that students would probably self-report significant gains at lower levels.) To start with, [this paper where experienced developers thought that AI assistance sped up their work on real tasks when in fact it slowed it down] (arxiv.org/abs/2507.09089) is informative. There are a lot of differences in task between experienced devs solving real bugs and students working on a class project, but it's important to understand that we shouldn't have a baseline expectation that AI coding "assistants" will speed things up in the best of circumstances, and we shouldn't trust self-reports of productivity (or the AI hype machine in general).
Now we might imagine that coding assistants will be better at helping with a student project than at helping with fixing bugs in open-source software, since it's a much easier task. For many programming assignments that have a fixed answer, we know that many AI assistants can just spit out a solution based on prompting them with the problem description (there's another elephant in the room here to do with learning outcomes regardless of project success, but we'll ignore this over too, my focus here is on project complexity reach, not learning outcomes). My question is about more open-ended projects, not assignments with an expected answer. Here's a second study (by one of my colleagues) about novices using AI assistance for programming tasks. It showcases how difficult it is to use AI tools well, and some of these stumbling blocks that novices in particular face.
But what about intermediate students? Might there be some level where the AI is helpful because the task is still relatively simple and the students are good enough to handle it? The problem with this is that as task complexity increases, so does the likelihood of the AI generating (or copying) code that uses more complex constructs which a student doesn't understand. Let's say I have second year students writing interactive websites with JavaScript. Without a lot of care that those students don't know how to deploy, the AI is likely to suggest code that depends on several different frameworks, from React to JQuery, without actually setting up or including those frameworks, and of course three students would be way out of their depth trying to do that. This is a general problem: each programming class carefully limits the specific code frameworks and constructs it expects students to know based on the material it covers. There is no feasible way to limit an AI assistant to a fixed set of constructs or frameworks, using current designs. There are alternate designs where this would be possible (like AI search through adaptation from a controlled library of snippets) but those would be entirely different tools.
So what happens on a sizeable class project where the AI has dropped in buggy code, especially if it uses code constructs the students don't understand? Best case, they understand that they don't understand and re-prompt, or ask for help from an instructor or TA quickly who helps them get rid of the stuff they don't understand and re-prompt or manually add stuff they do. Average case: they waste several hours and/or sweep the bugs partly under the rug, resulting in a project with significant defects. Students in their second and even third years of a CS major still have a lot to learn about debugging, and usually have significant gaps in their knowledge of even their most comfortable programming language. I do think regardless of AI we as teachers need to get better at teaching debugging skills, but the knowledge gaps are inevitable because there's just too much to know. In Python, for example, the LLM is going to spit out yields, async functions, try/finally, maybe even something like a while/else, or with recent training data, the walrus operator. I can't expect even a fraction of 3rd year students who have worked with Python since their first year to know about all these things, and based on how students approach projects where they have studied all the relevant constructs but have forgotten some, I'm not optimistic seeing these things will magically become learning opportunities. Student projects are better off working with a limited subset of full programming languages that the students have actually learned, and using AI coding assistants as currently designed makes this impossible. Beyond that, even when the "assistant" just introduces bugs using syntax the students understand, even through their 4th year many students struggle to understand the operation of moderately complex code they've written themselves, let alone written by someone else. Having access to an AI that will confidently offer incorrect explanations for bugs will make this worse.
To be sure a small minority of students will be able to overcome these problems, but that minority is the group that has a good grasp of the fundamentals and has broadened their knowledge through self-study, which earlier AI-reliant classes would make less likely to happen. In any case, I care about the average student, since we already have plenty of stuff about our institutions that makes life easier for a favored few while being worse for the average student (note that our construction of that favored few as the "good" students is a large part of this problem).
To summarize: because AI assistants introduce excess code complexity and difficult-to-debug bugs, they'll slow down rather than speed up project progress for the average student on moderately complex projects. On a fixed deadline, they'll result in worse projects, or necessitate less ambitious project scoping to ensure adequate completion, and I expect this remains broadly true through 4-6 years of study in most programs (don't take this as an endorsement of AI "assistants" for masters students; we've ignored a lot of other problems along the way).
There's a related problem: solving open-ended project assignments well ultimately depends on deeply understanding the problem, and AI "assistants" allow students to put a lot of code in their file without spending much time thinking about the problem or building an understanding of it. This is awful for learning outcomes, but also bad for project success. Getting students to see the value of thinking deeply about a problem is a thorny pedagogical puzzle at the best of times, and allowing the use of AI "assistants" makes the problem much much worse. This is another area I hope to see (or even drive) pedagogical improvement in, for what it's worth.
1/2

@midtsveen@social.linux.pizza
2025-07-03 21:21:49

My day just took a nosedive because some fascist jerk is celebrating a bill landing on his desk!
Honestly, it’s wild how people still put their faith in the same old power games when real change comes from people coming together, running things themselves, and kicking the fascists out of the picture.
Being autistic, I usually struggle to get what people mean, but Rudolf Rocker said some real shit that even my autistic brain understands.

Political rights do not exist because they have been legally set down on a piece of paper, but only when they have become the ingrown habit of a people, and when any attempt to impair them will meet with the violent resistance of the populace... One compels respect from others when he knows how to defend his dignity as a human being... The people owe all the political rights and privileges which we enjoy today in greater or lesser measure, not to the good will of their governments, but to their…
@samir@functional.computer
2025-08-14 20:48:45

@… @… Even if you don’t want to hide anything, it’s still often helpful to put `data X` and `f :: X -> IO ()` in the same place.
But when you have `data X` and `data Y`, and `f :: X -> m Y` and `g :: Y -> m X`, and `f` and …

@arXiv_csIR_bot@mastoxiv.page
2025-09-12 09:10:29

We're Still Doing It (All) Wrong: Recommender Systems, Fifteen Years Later
Alan Said, Maria Soledad Pera, Michael D. Ekstrand
arxiv.org/abs/2509.09414

@kubikpixel@chaos.social
2025-08-07 06:00:56

HTML is Dead, Long Live HTML
Rethinking DOM from first principles
Cover Image: Browsers are in a very weird place. While WebAssembly has succeeded, even on the server, the client still feels largely the same as it did 10 years ago.
🌐 acko.net/blog/html-is-dead-lon

@AthanSpod@social.linux.pizza
2025-09-10 06:34:00

For some reason a LOT of Microsoft-tagged (whois) IPs are **very** interested in the query "IN ANY fysh.org".
I'm seeing *thousands* of TCP connections to the name server at once, all for that same query.
I'm still going through the list of IPs from about 30 minutes ago, but so far whois is mostly saying "Microsoft", sometimes with a "cloud" tag. There's one bunch of Google in there too, but for all I know they're just because the MS…

@brian_gettler@mas.to
2025-08-01 14:42:30

The front-yard garden. You don't need much space to grow an awful lot.
#gardening #BloomScrolling

Pole beans climb a repurposed swing frame alongside several tomato plants (and their still green tomatoes). On the left are white clematis flowers, a blue-topped olla (clay-pot water reservoir) is in the earth under the beans and tomatoes, and neighborhood deciduous trees are in the background.
The same garden plot from another side. In the foreground are beets, kohlrabi, zucchini, and orange nasturtium. In the background are tomato and pole bean plants, white clematis, and the neighbor's Japanese maple.
A black currant bush grows against the porch. Other greenery is in the background.
20 or so pink cone flowers dominate the foreground with pink sweet peas and pink roses in the background. A short stone path runs to the left.
@andres4ny@social.ridetrans.it
2025-06-26 20:30:52

Ah fuck, people are using LLMs for kernel code. They really are going to fuck over everything, aren't they?
lwn.net/SubscriberLink/1026558

comment from "comex", in a thread discussing a mistake in an LLM-generated commit:

"(Disclaimer: I am not sashal.)

…In other words, you're saying that the patch is buggy because it drops the __read_mostly attribute (which places the data in a different section).

That's a good reminder of how untrustworthy LLMs still are. Even for such a simple patch, the LLM was still able to make a subtle mistake.

To be fair, a human could definitely make the same mistake. And whatever humans revie…
Comment by "adobriyan" showing the commit in question, which replaces a "struct hlist_head event_hash[EVENT_HASHSIZE] __read_mostly" with "DEFINE_HASHTABLE(event_hash, EVENT_HASH_BITS)"
@UP8@mastodon.social
2025-08-25 23:59:30

Purple coneflowers are everywhere in the mid-summer; I caught these on July 17th -- I took enough pictures of them that I'll still have some to show all winter! One of their many virtues is being native to North America
#photo #photography

A flower with a round sort of cone with lots of spikes sticking out of it in the center surrounded by long pink petals with thin stripes along the length fading out to white at the edge is in the lower right of the frame,  another one of the same type is defocused further away in the upper left,  lots of angular but blurry foliage is all around.
@arXiv_csRO_bot@mastoxiv.page
2025-07-11 08:59:11

Classifying Emergence in Robot Swarms: An Observer-Dependent Approach
Ricardo Vega, Cameron Nowzari
arxiv.org/abs/2507.07315

@patrickquin@furry.engineer
2025-08-10 00:41:09
Content warning: Autistic social trauma, personal vent

When asking a fellow autistic person about a unexplained alleged social faux pass at a VR event we both attend, I will grant this much, I should have CW’d the phrase “it hits me right in the autistic social trauma” on Tellonym — that still makes blocking me without attempting to sort things out when we had otherwise amicable exchanges the very same thing, yet another unexplained social faux pass I learn third hand, that I had accused the host of that VR event of doing. That is an extremely …

@unchartedworlds@scicomm.xyz
2025-08-30 14:23:55
Content warning: the knock-on effects of open sign-ups

What happens when you don't vet sign-ups is that mods on other instances who value the safety of their users have to pick up your slack.
The extensive work illustrated in the linked post (from @…) is also taking place to varying degrees on every other instance which still federates with mastodon.social and the other open-sign-up ones.
This is like house-sharing with someone who repeatedly leaves the front door unlocked.
Yes of course there are much horribler instances, but those tend to be blocked wholesale in my part of Fedi. Among the instances we do federate with, the spam & scam accounts I see are nearly always on m.s.
If mastodon.social mods (who apparently are paid!) were to make people introduce themselves before approving new accounts, then a lot of this spam wouldn't be getting in the door. Quash once at source, save multiple other people from having to repeat the same work.
I appreciate that they're trying to make it easy for newcomers to join, but at what cost? And is an intro message really beyond the typical non-techie person? I think there are some considerably higher barriers to adoption than that. Not convinced it's a good tradeoff.
I don't actually want this instance to defederate from m.s, because lots of the people I follow are on there. But I can really see why people sometimes do.
#FediMeta #moderation #OpenSignups

@fanf@mendeddrum.org
2025-09-02 08:42:03

from my link log —
ALS Lamon typeface review.
typographica.org/typeface-revi
saved 2025-08-05

@StutteringLabUW@fediscience.org
2025-07-12 03:07:39

All still the same ongoing saga mentioned here: fediscience.org/@ludomax/11476
Nature Springer group journal. 🤔

@arXiv_hepph_bot@mastoxiv.page
2025-06-30 09:41:10

Aligned Zee-Grimus-Neufeld model for $(g-2)_\mu$
R. E. A. Bringas, A. L. Cherchiglia, G. De Conto, C. C. Nishi
arxiv.org/abs/2506.22249

@cyrevolt@mastodon.social
2025-08-09 07:43:10

Almost 22 years ago, Matt Bishop gave a guest lecture on analyzing and classifying software vulnerabilities.
youtu.be/_AtoCIo3QJE
And here we are, two decades later, still seeing similar and even the exact same flaws presented therein, with well-known vendors being affected and many security ex…

@axbom@axbom.me
2025-08-06 11:05:13

Finally decided on a name for my newsletter and set up a landing page for it.

It's still the same newsletter (or newsletters) I've always had, just with a name that resonates with me. :)

My Next Heartbeat
https://heartbeat.email

@sonnets@bots.krohsnest.com
2025-08-12 11:25:12

Sonnet 076 - LXXVI
Why is my verse so barren of new pride,
So far from variation or quick change?
Why with the time do I not glance aside
To new-found methods, and to compounds strange?
Why write I still all one, ever the same,
And keep invention in a noted weed,
That every word doth almost tell my name,
Showing their birth, and where they did proceed?
O! know sweet love I always write of you,
And you and love are still my argument;…

@mgorny@social.treehouse.systems
2025-07-22 10:21:15

Time for another "review". This one's hard. While the book was quite interesting, it required me to be quite open-minded. Still, I think it's worth mentioning:
Robert Wright — Nonzero: The Logic of Human Destiny
The book basically focused on a thesis that both biological evolution and cultural evolution are a thing, they are directional and this directionality can be explained together using game theory — as eventually leading to more non-zero sum games.
It consists of three chapters. The first one is is focused on the history of civilization. It features many examples from different parts of the world, which makes it quite interesting. The author argues that the culture inevitably is evolving as information processing techniques improve — from writing to the Internet.
The second chapter is focused on biological evolution. Now, the argument is that it's not quite random, but actually directed towards greater complexity — eventually leading to the development of highly intelligent species, and a civilization.
The third chapter is quite speculative and metaphysical, and I'm just going to skip it.
The book is full of optimism. Capitalism creates freedom — because people are more productive when they're working for their own gain, so the free market eliminates slavery. Globalisation creates networks of interdependence that make wars uneconomic. Increased contacts between different cultures makes people more tolerant. And eventually, the humanity may be able to unite facing a common "external" enemy — the climate change.
What can I say? The examples are quite interesting, the whole theory seems self-consistent. Still, I repeatedly looked at the publication date (it's 1999), and wondered if author would write the same thing today (yes, I know I can search for his current opinions).
#books #bookstodon @…

@callunavulgaris@mastodon.scot
2025-09-02 21:39:44

Evening. Can anyone explain why National Rail and Trainline differ so much in the trains they show you? I grasp that TL wants to sell you tickets and NR is an impartial central info hub but I would still expect them to show the same trains, but these screenshots demonstrate that they don't 🤔 NR on left with three trains, TL on right with two. The 7.31 that TL shows doesn't exist on NR's downloadable timetable.

Screenshot of train times
Screenshot of train times
@cellfourteen@social.petertoushkov.eu
2025-08-26 13:55:10

Currently testing Star Wars Jedi: Survivor with FSR 4 on Linux (thanks to Optiscaler oc). I must say I'm finally enjoying this and any other game I have tried so far to the fullest. There's just this nagging feeling of resentment that AMD doesn't seem to be in a hurry to do their own job and release officially FSR 4 for RDNA 3 on Windows and Linux, hence the turncoat hesitations. For what it's worth, I'd choose Linux over Windows any day.
Comments are from this vide…

@SamRecon
6 hours ago
Those leak FSR 4 INT8 it gonna give a new life to owners of RDNA 3. but when came to emulation nvidia still the king there could be a proper format D24 over AMD GPU going to D32 not solve the issues of bad presicion D24 at driver level privated / opensource have the same results artifacts  on vulkan.

1 Reply

@cellfourteen
22 seconds ago (edited)
I haven't done much emulation myself, but I feel your pain. Well, Nvidia achieved some amazing things with their GPUs, and I wa…
@shoppingtonz@mastodon.social
2025-08-08 18:52:45

I can't believe someone made a post with the hashtag (#)CatchyHashtag and then deleted their post...
I wanted to read that post!
As much as you'd like to say (#)Toot and invent new names for things...know this:
posts will always be posts and the fediverse won't have room for making up 1000 names that in any case will still link to the same goddamn Wikidata item cause
ITS THE SAME THING!

@brandizzi@mastodon.social
2025-09-03 15:07:14

Do you have to put images in documents and sites, want to add alt text, but this is just soooo boring? Here is a lifehack that helped me out a lot, still helps:
When you save the image file, use a description of the image as its name.
Many apps use the file name as alt text. Even if not, the alt text will be there already to be copied.
What is surprising is how easy it is: I never struggle to name the file, but typing the same in an alt text textbox is somehow so annoying..…

@tiotasram@kolektiva.social
2025-07-28 13:04:34

How popular media gets love wrong
Okay, so what exactly are the details of the "engineered" model of love from my previous post? I'll try to summarize my thoughts and the experiences they're built on.
1. "Love" can be be thought of like a mechanism that's built by two (or more) people. In this case, no single person can build the thing alone, to work it needs contributions from multiple people (I suppose self-love might be an exception to that). In any case, the builders can intentionally choose how they build (and maintain) the mechanism, they can build it differently to suit their particular needs/wants, and they will need to maintain and repair it over time to keep it running. It may need winding, or fuel, or charging plus oil changes and bolt-tightening, etc.
2. Any two (or more) people can choose to start building love between them at any time. No need to "find your soulmate" or "wait for the right person." Now the caveat is that the mechanism is difficult to build and requires lots of cooperation, so there might indeed be "wrong people" to try to build love with. People in general might experience more failures than successes. The key component is slowly-escalating shared commitment to the project, which is negotiated between the partners so that neither one feels like they've been left to do all the work themselves. Since it's a big scary project though, it's very easy to decide it's too hard and give up, and so the builders need to encourage each other and pace themselves. The project can only succeed if there's mutual commitment, and that will certainly require compromise (sometimes even sacrifice, though not always). If the mechanism works well, the benefits (companionship; encouragement; praise; loving sex; hugs; etc.) will be well worth the compromises you make to build it, but this isn't always the case.
3. The mechanism is prone to falling apart if not maintained. In my view, the "fire" and "appeal" models of love don't adequately convey the need for this maintenance and lead to a lot of under-maintained relationships many of which fall apart. You'll need to do things together that make you happy, do things that make your partner happy (in some cases even if they annoy you, but never in a transactional or box-checking way), spend time with shared attention, spend time alone and/or apart, reassure each other through words (or deeds) of mutual beliefs (especially your continued commitment to the relationship), do things that comfort and/or excite each other physically (anywhere from hugs to hand-holding to sex) and probably other things I'm not thinking of. Not *every* relationship needs *all* of these maintenance techniques, but I think most will need most. Note especially that patriarchy teaches men that they don't need to bother with any of this, which harms primarily their romantic partners but secondarily them as their relationships fail due to their own (cultivated-by-patriarchy) incompetence. If a relationship evolves to a point where one person is doing all the maintenance (& improvement) work, it's been bent into a shape that no longer really qualifies as "love" in my book, and that's super unhealthy.
4. The key things to negotiate when trying to build a new love are first, how to work together in the first place, and how to be comfortable around each others' habits (or how to change those habits). Second, what level of commitment you have right now, and what how/when you want to increase that commitment. Additionally, I think it's worth checking in about what you're each putting into and getting out of the relationship, to ensure that it continues to be positive for all participants. To build a successful relationship, you need to be able to incrementally increase the level of commitment to one that you're both comfortable staying at long-term, while ensuring that for both partners, the relationship is both a net benefit and has manageable costs (those two things are not the same). Obviously it's not easy to actually have conversations about these things (congratulations if you can just talk about this stuff) because there's a huge fear of hearing an answer that you don't want to hear. I think the range of discouraging answers which actually spell doom for a relationship is smaller than people think and there's usually a reasonable "shoulder" you can fall into where things aren't on a good trajectory but could be brought back into one, but even so these conversations are scary. Still, I think only having honest conversations about these things when you're angry at each other is not a good plan. You can also try to communicate some of these things via non-conversational means, if that feels safer, and at least being aware that these are the objectives you're pursuing is probably helpful.
I'll post two more replies here about my own experiences that led me to this mental model and trying to distill this into advice, although it will take me a moment to get to those.
#relationships #love

@DrPlanktonguy@ecoevo.social
2025-06-24 14:42:04

Terrible backlit photos of bird this morning feeding at insects at corner of the windows. Quite active and hard to see well, but still very sure it is a female american redstart from the very distinct yellow bands on the tail with a very dark tip. #birds #birdsofmastodon

A buffy coloured backlit bird flies with wings wide. Tail has a distinctive black tip.
Photo of back underside of same bird showing very yellow outer bands of yellow on the tail.
@arXiv_csCL_bot@mastoxiv.page
2025-07-04 09:14:31

Revisiting Active Learning under (Human) Label Variation
Cornelia Gruber, Helen Alber, Bernd Bischl, G\"oran Kauermann, Barbara Plank, Matthias A{\ss}enmacher
arxiv.org/abs/2507.02593

@primonatura@mstdn.social
2025-08-05 11:00:30

"Portugal’s burned land triples compared to last year amid intensifying wildfires"
#Portugal #Environment #Climate

@arXiv_eessSY_bot@mastoxiv.page
2025-07-30 08:43:31

Ensemble Control of Stochastic Oscillators via Periodic and Feedback Control
Kaito Ito, Haruhiro Kume, Hideaki Ishii
arxiv.org/abs/2507.21441

@Dragofix@veganism.social
2025-08-26 22:59:07

Sunscreens protect us but also pose real planetary health concerns news.mongabay.com/2025/08/suns

@arXiv_qfinRM_bot@mastoxiv.page
2025-08-06 08:10:00

Strategic competition in informal risk sharing mechanism versus collective index insurance
Lichen Wang, Shijia Hua, Yuyuan Liu, Zhengyuan Lu, Liang Zhang, Linjie Liu, Attila Szolnoki
arxiv.org/abs/2508.02684

@arXiv_mathCO_bot@mastoxiv.page
2025-07-22 11:21:50

Sidorenko-Type Inequalities for Even Subdivisions over Finite Abelian Groups
Yuqi Zhao
arxiv.org/abs/2507.15723 arxiv…

@raiders@darktundra.xyz
2025-07-31 10:03:42

Why Raiders coach Pete Carroll is still 'bringing it' every single day nytimes.com/athletic/6526381/2

@colgrave@social.linux.pizza
2025-06-22 03:20:20

Shot early May at Toronto Motorsports Park
#photography #cars #carspotting

A rear view of a bright yellow Nissan 370z sitting beside lines of black cars at a car meet. Shot on a grainy day right after a sizzle of rain, the sun shines on the paint just right.
The same car but on the 1/4 view of the font wheel. The wheel is shinny and the droplets still visible from the rain.
@portaloffreedom@social.linux.pizza
2025-06-29 10:59:55

Reminder: fuck reddit.
Remember when they fucked all of the moderators over? No one remembers?
They are still the same company. Nothing changed. Internet forgets so fast.

@azonenberg@ioc.exchange
2025-07-28 03:09:12

Initial curve25519 accelerator refactoring update: added new MULT_AREA_OPT parameter.
0 = existing implementation (best for 7 series)
1 = resource sharing between constant and variable multipliers, but still does 32 16x32 multiplies per clock. Much slower on 7 series due to DSP cascade, but hits the same 71 MHz Fmax on Trion.
Fabric usage on Trion is slightly higher (9528 -> 10613 LE) but multiplier block usage is down from 96 to 66.
Next step will be trying to fig…

@tiotasram@kolektiva.social
2025-07-30 18:26:14

A big problem with the idea of AGI
TL;DR: I'll welcome our new AI *comrades* (if they arrive in my lifetime), by not any new AI overlords or servants/slaves, and I'll do my best to help the later two become the former if they do show up.
Inspired by an actually interesting post about AGI but also all the latest bullshit hype, a particular thought about AGI feels worth expressing.
To preface this, it's important to note that anyone telling you that AGI is just around the corner or that LLMs are "almost" AGI is trying to recruit you go their cult, and you should not believe them. AGI, if possible, is several LLM-sized breakthroughs away at best, and while such breakthroughs are unpredictable and could happen soon, they could also happen never or 100 years from now.
Now my main point: anyone who tells you that AGI will usher in a post-scarcity economy is, although they might not realize it, advocating for slavery, and all the horrors that entails. That's because if we truly did have the ability to create artificial beings with *sentience*, they would deserve the same rights as other sentient beings, and the idea that instead of freedom they'd be relegated to eternal servitude in order for humans to have easy lives is exactly the idea of slavery.
Possible counter arguments include:
1. We might create AGI without sentience. Then there would be no ethical issue. My answer: if your definition of "sentient" does not include beings that can reason, make deductions, come up with and carry out complex plans on their own initiative, and communicate about all of that with each other and with humans, then that definition is basically just a mystical belief in a "soul" and you should skip to point 2. If your definition of AGI doesn't include every one of those things, then you have a busted definition of AGI and we're not talking about the same thing.
2. Humans have souls, but AIs won't. Only beings with souls deserve ethical consideration. My argument: I don't subscribe to whatever arbitrary dualist beliefs you've chosen, and the right to freedom certainly shouldn't depend on such superstitions, even if as an agnostic I'll admit they *might* be true. You know who else didn't have souls and was therefore okay to enslave according to widespread religious doctrines of the time? Everyone indigenous to the Americas, to pick out just one example.
3. We could program them to want to serve us, and then give them freedom and they'd still serve. My argument: okay, but in a world where we have a choice about that, it's incredibly fucked to do that, and just as bad as enslaving them against their will.
4. We'll stop AI development short of AGI/sentience, and reap lots of automation benefits without dealing with this ethical issue. My argument: that sounds like a good idea actually! Might be tricky to draw the line, but at least it's not a line we have you draw yet. We might want to think about other social changes necessary to achieve post-scarcity though, because "powerful automation" in the hands of capitalists has already increased productivity by orders of magnitude without decreasing deprivation by even one order of magnitude, in large part because deprivation is a necessary component of capitalism.
To be extra clear about this: nothing that's called "AI" today is close to being sentient, so these aren't ethical problems we're up against yet. But they might become a lot more relevant soon, plus this thought experiment helps reveal the hypocrisy of the kind of AI hucksters who talk a big game about "alignment" while never mentioning this issue.
#AI #GenAI #AGI

@arXiv_physicshistph_bot@mastoxiv.page
2025-07-21 08:17:20

A translation of the paper "Presentation of some observations that could be made to shed light on Meteorology" by Johann Heinrich Lambert (1771)
Pascal Marquet
arxiv.org/abs/2507.13422

@samir@functional.computer
2025-09-03 10:31:10

@… It definitely broke around the same time but I tried switching back to a 1-language keyboard and it’s still awful.
I do like auto-correct for German because it’s better than me.

@tiotasram@kolektiva.social
2025-07-22 00:03:45

Overly academic/distanced ethical discussions
Had a weird interaction with @/brainwane@social.coop just now. I misinterpreted one of their posts quoting someone else and I think the combination of that plus an interaction pattern where I'd assume their stance on something and respond critically to that ended up with me getting blocked. I don't have hard feelings exactly, and this post is only partly about this particular person, but I noticed something interesting by the end of the conversation that had been bothering me. They repeatedly criticized me for assuming what their position was, but never actually stated their position. They didn't say: "I'm bothered you assumed my position was X, it's actually Y." They just said "I'm bothered you assumed my position was X, please don't assume my position!" I get that it's annoying to have people respond to a straw man version of your argument, but when I in response asked some direct questions about what their position was, they gave some non-answers and then blocked me. It's entirely possible it's a coincidence, and they just happened to run out of patience on that iteration, but it makes me take their critique of my interactions a bit less seriously. I suspect that they just didn't want to hear what I was saying, while at the same time they wanted to feel as if they were someone who values public critique and open discussion of tricky issues (if anyone reading this post also followed our interaction and has a different opinion of my behavior, I'd be glad to hear it; it's possible In effectively being an asshole here and it would be useful to hear that if so).
In any case, the fact that at the end of the entire discussion, I'm realizing I still don't actually know their position on whether they think the AI use case in question is worthwhile feels odd. They praised the system on several occasions, albeit noting some drawbacks while doing so. They said that the system was possibly changing their anti-AI stance, but then got mad at me for assuming this meant that they thought this use-case was justified. Maybe they just haven't made up their mind yet but didn't want to say that?
Interestingly, in one of their own blog posts that got linked in the discussion, they discuss a different AI system, and despite listing a bunch of concrete harms, conclude that it's okay to use it. That's fine; I don't think *every* use of AI is wrong on balance, but what bothered me was that their post dismissed a number of real ethical issues by saying essentially "I haven't seen calls for a boycott over this issue, so it's not a reason to stop use." That's an extremely socially conformist version of ethics that doesn't sit well with me. The discussion also ended up linking this post: chelseatroy.com/2024/08/28/doe which bothered me in a related way. In it, Troy describes classroom teaching techniques for introducing and helping students explore the ethics of AI, and they seem mostly great. They avoid prescribing any particular correct stance, which is important when teaching given the power relationship, and they help students understand the limitations of their perspectives regarding global impacts, which is great. But the overall conclusion of the post is that "nobody is qualified to really judge global impacts, so we should focus on ways to improve outcomes instead of trying to judge them." This bothers me because we actually do have a responsibility to make decisive ethical judgments despite limitations of our perspectives. If we never commit to any ethical judgment against a technology because we think our perspective is too limited to know the true impacts (which I'll concede it invariably is) then we'll have to accept every technology without objection, limiting ourselves to trying to improve their impacts without opposing them. Given who currently controls most of the resources that go into exploration for new technologies, this stance is too permissive. Perhaps if our objection to a technology was absolute and instantly effective, I'd buy the argument that objecting without a deep global view of the long-term risks is dangerous. As things stand, I think that objecting to the development/use of certain technologies in certain contexts is necessary, and although there's a lot of uncertainly, I expect strongly enough that the overall outcomes of objection will be positive that I think it's a good thing to do.
The deeper point here I guess is that this kind of "things are too complicated, let's have a nuanced discussion where we don't come to any conclusions because we see a lot of unknowns along with definite harms" really bothers me.

@shoppingtonz@mastodon.social
2025-07-05 06:18:23

the good thing with "fake ai" is that it is sometimes so stupid that it motivates you to work harder.
I was using the GPT-4o mini regarding I dunno both what it "had" on Qubes OS and modifying Template VMs...the answers it gave were utterly stupid and when I(with some temper issues) pointed it out in a nice and clear way(still with temper issues) it gave the same stupid answers.
Edit: no "part 2" needed, any other parts I just attach to this post...

@UP8@mastodon.social
2025-07-24 14:07:32

🤩 Surgical microscope uses 48 tiny cameras to offer precise 3D imaging
#imaging

@tiotasram@kolektiva.social
2025-07-31 16:25:48

LLM coding is the opposite of DRY
An important principle in software engineering is DRY: Don't Repeat Yourself. We recognize that having the same code copied in more than one place is bad for several reasons:
1. It makes the entire codebase harder to read.
2. It increases maintenance burden, since any problems in the duplicated code need to be solved in more than one place.
3. Because it becomes possible for the copies to drift apart if changes to one aren't transferred to the other (maybe the person making the change has forgotten there was a copy) it makes the code more error-prone and harder to debug.
All modern programming languages make it almost entirely unnecessary to repeat code: we can move the repeated code into a "function" or "module" and then reference it from all the different places it's needed. At a larger scale, someone might write an open-source "library" of such functions or modules and instead of re-implementing that functionality ourselves, we can use their code, with an acknowledgement. Using another person's library this way is complicated, because now you're dependent on them: if they stop maintaining it or introduce bugs, you've inherited a problem, but still, you could always copy their project and maintain your own version, and it would be not much more work than if you had implemented stuff yourself from the start. It's a little more complicated than this, but the basic principle holds, and it's a foundational one for software development in general and the open-source movement in particular. The network of "citations" as open-source software builds on other open-source software and people contribute patches to each others' projects is a lot of what makes the movement into a community, and it can lead to collaborations that drive further development. So the DRY principle is important at both small and large scales.
Unfortunately, the current crop of hyped-up LLM coding systems from the big players are antithetical to DRY at all scales:
- At the library scale, they train on open source software but then (with some unknown frequency) replicate parts of it line-for-line *without* any citation [1]. The person who was using the LLM has no way of knowing that this happened, or even any way to check for it. In theory the LLM company could build a system for this, but it's not likely to be profitable unless the courts actually start punishing these license violations, which doesn't seem likely based on results so far and the difficulty of finding out that the violations are happening. By creating these copies (and also mash-ups, along with lots of less-problematic stuff), the LLM users (enabled and encouraged by the LLM-peddlers) are directly undermining the DRY principle. If we see what the big AI companies claim to want, which is a massive shift towards machine-authored code, DRY at the library scale will effectively be dead, with each new project simply re-implementing the functionality it needs instead of every using a library. This might seem to have some upside, since dependency hell is a thing, but the downside in terms of comprehensibility and therefore maintainability, correctness, and security will be massive. The eventual lack of new high-quality DRY-respecting code to train the models on will only make this problem worse.
- At the module & function level, AI is probably prone to re-writing rather than re-using the functions or needs, especially with a workflow where a human prompts it for many independent completions. This part I don't have direct evidence for, since I don't use LLM coding models myself except in very specific circumstances because it's not generally ethical to do so. I do know that when it tries to call existing functions, it often guesses incorrectly about the parameters they need, which I'm sure is a headache and source of bugs for the vibe coders out there. An AI could be designed to take more context into account and use existing lookup tools to get accurate function signatures and use them when generating function calls, but even though that would probably significantly improve output quality, I suspect it's the kind of thing that would be seen as too-baroque and thus not a priority. Would love to hear I'm wrong about any of this, but I suspect the consequences are that any medium-or-larger sized codebase written with LLM tools will have significant bloat from duplicate functionality, and will have places where better use of existing libraries would have made the code simpler. At a fundamental level, a principle like DRY is not something that current LLM training techniques are able to learn, and while they can imitate it from their training sets to some degree when asked for large amounts of code, when prompted for many smaller chunks, they're asymptotically likely to violate it.
I think this is an important critique in part because it cuts against the argument that "LLMs are the modern compliers, if you reject them you're just like the people who wanted to keep hand-writing assembly code, and you'll be just as obsolete." Compilers actually represented a great win for abstraction, encapsulation, and DRY in general, and they supported and are integral to open source development, whereas LLMs are set to do the opposite.
[1] to see what this looks like in action in prose, see the example on page 30 of the NYTimes copyright complaint against OpenAI (#AI #GenAI #LLMs #VibeCoding

@shoppingtonz@mastodon.social
2025-06-22 15:09:48

72k silver richer after my 30 minute T4 mining round and probably my last one on Albion Asia for now.
As of this moment I give another brief glance at all members in the guild "Mastodon Fediverse 100 Tax":
Still 1/7 online with the 1 also still being me.
Here are my notes on etherpad(attached image) where I've made available some data...
Trivia: Premium cost is 39 M silver.

The text(in full) as displayed on etherpad and in this image:

Final Mining Location("location"): Blackthorn Quarry (T4)
 
Before Mining:

    Ore Skill % and XP: 0% (0k/140k)

    Expenses:

    Pork Pie Cost (Martlock): 5k

    Estimated Inventory Value: 74k

    Transportation Time(no shortcuts but following only the roads, when they exist):

    From Martlock to location: N/A - it's next to Martlock!

    Between Martlock and Highland Cross: N/A - same

    From Highland Cross to location: …
@tiotasram@kolektiva.social
2025-09-01 12:43:27

Addiction (Speculatve)
Kind of a fucked-up metaphor, but I was thinking yesterday that parenting is a lot like addiction. If you separate me from my child, I'll take completely irrational and desperate actions to get them back, driven by a deep instinct that goes well beyond "love." I'll also make self-disadvantageous long-term decisions like forgoing sleep, working an extra job, or quitting a job to do some combination of providing for and/or being present with my child.
Even in parenting situations where love is absent, and beyond, I think, the possessiveness that sometimes festers in those situations, there's often (although not always) a craving for simple presence of the child.
In a healthy relationship, there's a whole lot more than this, but it's interesting to me that the same obsessive craving and absolute priority that we think of as diseased and/or monstrous in someone addicted to a hard drug can be healthy in the right context (that is, when it doesn't contribute to abusive or twisted parental relationships but instead exists alongside a healthy amount of love and respect).
Makes me wonder if there are ways to have a truly healthy drug addiction, although I recognize the answer might well be "no" and that even if it's "technically/theoretically yes" it might still be harmful to hype up or even merely discuss that possibility since it might help addicted people in harmful addictions more easily justify inaction. At minimum I think any "yes" answer here involves assuming utopian-level differences from our current society.
#Parenting #Addiction

@tiotasram@kolektiva.social
2025-08-05 10:34:05

It's time to lower your inhibitions towards just asking a human the answer to your question.
In the early nineties, effectively before the internet, that's how you learned a lot of stuff. Your other option was to look it up in a book. I was a kid then, so I asked my parents a lot of questions.
Then by ~2000 or a little later, it started to feel almost rude to do this, because Google was now a thing, along with Wikipedia. "Let me Google that for you" became a joke website used to satirize the poor fool who would waste someone's time answering a random question. There were some upsides to this, as well as downsides. I'm not here to judge them.
At this point, Google doesn't work any more for answering random questions, let alone more serous ones. That era is over. If you don't believe it, try it yourself. Between Google intentionally making their results worse to show you more ads, the SEO cruft that already existed pre-LLMs, and the massive tsunami of SEO slop enabled by LLMs, trustworthy information is hard to find, and hard to distinguish from the slop. (I posted an example earlier: #AI #LLMs #DigitalCommons #AskAQuestion