douglasg14b @ douglasg14b @lemmy.world

Posts

11

Comments

929

Joined

2 yr. ago

When the feds come for you for using it

• Is it open source? (No)
• Is it's publishing and build pipeline open? (No)
• Can anyone audit it? (No)
• Does the author make unreliable claims of privacy? (Yes)
• Does the author detail how data privacy and security is implemented? (No)

It's probably not a honeypot. But it's also likely to be negligent enough in implementation that it might as well be.

Lol, called it.

Incompetence and false bravado is all but guaranteed with development teams. Especially when it's closed source, not audited, and has minimal room for feedback loops.

Samesies

Had to use gett when I visited Tel Aviv a few years back. That's about it

The non-technical public is scared of the word "AI". When it has a whole spectrum of meanings and implications.

AI has been in use in medicine, engineering, municipal infrastructure....etc long before LLMs/GenAI.

Even new products today (Like those assistive exoskeleton legs) use (non LLM) AI to interpret and extrapolate bodily functions l. And wouldn't work without it.

It's closed source, and the build and publishing pipeline isn't transparent.

For me that makes this no different than a potential ICE honey pot

Only if you don't have the critical thinking to understand how information management is a significant problem and barrier to medical care.

Being able to research and find material relevant to a patient's problem is an arduous task that often is too high a barrier for doctors to invest in given their regular workloads.

Which leads to a reduction in effective care.

By providing a more efficient and effective way to dig up information that saves a ton of time and improves care.

It's still up to the doctor to evaluate that information, but now they're not slogging away trying to find it.

It's already in use responsibly.

And irresponsibly.

Turns out that you can't really argue the slope of responsibility as a way to shoot down a tool, when that's an individual choice of how someone uses that tool.

I love seeing these outside views from folks who aren't developers 🤣

Gen AI is pretty well integrated into development pipelines at this point. In ways that are subtle and quite useful.

Especially autocomplete as you write code, and boiler plate autofill. These used genai, are subtle and not necessarily intrusive, and are pretty widely integrated across the development ecosystem.

Like everything the poison makes the dose. The larger the dose of genai the more poison you are introducing into your work.

I mean, rule of law doesn't matter anymore anyways.

So... The states could just ... Ignore it? Just like the fed has been.

We don't need people that push a divisive narrative and push us away from each other.

This is the kind of shit astroturfing bots do, and it works, it's toxic AF.

GTFO out of here with this kind of toxic gatekeeping bullshit please.

Back to reddit with you!

Don't forget actual laws passing in poorly educated state legislatures banning "chem trails" 🤦

Moving/copying/reading/deleting tonnes of tiny files isn’t significantly faster on an ssd because the requirements for doing so are not limited by HDDs in the first place.

You mean the physical actuator moving a read/write head over a spinning platter? Which limits its traversal speed over its physical media? Which severely hampers its ability to read data from random locations?

You mean that kind of limitation? The kind of limitation that is A core part of how a hard drive works?

That?

I would highly recommend that you learn what a hard drive is before you start commenting about its its performance characteristics. 🤦🤦🤦

For everyone else in the thread, remember that arguing with an idiot is always a losing battle because they will drag you down to their level and win with experience.

This is like asking for a source for common sense statements.

HDDs are pretty terrible at random IO, which is what reading many small files tends to be. This is because they have a literal mechanical arm with a tiny magnet on the end that needs to move around to read sectors on a spinning platter. The physical limitations of how quickly the read right head can traverse limits it's random I/O capabilities.

This makes hard drives, abysmal, at random I/O. And why defragmenting is a thing.

This is common knowledge for anyone in it and easy knowledge to obtain by reading a Wikipedia page.

SSDs are great at random I/O. They do not have physical components that need to move in order to read from random locations they generally perform equally as well from reading any location. Meaning their random I/O capabilities are significantly better.

No, I shouldn't know, IDFC.

Let's have some actually useful YSK and not celebrity birthdays.

If we had control over the weak force:

• We can likely turn elements into other elements at will
• We can manufacture safe decay sources for a new class of nuclear energy
• We can probably create safe "decay batteries" tuned to their specific use cases. Batteries that last for tens of thousands the lifespan of current chemical ones.
• Potentially engineer with neutrinos. Imagine communication via neutrinos, you could transmit straight through the earth.

I mean, with control over matter like that, at the scale of electricity, Star Trek matter replicators would be a thing.

Yes, optimizing thinness is the antithesis of increased battery life.

These are all holes in the Swiss cheese model.

Just because you and I cannot immediately consider ways of exploiting these vulnerabilities doesn't mean they don't exist or are not already in use (Including other endpoints of vulnerabilities not listed)

This is one of the biggest mindset gaps that exist in technology, which tends to result in a whole internet filled with exploitable services and devices. Which are more often than not used as proxies for crime or traffic, and not directly exploited.

Meaning that unless you have incredibly robust network traffic analysis, you won't notice a thing.

There are so many sonarr and similar instances out there with minor vulnerabilities being exploited in the wild because of the same"Well, what can someone do with these vulnerabilities anyways" mindset. Turns out all it takes is a common deployment misconfiguration in several seedbox providers to turn it into an RCE, which wouldn't have been possible if the vulnerability was patched.

Which is just holes in the swiss cheese model lining up. Something as simple as allowing an admin user access to their own password when they are logged in enables an entirely separate class of attacks. Excused because "If they're already logged in, they know the password". Well, not of there's another vulnerability with authentication....

See how that works?