Hacker News new | past | comments | ask | show | jobs | submit | atarian's comments login

same just redirects me to login every time

>The mainstream media narrative does shape general public opinion, even for the smarter folks

If that’s true then everyone should be hating Luigi Mangione by now.


Have your plans changed with all the recent news about tattoo ink? Do you try to vet the ink?


Honestly?

I don't know. I mean I am still eventually going to get the tattoos, the meaning of all of the tattoos I want are important to me. So technically no the plan hasn't changed and I am actively talking to an artist about my next tattoo. But what exactly to do about this situation... I honestly don't know yet.

I don't even know how I would vet the ink. Just asking if they got it from Amazon sure, but I have to imagine that this is not limited to Amazon and we only learned about it due to scale.


Coming soon: Toxoplasmosis supplements


You're probably aware that cat poo is where one gets the parasite from, right?


Not everybody has access to it. Somebody needs to deliver it to the masses.


what is this a tower for ants?


Summarizing the legal terms for a new job offer


Trusting an LLM for anything to do with legal agreements seems like a terrible idea.


I'd trust an LLM more than my own interpretation.


trusting any idea that floats into your head is a terrible idea. you have to vet the ideation.


Thankfully humans are great at pattern matching and it's trivial for me to "vet this ideation":

LLMs are notorious for getting subtleties wrong, and in legal agreements like terms of employment the subtleties are often of material import. Therefore this is a bad idea.

If you don't want to read/don't understand the terms of your job offer then pay a lawyer. Asking JobOfferGPT is just asking for trouble.


I’m not sure it’s so black and white.

Reading yourself (at whatever level you are capable of and can tolerate) followed by asking an LLM to highlight any areas of the terms that are non-standard, may cause concern, could be restrictive, or might cost you later could help identify subtleties you might have missed.

Certainly it’d seem no worse and possibly better than just reading the terms, especially as a layperson.


And what do you do when your interpretation is correct and the LLM is incorrect, contradicting you, but you aren't sure who's correct and who isn't?


Seek better advice than the LLM, if the discrepancy remaining unresolved is problematic enough for you.


as a human *cough


Behold the wonders of the modern age!


Fine print with prompt injection. Thank god for this modern age!


I’ve used this several times and every time it accidentally scanned items from the person next to me so it didn’t really impress me as much.


Very interesting how similar the code for setting up the pipeline is similar to Metal.


That’s not a coincidence.


Wasn’t the design of WebGPU heavily influenced be Metal?

Or was it that metal came from a team in Apple that helped work on WebGPU?


Apple and Mozilla presented WebGPU as basically a clone of Metal.

Then the standard changed a bit, but it was still based on modern GPU APIs


Isn’t it nice when standards just happen to come together. I like the similarities, it certainly helps when switching from one to the other.


"Helped" is one way to describe it. "Sat down and kicked their feet until they got their way" is another.


What were the better options at the time?


Or standards bodies exist in practice to push vendor solutions on others.

Apple plays that game well.


I think the story was that Apple refused to ship/implement Vulkan drivers for their computers, and everyone was scared of this happening again with WebGPU, so Apple got their way with the design of WebGPU.


I think everyone is in agreement that the Metal API is pretty nice and there was little objection to making the WebGPU API similar (unless portability concerns dictated otherwise). The main disagreement was over shaders.


Not really. Many wanted Vulkan for the web. But Apple virtually had a veto, apparently: https://cohost.org/mcc/post/1406157-i-want-to-talk-about-web...


Yes, really. There were other reservations about shader compilation in particular from other participants, Apple wasn't alone in that department (e.g. asset sizes and needing to fork the format to maintain compatibility guarantees). They did demand a non-binary format, which sealed the deal on no SPIR-V. But it was not as simple as "SPIR-V/Vulkan was perfect and what everyone except Apple wanted." The shading language by far had the most discussion and iterations; none of the participants in contrast had nearly as many reservations about the structure of the API.


It would be weird if everyone wanted the same thing, Vulkan or otherwise, but it seems quite clear that where Apple wanted something and some others did not, Apple got its way more often than not.


Why would Gemini be at fault for customers withdrawing funds? Isn't Genesis at fault for not having the liquidity to support the withdrawals?


Looking closely, it seems like the lawsuit is purely about bankruptcy clawback.

Genesis wants Gemini to give back all customer withdrawals looking back 90 days from Genesis' bankruptcy. The idea is to add these withdrawals to the bankruptcy to be redistributed to all creditors.


Just because they are sued doesn't mean they are at fault. The court will decide fault.


Meh, it's just some stuff they extracted from your spit. I wouldn't get bent out of shape over it. Who knows, we might all get a decent payout from a settlement. You certainly won't regret when that happens.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: