Has any streaming service trained a model to actually understand the music itself to work out what other songs would be of a similar vibe/genre?
My favorite band (vulfpeck, and more recently jack's solo stuff) often branch out into different genres, and it's a bit of whiplash when it goes to another song just because the artists are similar / appear together in other places.
At the risk of hijacking the comments, I've been trying to use OTel recently to debug performance of a complex webpage with lots of async sibling spans, and finding it very very difficult to identify the critical path / bottlenecks.
There's no causal relationships between sibling spans. I think in theory "span links" solves this, but afaict this is not a widely used feature in SDKs are UI viewers.
How big of an issue is this for GQL servers where all queries are known ahead of time (allowlist) - i.e. you can cache/memorize the ast parsing and this is only a perf issue for a few minutes after the container starts up
I’m not familiar with the work that OWASP does, other than the cheat sheet series.
The cheat sheet series is amazing - a great resource to defer to when you don’t know or want to think about how to do <x>, you just want to look up and implement the industry standard.
It’s a great reference, and I use it lot. <3 to the folks working on that :)
Maybe only kinda sorta relevant, but I interned at RefME for a summer - basically a Zotero competitor. There was a lot of value (for users) in scraping web pages to autofill to author, title, date etc so it could generate the references, something I started to work on (but then they got bought out so not sure what ended up happening)
Any I could've imagining this being a paid pro feature down the line
GraphQL makes a lot more sense at the scale of a big company where every team rewrites the same AJAX endpoint logic to fetch the same set of core entities (except in delightfully subtly different ways). Having “the one true” representation of your User object or Business object, but having the flexibility to fetch subsets of fields is huge.
And having a smaller team plug their page-specific types into the graph and just provide the foreign keys and have it “just work” is great.
GraphQL for me solves more of an organizational challenge rather than a pure technical challenge.
More security layers doesn’t always == better security
The “nth nth and nth” character of your password means they’re storing your password in plaintext, and Auntie Nora is more likely to have it written on a postit cos she can’t use a password manager.
“Name of your first school” etc type questions are obviously awful
My favorite is HSBC kept asking me to enable “voice identification” every time I phoned up as a “more secure way” of authenticating myself...which to me smells like a cat and mouse game between who has the better ML model. Oh also https://www.computing.co.uk/news/3010450/hsbc-voice-recognit...
When I moved to the US from the UK, I already had British HSBC accounts, so thought it made sense to open up an HSBC account and credit card. Got a $200 credit limit (thanks?), awful app, terrible customer service...eventually got fed up and closed all my accounts. Good riddance.
Also side note while I’m on the topic - to log into chase and do stuff, I enter my password. That’s it.
To log into HSBC or any other UK bank, you need to enter the 8th, 3rd and 19th letter of your password, app generated security token, digital security key password, the 822nd digit of Pi and the current orbital trajectory of Jupiter.