Mastodon Feed: Posts

Mastodon Feed

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

They are trying the same bollocks with regards to browsers; arguing that they must be allowed to remain the sole producer of a slower, less secure, buggier browser engine for all of iOS because [ checks notes ] "security and privacy concerns".

Anyway, if you'd like for this to not be our collective future, go join @owa

Mastodon Feed

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

Apple's baseless harping on the "risks" of the DMA is a transparent attempt to blame the regulators for their own failures and create anti-regulatory sentiment. El Reg is not having any of it:

https://www.theregister.com/2024/06/21/apple_intelligence_eu/

Mastodon Feed

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

Feels like this should be a bigger part of the UK election coverage.

https://www.carbonbrief.org/analysis-cutting-the-green-crap-has-added-22bn-to-uk-energy-bills-since-2015/

Mastodon Feed

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

Because I'm a tab hoarder, I just stumbled back onto this post by @janmaarten, and *phew*; enshittification of a11y is next level late stage capitalism:

https://janmaarten.com/gaad-2023/

Mastodon Feed

Gargron ("Eugen Rochko") wrote:

Here's a glimpse of this month's most popular publishing tools. It's just the data for posts made in June on mastodon.social:

- Web 23.9%
- Jetpack 6.5%
- Mastodon for Android 6.3%
- Mastodon for iOS 4%
- Tusky 3.3%
- IFTTT 3.2%
- Ivory for iOS 2.5%
- IceCubes 1.1%
- Mona for iPhone 0.7%
- Elk 0.4%
- Phanpy 0.3%

The rest is divided up between literally a thousand other sources. It means around 66% of users are posting from 3rd party apps and integrations!

Mastodon Feed

Gargron ("Eugen Rochko") wrote:

One of the strengths of Mastodon is our API that allows 3rd party developers to create powerful integrations and full-featured apps on entirely equal footing with our own, with absolute confidence that there will never be a rug-pull. I've decided to check how the diversity of tools looked like in practice.

Mastodon Feed

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

davidgerard@circumstances.run ("David Gerard") wrote:

here is the extremely polite Wikipedia way to phrase "fuck off with the fuckin dick pics"

https://commons.wikimedia.org/wiki/Commons:Nudity#New_uploads

i mean in case you were wondering or anything

Mastodon Feed

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

basilhogan wrote:

Enjoy your #caturday

Attachments:

Mastodon Feed

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

freikampf.bsky.social@bsky.brid.gy ("Raubtier den Atem") wrote:

Attachments:

Mastodon Feed

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

WhiteCatTamer@mastodon.online ("Jay") wrote:

@skinnylatte @kieranmcguire @lzg “Imagine if you could make art without suffering!”
-BANG-
“WHERE THE -FUCK- DO YOU THINK ART STEMS FROM IF NOT THE COLLECTIVE ANGUISH OF THE WRETCHED HUMAN CONDITION AS IT CRIES OUT FOR SOMETHING TO HOLD ALL OF ITS EXQUISITE BLEAKNESS AND TERRIBLE JOY?”
“…how did your college professor get in here, this is supposed to be a private meeting?!”
“I’m a little more concerned about the fact she’s been dead for six years…”

Mastodon Feed

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

Free peripheral idea: a wearable that buzzes at kids every time they interrupt an adult.

May save sanity and/or relationships.

Mastodon Feed

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

GottaLaff ("Laffy") wrote:

Via Roger Parloff, 🪡 unrolled by the Thread Reader App:

Govt's reply last night, asking Judge #Cannon to stop #Trump from claiming that FBI wanted to kill Trump & his family, gives details about Ricky Shiffer’s 2022 attack on an FBI hdqtrs & a more recent threat to an agent working on the Hunter Biden case... #legal #JackSmith

https://threadreaderapp.com/thread/1804467137764868542.html

Mastodon Feed

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

Lightfighter@infosec.exchange wrote:

Livescience.com: Astronauts stranded in space due to multiple issues with Boeing's Starliner — and the window for a return flight is closing
https://www.livescience.com/space/space-exploration/astronauts-stranded-in-space-due-to-multiple-issues-with-boeings-starliner-and-the-window-for-a-return-flight-is-closing

Mastodon Feed

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

a friend just showed up, shoved a giant bag full of blueberries into my arms, and then drove off laughing… how delightful

Mastodon Feed

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

privacyint@mastodon.xyz ("Privacy International") wrote:

🚨Job opening: Legal Officer🚨

✅ Passionate about tech & human rights?
✅ Curious about how tech affects power & shapes the future?
✅ Ready to speak out for change?

Join our team! ❤️

📋 Job description: https://t.co/ICY3vtJRdj
📨 Deadline: Sunday, 14 July 2024, 11:59pm BST https://t.co/DjbzKVliD9

Attachments:

