Hacker Newsnew | past | comments | ask | show | jobs | submit | bigmadshoe's commentslogin

Is it consumerism to walk around the beach collecting pretty rocks to go home and put them on a shelf?

A rock is not a consumer good, so no.

And a rock is unique, nice to look at, did not cost you anything and kind of an appreciation of nature.

Enjoy your rock! (i'm sincere)


Naturally since people are buying things, technically they are consuming.

I mean that collecting a relatively small number of durable and visually pleasing objects isn't really the worst flavor of consumerism, even if it seems pointless to some people.

I agree we have a massive problem with over-consumption (most glaringly with things like fast fashion), but I'm not sure record collectors are a big problem.


If you're connecting through a VPN there is no way for your ISP to know that you're using TPB or any other website.


They can if you let DNS leak to their servers so make sure you really firewall your ship off


I know, that's why I use tor to get the links


The problem of track isolation is sometimes underconstrained, and so any AI system that does this will probably invent "neat parts" for us to hear that weren't necessarily in the original recording. It feels like using super-resolution models to notice details about your great-grandma's wedding dress.


Capital ≠ income


I’m really no expert on sharding but if you’re using increasing ints why can’t you just shard on (id % n) or something?


Because then you run into an issue when you 'n' changes. Plus, where are you increasing it on? This will require a single fault-tolerant ticker (some do that btw).

Once you encode shard number into ID, you got:

- instantly* know which shard to query

- each shard has its own ticker

* programatically, maybe visually as well depending on implementation

I had IDs that encode: entity type (IIRC 4 bit?), timestamp, shard, sequence per shard. We even had a admin page wher you can paste ID and it will decode it.

id % n is fine for cache because you can just throw whole thing away and repopulate or when 'n' never changes, but it usually does.


^ This


Square is primarily a payment platform so you probably have used your credit or debit card thousands of times with them already.


Yup. Credit. Or Debit. They can play with crypto behind the scenes all they want. That doesn't make it worth anyone's time.


Presumably they were paid for finding the bug and inn accepting relinquished their right to blog about it.


No, you relinquish the right when you agree to their TOS irrespective of if they pay you.


TOS != law

They will stop letting you use the service. That's the recourse for breaking the TOS.


I don’t want to pay for a lawyer to argue that for me. != law does not equate to ‘won’t come with a cost’.

I say this as someone threatened by a billion dollar company for this very thing.


Up until Van Buren v. United States in 2020, ToS violations were sometimes prosecuted as unauthorized access under the CFAA. I suspect there are other jurisdictions that still do the equivalent to that.


Being a sellout is weak and sad.


Yeah the needle in a haystack tests are so stupid. It seems clear with LLMs that performance degrades massively with context size, yet those tests claim the model performs perfectly.


As someone who abuses gemini regularly with a 90% full context, the model performance does degrade for sure but I wouldn't call it massively.

I can't show any evidence as I don't have such tests, but it's like coding normally vs coding after a beer or two.

For the massive effect, fill it 95% and we're talking vodka shots. 99%? A zombie who can code. But perhaps that's not fair when you have 1M token context size.



I'm the same and I tolerate vegan D3 (from lichen). Some people are sensitive to the sheep-wool derived regular D3.


I will give it a try thanks for the suggestion


How could price per token not be a concern for any “multi-billion” or “multi-trillion dollar” business? Do they just burn money to remain profitable?


You'd be surprised.


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

Search: