skysight-inc/HackerNews huggingface dataset:
The post this post links to a few times [1] is the more interesting one:

https://continuations.com/post/671863718643105792/web3crypto...

Still, it's unconvincing to me.

It argues web3 is about permissionless data. The problem with that is we already have permissionless data -- you can put almost any kind of data you want on a server and encourage people honor it. What they actually want is shared data, governed by rules that hard for anyone to change, and use that as scaffolding to build systems around consequential data. That's kind of interesting, but what happens when the rules conflict with reality. E.g., when the blockchain says you own the land but the law says someone else does? Now you could agree to make a blockchain database is the authority on something, even contractually, which would help it harmonize with laws to a decent degree. But that would be an individual decision and doesn't preclude scams, fraud, people acting in bad faith, etc.

Ultimately blockchains about data of any consequence will have to comport with applicable laws and regulations, just like everything else. The lack of flexibility likewise makes blockchain pretty useless for softer things, like social networks. (It's kind of silly to even bring up social networks in this context, but the post brings up Facebook.)
No sarcasm, that honestly sounds pretty cheap. About the price of a mid-level FAANG SWE.
We are talking about supposed "top" people who are critical hires here. Such offers go directly to Mark Zuckerberg and he has to approve them personally. And it was $3M in order to beat Google when someone I know got one of those offers but again I will eat all your delicious downvotes because that's not true, that's impossible (tm).

You're right about fungibles at each level though. But this article is about top people right?
All I could think of was Stripe off the top of my head, but maybe a good place to start would be https://duckduckgo.com/?q="completes+series+d" ? It's an interesting approach to filtering the job noise.
> I assume because you're using a remote socket connection from the client?

Yeah, it's common for all developers to connect to and query against prod postgres DBs via DataGrip or similar.

dqlite definitely looks interesting, but I worry it's a bit heavy given that our only use case for remote access is prod troubleshooting. I think I saw something recently where you could spin up a server on top of a sqlite file temporarily - that might be ideal for us.
Do you have teams that tend towards younger ages? I'd throw out there that what trends you see will be heavily dependent on that.
Indeed. If the bug were assigned to me, my inclination would be to respond: you're being paid -- so Use the Source, Luke.
>>> But something tells me that there could also be some positive effects from actually wondering about the behavior of others and how you treat them, even if it’s pigeonholing and preconceptions based on bogus research.

The problem is that "something good can come from lying to people" requires lying to people, and people believing the lie. If someone realizes that the whole thing is bunk, then the positive effect evaporates.
For whatever it is worth, Dorian Nakamoto (whom Leah Goodman claimed to be "The Face Behind Bitcoin"[1]) stays nearby - within the realm of possibility :)

[1] https://www.newsweek.com/2014/03/14/face-behind-bitcoin-2479...
You're correct, it's not an actual thing. I'm using it as a device to summarize the kinds of protocols and networks that are part of common visions for what Web 3.0 constitutes. There is no canonical "pure Web 3.0" vision I can point to. But http:// doesn't play strongly in most advanced visions, especially if you subscribe to the hypothesis that wallets will move on from the web browser for average users for security reasons. Speculatively, wallets could possibly become a kind of browser themselves, with http://'s utility becoming more marginalized eventually.

I'm not referring to Gavin Wood's specific conception or the associated Polkadot and its foundation's specific usage of the term. FWIW, I'm really trying to dissect the name and not the vision and perhaps not doing it that well. As far as I'm concerned, the usage of the term predates even bitcoin and originally meant Semantic Web. Content-addressable networks like IPFS or Arweave could be seen as related to that conception, but it's a bit of a stretch.
Regarding point 1, the belief that the earth is 6000 years old is much more commonly held by evangelicals: Of all the major religious groups in the U.S., white evangelical Protestants are the most likely to reject evolution. Nearly two-thirds (64%) of white evangelicals say that humans and other living things have always existed in their present form, while roughly one-in-ten white evangelicals (8%) say that humans evolved through natural processes.