Mastodon Feed

Reblogged by zack@toot.cafe ("Zack"):

owa ("Open Web Advocacy") wrote:

BREAKING 🚨: Is Apple compliant with the Digital Markets Act with respect to browsers and Web Apps?

OWA's full 118 page report is out today.

Read. Share. Help save the future of the web!
https://open-web-advocacy.org/apple-dma-review/

Mastodon Feed

Reblogged by kornel ("Kornel"):

EUCommission@ec.social-network.europa.eu ("European Commission") wrote:

🛰️ Satellite data can be used to detect marine litter from space.

Scientists discovered they can use satellites to locate patches of floating litter, also called “windrows”.

By analysing images taken by Copernicus satellites, they found thousands of litter windrows in the Mediterranean Sea, ranging from a few hundred metres to 20 kilometres long.

This can facilitate clean-up operations, making our oceans cleaner.

Details: https://europa.eu/!xxpPDd

#EUGreenDeal

Attachments:

Mastodon Feed

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

graydon@types.pl ("Graydon Hoare") wrote:

Man, 50 years of neoliberal public investment-starvation just keeps delivering the hits. "Ontario closes its huge and unique palace of scientific wonders for children of all ages due to an unmaintained roof" is not in any way surprising, but it sure is some shitty icing on a shitty cake.

Mastodon Feed

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

piratenpanda@norden.social ("Benjamin") wrote:

Woop woop #darktable 4.8 ist da: https://www.darktable.org/2024/06/darktable-4.8.0-released/

Mastodon Feed

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

SrRochardBunson@universeodon.com ("Sir Rochard 'Dock' Bunson") wrote:

"Dammit I'm mad" spelled backwards is "Dammit I'm mad".
:thinkSpin:

Mastodon Feed

Gargron ("Eugen Rochko") wrote:

Been listening to #FourStrokeBaron's most recent album a lot this month.

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

#NowPlaying #NP

Mastodon Feed

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

sil ("Stuart Langridge") wrote:

Write HTML. If that’s not enough, also write CSS. If that’s also not enough, write JS. But you’d be surprised how much you’ll find that CSS is actually enough, if you’re good at it.

(But be sure to check the accessibility of what you’re doing. Adding a little progressive enhancement JS to fix that is correct behaviour.)

From: @slightlyoff
https://toot.cafe/@slightlyoff/112656907361237543

Mastodon Feed

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

Processing JS, e.g., is at least 3x more expensive per byte than HTML and CSS. That means that you can afford three times as much declarative content given a constant latency budget. Including network time, the multiple might drop to only 1.5-2x, but holy cow! In a world awash is shockingly slow Androids and low-end Windows machines, JS is (and always has been) special-occasion food.

Mastodon Feed

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

Going against the grain reliably blows up your spot because HTML and CSS are shockingly efficient UI compression syntaxes. You can't beat 'em, byte-for-byte, and ~30 years of engineering have gone into optimising them for the *specific* environment they thrive in: loading sites the first time, through a straw, on CPU-starved devices.

Every time it has looked like the environment would favour less efficient approaches, the world has changed in ways that disappoint post-scarcity naïveté.

Mastodon Feed

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

Today in "two things can be true at once":

  • web abstractions can be ugly and full of unpleasant limitations
  • deciding to YOLO it and move everything to userland (GWT, Flutter web, React, CSS-in-JS, some of the WASM alt-lang dreams) never works as well as going with the web's grain
Mastodon Feed

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

Nothing like going down a font subsetting rabbit hole because you discovered the font on your website doesn't have proper oldstyle numerals.

Mastodon Feed

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

jeffs@well.com ("Jeff Sonstein") wrote:

attributed to Cohen the Barbarian: “Never enter an arse-kicking contest with a porcupine.”

(translation: it is pointless to undertake a direct attack against an enemy extensively armed with efficient projectile weapons)

Mastodon Feed

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

Egg sac #2:

https://freethoughtblogs.com/pharyngula/2024/06/21/look-who-made-a-second-egg-sac/

Attachments:

Mastodon Feed

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

Amazing to see good coverage of @owa's latest. You can tell Apple isn't on the level with BrowserEngineKit and the contract requirements because there's *no universe* in which they would accept the same restrictions.

Safari isn't BrowserEngineKit-based, and that speaks volumes:

https://www.theregister.com/2024/06/21/eu_apple_owa/?td=rt-3a

Mastodon Feed

isagalaev ("Ivan Sagalaev :flag_wbw:") wrote:

#Python gotcha of the day: in unittest, `patch` decorators on a test class override those on its methods. It becomes obvious when you think how are they applied, but you intuitively expect and want the method ones to be more specific and override the more general class patching.

One workaround is to use `patch` via a `with` inside a method, which is going to run later then the class decorator. Any other ideas?