Mastodon Feed: Posts

Mastodon Feed

Boosted by glyph ("Glyph"):
hugo@treehouse.systems ("Hugo Slabbert ⚠️") wrote:

@glyph pathological overthinking in the age of the Not Thinking Enough Machine

Mastodon Feed

glyph ("Glyph") wrote:

also just gonna take a little victory lap here that I was so obviously correct about this particular architectural feature that the old style of API from before they fixed this issue is being slowly deprecated https://github.com/stripe/stripe-python/wiki/Migration-guide-for-v8-%28StripeClient%29

Mastodon Feed

glyph ("Glyph") wrote:

In 2018, I filed this issue:

https://github.com/stripe/stripe-python/issues/392#issue-292517299

In 2024, they implemented the fix:

https://github.com/stripe/stripe-python/pull/1200

In 2026, I once again have occasion to call this API, and I am pleased to discover that I get a regular old object with type annotations and stuff that I can easily partially mock if I want to for testing, instantiate multiples of for different accounts, whatever.

File that bug that's bothering you. Sometimes it's very much worth it even if it takes a while.

Mastodon Feed

Boosted by kornel ("Kornel"):
molly0xfff@hachyderm.io ("Molly White") wrote:

Often when there’s a “crypto winter”, it can take a little while before we start to see the fallout. But it seems to be emerging now, with three crypto exchanges announcing shutdowns in July, and multiple high-profile web3 projects closing up shop recently.

#crypto #cryptocurrency #USpolitics #USpol #CitationNeededNewsletter

The crypto industry is having an increasingly rough time as prices remain depressed. Bitcoin is hovering around its lowest price since autumn 2024, well below the “Trump pump” prices spurred by traders who hoped his inauguration would bring about a crypto renaissance. Robinhood reported crypto trading revenue down 38% and trading volumes down 35% year-over-year.1 Coinbase reported a net loss of $359 million and has stopped reporting trading volume entirely, claiming it “no longer reflects the breadth of our business”.2 At least three crypto exchanges — AscendEx,3 BitMEX,4 and BitMart5 — announced in July they would be shutting down. Other darlings from the web3 bubble have also announced they’re closing up shop recently: the Proof of Attendance Protocol [W3IGG], the Step App “move-to-earn” product [W3IGG], and MVMT Labs [W3IGG]. Poolin, a bitcoin mining firm that once accounted for a fifth of the global hashrate, his filed for bankruptcy [W3IGG].

Mastodon Feed

Boosted by kornel ("Kornel"):
rebane2001@infosec.exchange ("Rebane") wrote:

i love seeing creative qr code designs, so i made this guide explaining what tricks you can (and can't!) do with qr codes while still keeping them very much readable

have fun and make cool stuff!!

(ADVANCED) Guide to (not) fucking up qr codes ...while still making them look cool asf! by Lyra Rebane (1) Just have the QR code as-is, works the best! (2) But leave some white padding, otherwise some scanners can't scan the code! (3) Recolor the code using a light and dark color! (4) But don't invert the colors, some scanners can't handle this. Everything tested with: GrapheneOS, Samsung, iOS, Binary Eye Page 1/4
(1) Depending on the error correction you can cover up to 30% of the data in the QR code. This will make the QR harder to scan, but it should still work on all scanners. (2) But this only applies to the data and ec (green). You can also cover one of the format info parts (yellow) (3) Counter-intuitively, it also only applies to entire codewords (bytes) at once. Therefore you should make sure to never mess up over 30% of the codewords, even by a single pixel! (4) For example, I added a sneaky one pixel thick worm onto this QR code, which makes it unscannable! (5) But this QR code I added that chonky snake with a pride scarf onto remains perfectly readable! Page 2/4
(1) To scan QR codes, scanners will first find the three locators (blue) and then use the zebras (red) to create a grid over the code. (2) This means that you can stretch, skew, or rotate your codes because the grid still stays intact! Don't go too overboard with this, as some scanners can't handle extreme transformations. Pretty much just make sure that straight lines can still be drawn! (3) However, transformations that don't retain the grid - such as bends - can make the QR code unreadable. Keep this in mind when putting your QR codes on curved real world objects, such as posts and pipes. (4) If you need to draw curved lines for a grid, the code cannot be scanned. Note: the GrapheneOS stock Camera app might struggle with certain skews/rotations Page 3/4
(1) QR code scanners use the grid to pinpoint the center parts of pixels, which means that the rest of the pixel does not matter! (2) This means that you can shape your pixels however you want, provided that the middle stays unchanged. (3) Or you can fill the rest of the QR code with a different image or even pure noise! Note that a QR code like this could break after resizing or image compression, so use with caution! (4) As with the other tricks, this reduces scannability, so make sure to test it with multiple devices, especially if you’re combining all of the tricks into one ultra QR code! (5) This example still scans, but may not work properly or reliably everywhere! Page 4/4

Mastodon Feed

Boosted by glyph ("Glyph"):
AlSweigart ("Al Sweigart") wrote:

  1. What do you think of the term "prompt engineering"?
  2. Are you in software or IT or tech?
Mastodon Feed

Boosted by neatnik@social.lol ("Neatnik :prami:"):
macmanx@social.lol ("James Huff :prami_pride:") wrote:

No alt text = no boost. It's quite literally the least we can do to help those who need it. :janky_ty:

Mastodon Feed

Boosted by dysfun@treehouse.systems ("gaytabase"):
gsuberland@chaos.social ("Graham Sutherland / Polynomial") wrote:

squirrels are so good at climbing trees because they have branch prediction

Mastodon Feed

Boosted by glyph ("Glyph"):
dpnash@c.im ("David Nash") wrote:

@glyph @ildiavolorosso @Firesphere @pluralistic

Case in point follows.

For context, bear in mind I have been, and remain, extremely skeptical of the long-term utility of this tech ever since ChatGPT gave me a giant wall of bullshit in response to a question I knew the answer to, back in ChatGPT 3.5.

I was testing out a then-current release of Claude Sonnet to be sure I wasn’t creating a strawman argument about the state of the art based on older impressions.I handed it a simple programming task with a graphical component (plot some data in 2D or 3D). A program like Claude Sonnet might be able to generate code for the plot, but being a large *language* model, it can’t actually analyze the plots at all competently. After getting the “base” program from Sonnet, and having it come up with an expectedly garbagepants analysis of the plot, I had it tweak the parameters of the plot a few times so it was easier for a fellow human to see that the analysis was consistently garbage. I had Claude do this a few times before collecting enough plots to make the case clear: even with a syntactically clean program, it wasn’t able to comment intelligently on the output.

The biggest problem here was *not* that Claude produced crappy analyses of graphical data, though of course, that is indeed a problem.

The biggest problem here is that I didn’t read the program itself for a while and tinker with the output it gave — something I have done many times with programs I’ve been developing — but instructed Claude to do the tinkering itself.

I had gotten sucked into an approach to debugging things that I not only did not intend to at the start, it’s one I know I generally dislike. I’d let my hands come off the wheel and let Claude take over much of the actual interaction with my source code, *even though I actively believe this is a bad idea*.

I take this as very strong evidence that personal assessments of how you are *actually* using apps like these are fundamentally unreliable, and only non-subjective impressions, agreed on in advance by the people involved, are appropriate for making judgements about how useful and productive working with gen-“AI” coding tools actually is.

Mastodon Feed

glyph ("Glyph") wrote:

abbreviations can be useful for saving on typing but in documentation or formal writing, always remember to use long-form versions of technical terms to make them more readable.

for example,

ghost in the init .
ghost in the help
ghost in the clone
ghost in the fetch
ghost in the push

Mastodon Feed

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

getting set up for weekly local voice net on 50.250MHz USB

KX-3 transceiver, battery, and microphone on backyard table
6 meter band rigid dipole on a short mast & tripod

Mastodon Feed

Boosted by jonny@neuromatch.social ("jonny (nonvenomous)"):
GrapheneOS@grapheneos.social wrote:

They have their tool pretend to be a certain USB peripheral to target specific Linux USB drivers. These exploits are widely used including against journalists and political activists. Here's a technical article about a specific case of this in Serbia:

https://securitylab.amnesty.org/latest/2025/02/cellebrite-zero-day-exploit-used-to-target-phone-of-serbian-student-activist/

Mastodon Feed

Boosted by glyph ("Glyph"):
selectric@tacobelllabs.net ("liz ten eleven") wrote:

they call it single sign-on because YOU HAVE TO SIGN ON EVERY SINGLE GODDAMN TIME

Mastodon Feed

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

so i see there is a position open to work on element.

do you think i'd gain or lose points for adding a joke about unable to decrypt message?

Mastodon Feed

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

how can people say linux isn't enterprise ready when it's just as full of slop as enterprise stuff?

Mastodon Feed

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

@alina @gsuberland no, matrix is a distributed denial of service technology

Mastodon Feed

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

the JSON performance crowd

ah yes, you know you're in the very top tier of performance when you elect to use JSON.

Mastodon Feed

glyph ("Glyph") wrote:

apparently people are out here rocking 30g switches. i assume to do that you first have to replace all your fingers with carbon fiber wireframes first

Mastodon Feed

Boosted by jsonstein@masto.deoan.org ("Jeff Sonstein"):
antlerboy ("Benjamin P. Taylor") wrote:

Teaching with the wrong ends of the constructivist stick – Christian Moore-Anderson

https://christianmooreanderson.com/teaching-with-the-wrong-ends-of-the-constructivist-stick/

Mastodon Feed

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

oh goody, the ECB has a youtube channel and they have a video out about "taking care of your money".

which is good, because i'd ordinarily assume they were spaffing it up the wall on AI datacenters or something.

Mastodon Feed

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

so which egyptian god is it that's reborn tomorrow? i've lost track.

Mastodon Feed

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

guess which silly spattered boiling hot fat all over their chest, legs and face.

it fucking hurts.

Mastodon Feed

glyph ("Glyph") wrote:

c.f. https://pypi.org/project/MOPUp/

Mastodon Feed

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

testing backyard setup for tonight’s local voice net on 50.250 MHz USB. going to use a rigid dipole this time around

KX-3 transceiver set up on backyard table

Mastodon Feed

glyph ("Glyph") wrote:

keyboard update: 43g is _real_ light actuation force, I might have overdone it with these "fast" switches

Mastodon Feed

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

the first example was scottish soldiers' chest measurements

Mastodon Feed

Boosted by kornel ("Kornel"):
ellecordova@kilogram.makeup ("Elle Cordova") wrote:

Massive new data centers are being built across the country whether we’re ready for them or not. This is our moment to decide the terms at zoning meetings and utility hearings, in written testimony, and at the ballot box.

As hyperscalers come into communities to build these data centers, we should be asking: what tech will it be using, and how is it powered? Who pays for any necessary grid upgrades? What benefits does the surrounding community receive, and are those promises legally binding?

I have another video that will go into the details on all of this coming soon, so watch this space for more info!

Attachments:

Mastodon Feed

glyph ("Glyph") wrote:

it's that time again! upgrade your #python on macOS with `mopup`:

a terminal running pipx run --python python3.14 mopup and upgrading from 3.14.6 to 3.14.7

Mastodon Feed

Boosted by glyph ("Glyph"):
ronald@blog.ronaldoussoren.net ("Ronald Oussoren") wrote:

I’ve released #PyObjC 12.2.2. This release can be build with Xcode 27 and the Python 3.15 wheels where build with 3.15rc1.

Mastodon Feed

Boosted by brib@bribstodon.xyz ("brib :neofox_floof:​ :Nonbinary:"):
joepie91@slightly.tech ("Sven Slootweg, ("still kinky and horny anyway")") wrote:

reminder: all those 'homemade hacks' for looking at an eclipse (looking through CDs, sunglasses, etc.) are going to damage your eyes permanently, and you won't notice until much later. they do not work.

you have exactly three valid options:
- look through certified eclipse glasses from a known-good manufacturer for <30s at a time at most
- go to your local observatory, they probably have equipment set up to do this safely
- project the eclipse on the ground using small holes but DO NOT look at the eclipse directly, also not through small holes

anything else will leave you with eye damage for the rest of your life. you do not want eye damage.