You can see a breakdown here: https://www.pewresearch.org/fact-tank/2014/10/30/5-facts-abo...

The rest of your argument hinges on the rejection of evolution being shared among other groups and therefore being invalid, but as you can see, the rejection of evolution is largely a evangelical phenomenon.
1Password White Paper [pdf]
It is always the boards fault.
> Only a single process can write to the database at any time; it does not support concurrent writers.

Potential plus in cloud/container deployments.

> It is not client/server; a process must be able to fopen() the database file. NFS and SMB are options that can convey access to remote systems, but performance will not likely be good.

There are other possibilities given a bit of additional wrappers (over the db process) and federating nodes with some (consensus) protocol. It may actually be a good fit as the 'node-unit' for very large scale distributed metadata store that would benefit from relational DB semantics instead of basic K/V.
If you care about data normalization and data integrity then SQLite is going to be a much better choice.
> The core argument from economists for things like co-pays and against free healthcare is that absent a cost, people will over-consume health care

People dying because they can't afford insulin are usually not dying because they have insurance where the prescription co-pays for insulin is too high, but because they either are actually uninsured, are effectively uninsured because of a high deductible, or have insurance that works on a coinsurance rather than co-payment model.

And even then that's usually not really the problem, the problem is usually that they can't afford a more basic life necessity (often food or shelter) for themselves or their dependents, and voluntarily forego (or limit use of) insulin to afford the other need. Which is a real problem (and a real public economic policy problem), but usually not fundamentally a healthcare policy problem.

