mastodon - Link to source
This song is currently included as a demo project in Apple's #LogicPro. I'm too young to have used Logic 9 when that was out so I'm not sure about those, but of all the demos that came with Logic Pro X and now 11, this one's my favorite by far. Wonder what Apple will do with Logic 12 coming out about two weeks from now. youtu.be/eTkFpdLogEg

Ellie Dixon - Swing!

SWING SWING! - https://EllieDixon.lnk.to/InCaseOfEmergencyIDTHE SWING MUSIC VIDEO IS HERE!! ⚾Hope you have a ball with this one ✨I wrote this song when I was...
YouTube
#LogicPro

mastodon - Link to source

I’m SO excited to have finished my first round of prototypes for my new keyboard clicker fidgets!!

Remember Apples legendary iMac G3 computers from circa 1998-2005(ish)?! You’ll love my new project!

Custom designed keyboard clicker fidgets (with real switches) - available in rainbow 🌈 colours, printed with translucent filaments, topped with textured keycaps.

I strive to create creative, unique and useful fidgets. Let me know what you think!! (Listing coming in a few days!) #BrittBuilds3D

Strawberry Ice, Tangerine Ice, Lemon Ice, Apple Ice, Blueberry Ice, and Grape Ice. — Names all borrowed from Apple’s iMac G3 naming scheme. 🖥️

Rainbow coloured keyboard fidget toy with wrist strap.
Example of the ‘ice’ style for these keyboard clickers. The base transitions from light translucent blue to ice white with blue keycaps with various textures.
Photo of all of the colours: Strawberry Ice, Tangerine Ice, Lemon Ice, Apple Ice, Blueberry Ice, and Grape Ice.
Throwback photo , overhead, of the Apple iMac G3 computers
#brittbuilds3d
This entry was edited (4 days ago)
in reply to feld

pleroma - Link to source

≠ HER PENIS ≠

westbend.com/collections/toast…

Looks promising


West Bend QuikServe Compact 2-Slice Toaster with Extra Wide Slots and Cool Touch Exterior, in Black (77224)

The West Bend QuikServe Toaster browns bread in less than two minutes, one of the fastest toasters on the market. Items are held to toast, then released to bottom serving tray. Toast, bagel, and gluten free settings.
West Bend

mastodon - Link to source

The rise and fall of Stack Overflow is a case in point of the parasitic nature of LLMs. LLMs feed their models on places like Stack Overflow to be useful to users, so users flock to them to avoid the eternal snarky comments and just get an answer to their problem right away. But this is a dead end. No new answers will be generated if no one uses Stack Overflow or similar places.

What goes for Stack Overflow goes essentially for the whole internet. Like a mold growing on food, consuming it, and dying once the food is gone - LLMs will kill large parts of the 'old' internet before long.

Graph showing rise and fall of Stack Overflow usage between 2008 and 2026 in numbers of questions asked per month. There's a clear bell curve visible coming from 0 and going to 0.

mastodon - Link to source
Well over lunch, I discovered something funny. ChatGPT has access to Espeak inside its own sandbox environment, so it can run Espeak and generate IPA forms for what Espeak would output. Huge help. So, we fixed US English, next up is patching other languages. Both UK and US English now sound like they should in NV Speech player. Add-on link: eurpod.com/nvSpeechPlayer-2025…
(or original link works too, always latest there if you have a nice Browser like Firefox that doesn't cache downloads.)
Oh, and it also adds a dummy normalizer for empty IPA phonemes (that have no mapping right now.) We send a dummy 10-frames of audio in that case so speech shouldn't stall during say-alls.
This entry was edited (3 days ago)

Zach Bennoui reshared this.

in reply to Brandon Tyson

mastodon - Link to source

Tamas G

@BTyson @maysoncabo nah, but I think introducing US English letters changed some of the British ones, so the IPA tokenizer also needs to know the nuance between letter types per language and how ESpeak represents that data. Bleh. Sadly that DLL change wasn't much, it did make S's a bit softer which is probably enoough of a downside to not keep it for now anyway. But yeah, really don't know what beyond the ends-of-pitches clipping they did different in their inflection logic, but the entire player itself changed and that may have been enough to offset inflection differences too.
@Brandon Tyson @maysoncabo

mastodon - Link to source

#Catima 2.41.5 is out!

Catima is a simple Android app to store event tickets/plane tickets/store discount codes and more in.

Version 2.41.5 is the last iteration of the barcode encoding feature. It removes automatic encoding in favour of deciding encoding once on adding a card (extracted from pkpass files, otherwise ISO-8859-1) and then sticking with that. It also fixes some other bugs.

github.com/CatimaLoyalty/Andro…

Coming soon to an app store near you!

#IzzyOnDroid #FDroid #GitHub #GooglePlay


Release 2.41.5 · CatimaLoyalty/Android

Fix list widget sometimes opening wrong card Fix several bugs with shortcut handling Fix About activity not using pure black title bar in OLED mode Fully remove automatic barcode encoding detection...
GitHub
#fdroid #github #googleplay #catima #izzyondroid

IzzyOnDroid ✅ reshared this.

in reply to hipgnose

mastodon - Link to source

Sylvia

@hipgnose Oh, I didn't know you didn't have GitHub. I'm not gonna ask someone to make a GitHub account :)

Sadly implementing this turns out to be more difficult than planning because setting "android:showWhenLocked=true" forces it to always stay above the lock screen, even when "Settings -> Prevent screen lock" is set to off.

So unless there is a way to get AndroidManifest.xml to read the app settings somehow or another way to do this I fear this is not possible :(

@hipgnose

mastodon - Link to source

I'M BEGGING - ICE will track you with your phone

THERE IS A WAY TO NULLIFY AND STOP IT. Please read.

No promotions, no affiliation, not sponsored. I just use this service myself - they have no idea who I am. Please, I'm saying this to protect people I'm not benefiting from this post.

ICE with Webloc is able to scan entire neighborhoods and obtain mobile phone service data. On of the most critical pieces of information they log is your IMSI. Its like your car's VIN number, it identifies that device uniquely, and is the identifier the cell tower sees when your phone connects to it.

Now your IMSI and its location is logged, and cataloged to track your location over time; where you work, hangout, live, etc.

YOU NEED TO ROTATE YOUR IMSI TO MAKE THE DATA USELESS, and rotate it often.

My cell service provider does this automatically every 24 hrs. I only know of 1 cell provider that does it = Cape.co. There are other privacy focused providers, but they focus on minimal data collection (Cape does that too) and other security practices first.

Cape:

  • Rotates your IMSI every 24 hours (or you can refresh it manually)
  • Prevents man-in-the-middle attacks and Stringrays with Enhanced Signal detection. If the cell tower your phone attempts to connect to does not match to a known CAPE middle core, it will not connect. It also alerts in the app when suspicious connections are attempted and automatically blocks them.
  • Collects 0 PII - not even your billing info. They known the phone number they are servicing and that's it - not your name, address, DOB, nothing. If they receive legal demand to hand over your data they cannot, as they don't know who you are and never logged it in the first place.

Normally I'd include a coupon here, but to show you I'm extremely serious, I'm not going to include it. If you really want $10 off for life you can find a coupon somewhere, and they have a promotion rn, but I will not directly benefit from this post.

FUCK ICE AND THE FASCIST HELLSCAPE.

that is all. Visit: Cape.co

mastodon - Link to source

Minnesota is really putting the facts of the 'opposition' party on show.

Walz says "I'm gonna deploy the National Guard," but actually deployed the state troopers to protect the Gestapo.

Now Frey's up on stage saying that MPD is just too busy protecting the economy to deal with crimes against humanity, so all protesters should go home. Because MPD won't protect them.

This is not opposition; it's collaboration and gaslighting.

mastodon - Link to source
Welcome calm329 as #curl commit author 1431: github.com/curl/curl/pull/2032…

imap: skip literals inside quoted strings by calm329 · Pull Request #20322 · curl/curl

The IMAP response parser would incorrectly detect {size} literals inside quoted strings, causing protocol desynchronization. For example, a server response like: * 1 FETCH (BODY[HEADER] "Subje...
GitHub
#curl

mastodon - Link to source

It seems that py/cryptography's thoughts about OpenSSL (cryptography.io/en/latest/stat…) are doing the rounds at the moment.

I've not touched OpenSSL directly in a long time. In fact, it appears that the 10-year anniversary of that (imperialviolet.org/2015/10/17/…) passed by a few months ago!

So I've no direct comments on the piece but, a long time ago, I was in the position where I was landing changes in both OpenSSL and NSS (Mozilla's TLS library). OpenSSL was somewhat famous for having bad code. And, indeed, if you looked at it back then the functions were full of single-letter variable names with pointer arithmetic everywhere and context-free, somewhat scary comments. It wasn't outside the norm for 1990s C code, but I understand why people recoiled.

In contrast, if you looked at NSS code, it looked good! Consistent formatting (before clang-format), good naming, good comments.

But NSS had a PKCS#11 abstraction layer and, even after years, I never could understand how the control flow worked there. I would have to single-step in gdb every time to figure out where an operation grounded out into actual code. I was reminded of that when reading py/cryptography's descriptions of OpenSSL 3.0.

I had a pet theory at the time that, because OpenSSL was repulsive on the surface, it inhibited people enough that they couldn't add much deeper complexity. But NSS, with its invitingly clean-looking code, was understandable and then people had enough capacity left over to add deeper complexity.

There might be something to it, although you shouldn't discount the fact that entities who are willing to fund cryptography libraries often have demands that are contrary to clean code. Things like FIPS compliance and compatibility with a zoo of different accelerators and bespoke needs.

So rather it might have been that old OpenSSL was old OpenSSL because it was mostly unfunded. That meant that it looked pretty ragged, but also there weren't so many demands in tension with good design.

NSS was funded by interests that really cared about PKCS#11 compatibility so that you could use a super-expensive, certified-everything HSM with it. When OpenSSL got shocked into switching to a higher-funding model, that brought lots of those same sorts of competing interests, and then the incentives pointed towards adding slow, impenetrable layers of abstraction all over.

The State of OpenSSL for pyca/cryptography — Cryptography 47.0.0.dev1 documentation

cryptography.io

akkoma - Link to source

So @lwn is currently under the heaviest scraper attack seen yet. It is a DDOS attack involving tens of thousands of addresses, and that is affecting the responsiveness of the site, unfortunately.

There are many things I would like to do with my time. Defending LWN from AI shitheads is rather far from the top of that list. I *really* don't want to put obstacles between LWN and its readers, but it may come to that.

(Another grumpy day, sorry)

@LWN.net
⇧