> So why is this met with warm welcoming arms especially when they are also going into cryptocurrencies?
In the other thread it was not: https://news.ycombinator.com/item?id=26713953
883 karma · joined May 21, 2012
In the other thread it was not: https://news.ycombinator.com/item?id=26713953
The guy didn't intend to mislead. He didn't even advertise the thing besides publishing it on the blockchain. People bought it from him without auditing it. I sincerely hope this would be a difficult fraud case to make.
The part of contract law you're citing is used to prevent e.g. predatory lending. I understand that it exists and what the precedent means, and I disagree that this is the same thing.
Put another way: I can't claim fraud just because I didn't understand/read/validate the contract language.
No solution is perfect, but this one keeps me sane.
It's one of the reasons I love stale closing bots. I don't have to pay attention to people who are dicks. I can just unsubscribe from their issues and let a bot handle it.
Denver != Pennsylvania, obviously, but perhaps it's a federal law? I don't really know where the rule comes from.
Anyway, overall takeaways working were: 1. everyone was super friendly and it was a great experience and 2. Denver+Colorado really have their shit together when it comes to elections. It's easy to vote, there's a paper trail for everything, and the default is by mail. Everyone should do it like we do.
Huh? I send messages to my friends daily using the API via https://gitlab.com/thefinn93/signald which is definitely third party.
I spent thousands of hours playing Diablo 2 through middle school-graduate school, developing bots, etc.; it's where I really got interested in computers and reverse engineering. My dad locked the disk in our family's safe at one point to prevent me from playing, and I've had hundreds of cd-keys banned from Battle.net. I'm sure many people out there are the same, but it's hard to overstate how much that one game influenced my life. Awesome to see that it was made by such a great guy.
https://snapcraft.io/docs/snap-store-metrics
> the store assigns an anonymous identifier, the device-serial, to every new snapd client it sees. This exchange usually happens when a new installation contacts the store, and the identifier persists for the lifespan of the machine.
> Systems running snapd will periodically make a refresh request to the store, checking the for the most recent release of each installed snap. At that moment, they inform the store of their device-serial along with a list of the currently installed snaps.
Can you elaborate more on this? (Maybe you can't because of the SEC?) APY of Ally is 1.0% right now, vs. 0.20%, so are the expected value of winnings 0.8%?
Late reply, but this might fix it:
And yet you did :)
Well, yeah.
> Current estimates are that about 12 million to 12.8 million Africans were shipped across the Atlantic over a span of 400 years. The number purchased by the traders was considerably higher, as the passage had a high death rate with approximately 1.2–2.4 million dying during the voyage and millions more died in seasoning camps in the Caribbean after arrival to the New World. Millions of slaves also died as a result of slave raids, wars and during transport to the coast for sale to European slave traders.
There are specific problems like you can't use syscalls which must be single threaded (a royal pain for container managers, since setns() is), but binding to a library like simdjson wouldn't have this problem.
No, they don't. There are many articles on the subject, here is one:
https://www.nytimes.com/roomfordebate/2015/04/16/what-are-co...
[alias] dfif = diff idff = diff grpe = grep