(On the other hand, it's often a problem where moral hazard arguments of the type at issue here contribute to the failure to solve, so the argument about that being the problem may still be correct by a less direct route then seems to have been intended.)
I tried to use GTD for quite a while. I abandoned it in favor of Timeboxing, using Work Clean for the precise implementation. I used org-mode to put it to use, it's flexible enough even though GTD was a big influence on its design.

https://www.amazon.ca/Work-Clean-life-changing-mise-en-place...
And already undone due to https://en.wikipedia.org/wiki/Wikipedia:Manual_of_Style/Disa... .
Groton St, Queens
>This is not true. When you invest in a venture, hold its stock for 60 days, and it pays you its profit, this income is considered "qualified dividends" and is subject to capital gains tax.

And? Okay, that's a) a special case, and b) confirmation of the point I was making that you get taxed on dividends (and on capital gains) only as one piece of total "capital income taxation". (The fact that something is taxed at the capital gains rate does not somehow mean that the dividends were not taxed, as you seem to be implying.)

>What are "profit tax" and "dividend tax"? These are not terms used in USA.

It sounds like you're just trying to be difficult and uncurious at the cost of a productive discussion.

I was speaking in the most lay, general terms. Profits are taxed. Dividends are taxed. In normal, ordinary usage of English, one can refer to those taxes as "profit taxes" and "dividend taxes", even if the technical term is different. (Your native language probably does the same.)

If I go through you posting history, am I going to find you always using the technical term?

Yes, the "profit tax" I referred to would be more technically referred to as the corporate income tax. The dividend tax also might have a more technically accurate term, similarly irrelevant to this context or point.

>Whereas ordinary dividends are taxable as ordinary income, qualified dividends that meet certain requirements are taxed at lower capital gain rates.

I don't know why you think this is relevant to my point. It just means sometimes the rate is different from "the" capital gains tax. In no way does it refute that the events of profit and dividend payment are subject to a separate tax, making the "capital gains tax" an incomplete picture of the tax rate on capital income.

If you agree with that latter point, then you agree with my comment, and you're just cluttering the discussion with misdirection and red herrings.
You mean using this hack: https://blog.robertelder.org/recording-660-fps-on-raspberry-... I didn't check that yet, but using the provided software and the flag (--framerate), I got the following timestamps:
# timecode format v2
0.000 8.329 16.657 24.987 33.316 41.644 49.972 58.302
Meaning that the camera is working at max. 120fps@640x480
AP Computer Science Principles Is Diversifying Computer Science
> When The College Board, the company who administers Advanced Placement (AP) courses and the SAT test to thousands of future college applicants each year, began developing the AP Computer Science Principles (AP CSP) course(...)The data also showed that students who took AP CSP were over three times as likely to major in computer science when they advanced to college. They are also twice as likely to enroll for AP CSA, a course that focuses on programming languages. Those increases were seen across all desired demographics, including first generation college students.
SQLite hides a ton of complexity that lives in the filesystem. It’s incredibly hard to do robust IO correctly with the APIs we have.

I almost always choose SQLite for persisting to disk over JSON files. It essentially removes a large class of bugs and is robust enough that I’m not worried about introducing new problems.
Tumblr is at war with Apple over ‘mature’ content on its app again
If ever you wanted to see a prime example of emotionally derived laws, look at how fast the Patriot Act was passed after 9/11. That body of legislation was sitting in a desk, waiting for the day where it could exploit our emotions about the situation. And their plan worked perfectly.
Do you have any proof for your claims?
Perhaps I should have made clear that I agree Amazon has some responsibility here in what kinds of things go onto their platform, but to me it seems like a problem with no obvious solution. Particularly as we move toward more dynamic digital assistants that scrape content directly from the internet, I think we will run into more situations like this. To me it just seems like the safest course would be to treat Alexa and other digital assistants more like a courier than a family friend. Parents let deliveries into the house all the time, but shouldn't leave children alone with the delivery person. I'd expect a courier service to fire their couriers (and take appropriate legal action) if they demonstrated problematic behavior toward children on their route, just as I expect Amazon to take steps to prevent what happened here with Alexa, but I worry that the inherent potential for danger is ever present.
The answer isn't microtransactions. Even if you solve the payment problem, Microtransactions involves huge amounts of new friction and creating an entirely new selling process and method.

I think the answer is in federation and mutually owned infrastructure.

People are comfortable paying Netflix/Hulu/Crunchyroll $10-15 per month. They don't have to worry about "do I want to watch this episode enough to spend 45 cents for it?" or "do I need to make and manage a whole new account just to watch a different show?" The fact the money eventually gets divvied up to content creators is handwaved away behind the scenes.

Federation gives other creators the opportunity to sell a similar one-stop-shopping experience you that. I could imagine, say, a subscription where I'd get through the paywall not just on my local newspaper, but the dozens of other papers that might print one or two articles a month that I care about. Or a Patreon-style service where you unlocked everyone for a flat fee, and they use analytics to determine how much of the fee goes to each creator each month.

The problem is that most of the content is living on third-party platforms. An OnlyFans or YouTube, for example, could offer a subscription around that model, but they'd just vaccuum up most of the revenue generated for themselves. The creators have to own the platform themselves to prevent that sort of diversion.
> I can imagine building a SAAS app where each customer has a “workspace” each as a single SQLite db

I did just that at my (now defunct) startup a few years ago. We were building a collaborative database query tool. The software we built used sqlite to keep a local db for storing user credentials, caching query results, etc. Bonus, we were able to have the local database file be encrypted protecting the data at rest.
I feel like we’ve looped. You wrote “A court order can't legally force someone to share incriminating information”. I gave an example where the court could force you to share incriminating information. Did you perhaps mean that a court order can’t force someone to answer questions that may incriminate them?
That's what centrist would mean in a vacuum, but in the US it generally means concern-trolling the Left while being a full-time apologist for the Right. I have yet to meet a "centrist" who is more concerned about what the Right is doing than they are about how the Left speaks about what the Right is doing (tone-policing and such).
Discord, Born from an Obscure Game, Became a Social Hub
A simple multi-profile Nix-flake deploy tool
That is... hilarious.
To be fair, an expert not answering a question that they don't know the answer to is a good outcome. The real expert for your question would be a researcher in the specific field, or perhaps the rare doctor who has taken an interest in following such research.
> replace money

Uh what?

> programmatic agreement enforcement

If writing logic were this easy, we wouldn't need the court system.

> creating financial assets that can't be controlled

I'm quite libertarian but again, not sure this is a feature.

> incentivizing things that need incentivizing and all that

Otherwise broadly known as a "marketplace"
Did you try SSH and using SQLite command line tool?
edit: krapp below me is right, I AM AN IDIOT. I just ran it through an anagram website and trusted it without even checking.

---

I always thought Satoshi Nakamoto was an anagram.

Antonomasias ~ Satoshi Nakamoto

Antonomasias: the substitution of an epithet or title for a proper name (e.g., the Bard for Shakespeare).

So it seems like a play on words, because Satoshi Nakamoto is a real name, and therefore a group might have wanted the creator to have a human name.
I used it for ETL process extensive which is great. I still don't know how people use it for concurrent writes like a simple ToDo webapp?
Ask HN: Cheapest/Industry standard for Load testing?
I've been trying to figure out what the more generally accepted services for load testing are. I am trying to test functionality across a couple sites. I'd like to find out how many concurrent requests I can support, how many concurrent submissions I can support, etc. What are some commonly encountered tools/methodologies in Industry?
this is one fugly text file:

https://docs.fcc.gov/public/attachments/DOC-378593A1.txt
One company controls the specification and reference implementation. These gimmicks tend to be "open" so contributions can flow in from anywhere, but the company has full priority and benefits by controlling the pace and final result.

Outsider contributions are submitted publicly, while features developed by the company start in secret and can remain secret as long as possible. The company's contributions are rammed through while outsiders contend with endless bikeshedding with no guarantee they will get anything they need.

In the end there is no sensible reason for any other entity to partner with the controlling company. The partner finds they are prevented from innovating while being bogged down by the "process." The controlling party then seeks to cannibalize the partner's product during this time by shelving any of their unique features and ideas. Once the partner moves on, the requisite changes and fixes to the specification are magically pushed through.

I wouldn't call this a core business model as much as an enhancement to one. Fundamentally it's an attention grift -- a bamboozle of complex rules, procedures and processes, cloaked in goodwill, and furnished by a large interest and future hope at any given time.
> Within the special maritime and territorial jurisdiction of the United States [...]

https://www.law.cornell.edu/uscode/text/18/7
Thank you! This is very actionable.
Personally, I think its fine if so-called "fact checkers" exist as long as their fact-checking isn't used to flag and censor people.
It's mostly because there is a demand for HA which requires multiple replicas. The moment you start going down that route you increase complexity.

Whether most things actually require HA is debatable, but a lot of businesses make it a core requirement and so it gets baked into the architecture. Personally I feel like most stuff would be better suited to having fast fail-over and recovery early on, but my advice rarely gets taken. Instead you end up with complicated HA architectures that nobody totally understands, which then (inevitable still) fall over and take hours to recover.
This is part of their Linux marketing plan. Make windows worse (challenging work!), and push people to Linux. End goal being irrelevance.

Very noble!
In the sense that use-package should pretty clearly be bundled with Emacs by now, sure. You don't need Projectile installed to use dashboard (I barely use Projectile, and have it turned off in my dashboard thingy).
Yeah, and it's difficult to stomach the gaslighting. "We haven't been pushing you at all! Why are you reacting like this!?"
Or harassed by that supposed journalist who tried to expose that old guy she tracked down just because he was Japanese and was formerly some kind of engineer
Also because it was imaging far infrared with wavelengths 100-1000 times that of visible light, the resolution of the optics was much lower and yielded kind of bla images (with a few notable exceptions):

https://www.herschel.caltech.edu/images
"In the Jan of 2009 when Hal and Satoshi were working on Bitcoin Alpha version, Hal encountered an error with the software and he posted the debug log to the mailing list."

The "dox" assumes that only three people were using Bitcoin at the time, and thus one of them must be Satoshi. That's a bad assumption, as Bitcoin was publicly available at that time, and was announced on the public cryptography mailing list, and we know for a fact that a few people tried it out early on.

The IRC initial seeding mechanism was _not_ mandatory to use, let alone full time. So it wouldn't be surprising at all if Satoshi wasn't using it.

"This is not a TOR exit node which implies that this is the IP address used by Satoshi on 2009-01-10 and he was in Van Nuys on this day"

It's not a TOR exit node in 2016, when this article is published. That doesn't tell us anything about 2009.
Very thoughtful comment thanks.

>>Or maybe just go back to typewriters and a good secretary or two.

https://www.theguardian.com/world/2013/jul/11/russia-reverts...
So there is a Child Tax Credit... of sorts. /s
BerkeleyDB maybe? DBM files used to be pretty commonly used on Unix boxes. Sendmail, for example, uses DBM files.

Or LMDB, LevelDB, RocksDB, etc, if performance is important.
Tetr.io
> Can't you run your queries in a copy of the data (eg.: a backup)?

That's essentially what we do: copy the file locally if we need to inspect it. It's slightly more cumbersome though.

> I think that'd be advisable even if you were running postgresql.

Connecting to live prod servers is definitely not a 10/10 on the "best practices" scale, but it works well for our business (trading), where there are small developer teams that also operate, no PII in the database, and critical realtime functionality isn't directly involved with the database anyway.
Sure, in present day United States it's largely an evangelical phenomenon.

In 19th century Europe and in modern central and south America, however, this is not associated with evangelical protestants, though protestants generally are more likely to have an issue with evolution.

Still, that's not really it - you've got a ton of irrational beliefs held by the catholic church. Unless you think those specific beliefs are what prevent constructive discourse?
I don't doubt the power of SQLite, but its difficult to see why its worth using over Postgres anyways.

This is what it takes to run a basic postgres database on my own PC (in a docker compose file):

postgres:
image: postgres:12.7
container_name: postgres
environment:
- PGDATA=/var/lib/postgresql/data/pgdata
- POSTGRES_PASSWORD=<pw>
volumes:
- ./volumes/postgres/:/var/lib/postgresql/data/

For someone who's completely allergic to SSH and linux, a managed Postgres service will take care of all that too.

SQLite seems simple in that its "just a file". But its not. You can't pretend a backup is just copying the file while a DB is operating and expect it to be consistent. You can't put the file on NFS and have multiple writers and expect it to work. You can't use complex datatypes or have the database catch simple type errors for you. Its "simple" in precisely the wrong way - it looks simple, but actually using it well is not simple. It doesn't truly reduce operational burden, it only hides it until you find that it matters.

Similarly postgres is not automatically complex simply because it _can_ scale. It really is a good technology that can be simple at small scale yet complex if you need it.
You can use emacs with vim-keys or any other config you like.

I never used the built in keys for cursor movement (I use the arrow keys), buffer switching (I define my own more efficient key), etc.
That is just not true.

https://www.irs.gov/businesses/small-businesses-self-employe...

It's not like it's a line item on your 1040 "Crime: $4000". It's just self-employed income.
I feel it's strange that this kind of hyperbolic response to a network adapter driver bug is considered normal discourse.
arp242 has an excellent post[0] about statically compiling sqlite for Go programs, which may be useful.

Isn't there some issue where SQLite basically has to be single-threaded in Golang programs, at least if you use the stdlib SQL library?

[0]: https://www.arp242.net/static-go.html
It would be funny if he's just a normal engineer somewhere who did this as a quick side project and won't come out as the creator because he's too embarrassed that he lost the keys.
A lot of people are blaming Yahoo!, Marissa Mayer, changing pricing, missing the boat on mobile, but I'm not convinced the model would have ever worked.
In the spirit of the discussion.... just as a screen tap counts as a 'zero-length' swipe, serving on the board of directors is a zero-degree separation. But it is still a degree of separation. /s