ceargaest

[tʃæɑ̯rˠɣæːst]

linguist & software engineer in Lenapehoking; jewish ancom trans woman.

since twitter's burning gonna try bringing my posts about language stuff and losing my shit over star wars and such here - hi!


username etymology
bosworthtoller.com/5952

ThePhD
@ThePhD

With an integer overflow, no less. The thing we have ample knowledge and experience knowing exactly how to combat to stop these kinds of actively exploited problems,

Computing continues to largely be an enormous fucking mistake.

Meanwhile, we'll be writing about how we need to have "high impact libraries that help lots of users" and then give examples like CLI Parsing/JSON Parsing (https://isocpp.org/files/papers/P3023R1.html) before we sit down and go "we should have some standard library types / functions for integers...?".

v.v.v.v. cool prioritization we do, here!

Worse?

We keep calling ourselves software engineers, but engineers elsewhere advance their industry by analyzing failures and building up tools to stop those and make them standard industry practice!

But we'll just have the same 6 problems, on a regular spin cycle, for like 40 years.



curiousquail
@curiousquail

but everything the company does is actively hostile towards musicians like me and it really sucks to see it paraded around with free marketing.
Look at this shit!

A new threshold of minimum annual streams that a track must meet before it starts to generate royalties. The threshold, according to MBW, will de-monetize tracks that had previously received 0.5% of Spotify’s royalty pool.

Scenario: A musician has paid a distributor to put their music on Spotify. People (subscribed or ad-based) are listening to it - but Spotify has deemed it's not listened to enough for their threshold and therefore will not pay out for streams.
Full stop, Spotify is profiting off that music without paying the artist.

'but it's so easy to listen to any music I want at the push of a button' really fucking screwed us all.