It sounds like that story could make a great blog post

Comments URL: https://news.ycombinator.com/item?id=50163131

Points: 5

# Comments: 0

You really need to not value your time at all to be willing to participate on those schemes.

Your proposal doesn't solve the actual problem.

Comments URL: https://news.ycombinator.com/item?id=48025100

Points: 1

# Comments: 0

Someone reaches out in Linkedin claiming to have full time and part time roles that match my profile. I say I could be interested in part time work and they immediately reply that there's a 4k monthly salary offer for 15-20 hours per week.

I reply that's half my hourly rate and they reply the client is almost willing to accept but wants to meet with me first. 1st red flag: no problem with doubling the offer

I accept and book a time with their technical person. 2nd red flag: the calendar had pretty much full availability

They tell me to complete a task before the meeting and provide a Microsoft Teams chat with someone from their team to talk about the task.

The person in the chat sends me screenshot of two issues. I ask if they have the code in github, to which they replied "github?". 3rd red flag

Then the same parson sends me a zip file and ask about my node version. 4th red flag

At this point I'm already suspicious and not willing to run that code on my machine. I get a fresh linux install on an old machine and download the code. I asked Cursor to find anything suspicious, and the only thing was a dependency mismatch between package.json and package-lock.json. I check the package present in package-lock, `json-map-source`, which is marked as a malicious package on https://security.snyk.io/package/npm/json-map-source. This package was removed from npm 18 days ago. Big red flag.

I check what's npm's resolution of that mismatch, and I find it would install `json-mappings`. I check on npm this package was created 18 days ago, and the first and only version is 2.3.8, which happens to be the same version flagged as malicious for the package `json-map-source`. Massive red flag

Furthermore, the package is not on git, it's uploaded by a throwaway email, and the README that is shown in npm list the yarn install command as `yarn add json-map-source` (the malicious package). In the code the package is just loaded and passed as middleware to an express app. The package has `sqlite3` as native dependency, which compiles native code.

As I'm writing this message I really don't see how this could be something other than a hack attempt, but I'd love to have someone else's input on this. Especially from people more knowledgeable about security than me, which is easy.

Thanks!

Comments URL: https://news.ycombinator.com/item?id=46366296

Points: 3

# Comments: 4

I've been improving it with feedback from other users, and I've just released version 2.

You can get it for free, which it's already the best way out there to manually change audio devices. You can also buy a license for $10 one time payment and the app automatically select your preferred device. There's a 1 week free trial for the license version so you can see if it does what you want.

Comments URL: https://news.ycombinator.com/item?id=46324625

Points: 3

# Comments: 1

How much was google revenue in 2003? It was 1.5 billions (2.6 in today's USD)

Not saying the price is justified, but the comparison is not very fair.

Unfortunately, as you say, it's very easy to freeze a GPU if you start doing more complex SVGs.

What are my options?

What? Where do you get this from? It's quite the opposite.

If anything, it sounds like ruby on rails should've been _the past_ of AI. But it clearly wasn't.

- macOS switches to HFP whenever the bluetooth headset is in use for both input and output. Interestingly, using the bluetooth mic and macbook speaker doesn't activate the HFP,

- bluetooth in general (not just HFP) seems to be designed to work under the constraint of tech from 20 years ago. Small bandwidths, small batteries, and small computational power,

- there are very nice codecs like Opus that are not used even though they've been working for over a decade.

From there I think the main problem is: - macOS should not assume you're in a call just because you're using the mic. There are a few scenarios where that's not the case and you might not care about low latency,

- better existing codecs should be used, but aren't for some reason,

- bluetooth specs should update the constraint they have to work under.