dave

joined 1 year ago
[–] dave@feddit.uk 1 points 3 months ago

Interesting to see the difference 20 years of improvement in digital cameras have made too. I suspect 2004 was film, but it’s possible early digital.

[–] dave@feddit.uk 17 points 3 months ago (2 children)
[–] dave@feddit.uk 1 points 3 months ago

It annoyed me too for a while but it’s changing. I can’t find a definitive source, but I’ve seen a quote from MW from 2015 which had the original meaning. Now it includes “severely injure”.

https://www.merriam-webster.com/dictionary/electrocute

[–] dave@feddit.uk 3 points 3 months ago

Reminds me of when the BBC show Have I Got News For You replaced Roy Hattersley with a tub of lard after he failed to show up. Good times.

[–] dave@feddit.uk 10 points 3 months ago

Anything’s a regex if you’re brave enough.

[–] dave@feddit.uk 5 points 3 months ago

That’s because the explanation is often a bit disingenuous. There’s practically no difference between “listening locally” and “constantly processing what you’re saying”. The device is constantly processing what you’re saying, simply to recognise the trigger word. That processing just isn’t shared off device until the trigger is detected. That’s the claim by the manufacturers, and so far it’s not been proved wrong (as mentioned elsewhere, plenty of people are trying). It’s hard to prove a negative but so far it seems not enough data is leaving to prove anything suspect.

I would put money on a team of people working for Amazon / Google to extract value from that processed speech data without actually sending that data off device. Things like aggregate conversation topic / sentiment, logging adverts heard on tv / radio for triangulation, etc. None of that would invalidate the “not constantly recording you” claim.

[–] dave@feddit.uk 9 points 3 months ago

UK just went from announcement to election day in 6 weeks. But then, there wasn’t much point dragging it out any longer, was there Rishi ;)

[–] dave@feddit.uk 8 points 3 months ago (3 children)

It’s too late and I’m too many beers in to look this up, but I’d bet my next beer on the word pair ‘white people’ being considerably more prevalent than ‘while people’, especially around here. So you’re not necessarily in need of coffee, your brain is just doing its job—matching patterns and saving you fractions of a calorie to not have to actually pay attention to the letters.

[–] dave@feddit.uk 10 points 4 months ago

I suspect it’s not dissimilar to the way spam emails are full of typos and grammar errors. You may wonder why they don’t just get those fixed, but they’re specifically to filter out the people who notice them and dismiss the spam, as they (the spammers) are far less likely to successfully scam someone who is offended by the way the spam is written. They are a kind of first level filter.

MS are filtering out the vocal, knowledgable people who will cause problems next time they have some security breach or do something shady around privacy. Convert that relatively small number of people to Linux, and you’re left with a compliant and fully tracked customer base—far more use in the long run.

[–] dave@feddit.uk 1 points 5 months ago

I guess the company was providing a kind of UBI? Not sure what will happen when all of those non-jobs disappear…

[–] dave@feddit.uk 2 points 5 months ago (1 children)

My PhD was in neural networks in the 1990s and I’ve been in development since then.

Remember when digital cameras came out? They were pretty crappy compared to film—if you had a decent film camera and knew what you were doing. I fell like that’s where we’re at with LLMs right now.

Digital cameras are now pretty much on par with film, perhaps better in some circumstances and worse in others.

Shifting gear from writing code to reviewing someone else’s is inefficient. With a good editor setup and plenty of screen real estate, I’m more productive just writing than constantly worrying about what the copilot just inserted. And yes, I’ve tested that.

 

At least, I consider this a bug… :). It seems the scroll out of view trigger fires no matter which direction you scroll, and I think it should be only when scrolling posts ‘up’ off the top of the view.

For example, scroll a post until you can just see the first line of its title then scroll it off the bottom again. It will be marked as read when in fact you’ve only seen a few pixels of it.

 

Apologies if this is old and I can’t find it. I’m making the move (somewhat reluctantly) from Memmy, as I think development has stopped there which is a shame. Arctic is the closest I could find, and has a couple of key features like mark read on scroll that I really like.

But I’d love to see the community name above the post—gives good context for how to treat what you read in the post title, etc. I find I’m having to scroll down first then back up to read the content.

I couldn’t see an option anywhere for that—is it possible?

 
 
view more: ‹ prev next ›