Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
jka
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
18 ms
·
121.
▲
Evidence Critical Systems: Designing for Dispute Resolution (2021)
(benthamsgaze.org)
2 points
by
jka
4y ago
|
1 comments
122.
▲
by
jka
4y ago
An important observation in this video (also noted by the oxide.computer team while they were building their foundations, if I remember correctly): What you think of as "your computing device" (laptop / phone / etc) is i
123.
▲
by
jka
4y ago
Around April 2020 I identified a project need for an "inverted search engine" - a system that would accept documents (recipe ingredient lines, like "three large onions") as input, and would match those against a dataset
124.
▲
Pluralization (P11n) – The Many of Plurals
(lingohub.com)
3 points
by
jka
4y ago
|
0 comments
125.
▲
Statistics: Percentage trust-in-government for each of the 38 OECD countries
(data.oecd.org)
10 points
by
jka
4y ago
|
2 comments
126.
▲
by
jka
4y ago
Ech, forgot the link, and now can't delete this post. It is: https://recipesage.com/
127.
▲
RecipeSage: FOSS recipe keeper, meal planner, and shopping list organizer
3 points
by
jka
4y ago
|
1 comments
128.
▲
by
jka
4y ago
I'm probably drawing parallels here that someone who has a better understanding of the academic world could validate or reject, but.. it feels a bit like there are more similarities emerging between published research and published sof
129.
▲
Takotsubo cardiomyopathy (broken-heart syndrome)
(health.harvard.edu)
1 points
by
jka
4y ago
|
0 comments
130.
▲
by
jka
4y ago
Strange; what I get from those articles is roughly: - Google tailors results to users, so it shouldn't be considered a common carrier - Google doesn't charge users for access, so it shouldn't be considered a common carrier -
131.
▲
Code Rush – documentary film about Netscape and the origins of Mozilla (2000)
(archive.org)
5 points
by
jka
4y ago
|
0 comments
132.
▲
by
jka
4y ago
Anyone feel like ratcheting up the optimism in the room for a change and trying to make this happen? (upvote, share with your network operator friends, ISP friends, mention it at relevant meetups, and so on) Yes, maybe it's a slightly
133.
▲
by
jka
4y ago
For anyone curious about potential open-source migration options given the prospect of uncertainty around VMware pricing and support: - xcp-ng[1] is a support-available fork of XenServer. Migration[2] can be performed using export to OVA f
134.
▲
Jumbo Stay
(en.wikipedia.org)
139 points
by
jka
4y ago
|
38 comments
135.
▲
by
jka
4y ago
See also: Pew's in-depth 2017 report: https://www.pewresearch.org/social-trends/2017/06/22/america...
136.
▲
by
jka
4y ago
Upvoted and agreed, that's a reasonable complaint. Can you provide sources that illustrate the absence of correlation after dividing the dataset? I haven't yet, although I did find this publication from Boston University positive
137.
▲
by
jka
4y ago
As far as I can tell, the 500k-3m figure is from an unpublished[1] report that was commissioned by the CDC - further validation could be helpful. There is also separate disputation of the figure in a report[2] by Harvard's Injury Contr
138.
▲
by
jka
4y ago
There is a correlation chart[1] of gun ownership and gun deaths per state for 2013 in this article: https://www.motherjones.com/politics/2015/07/gun-owners-stud... (correlation does not explain causation, but
139.
▲
by
jka
4y ago
Could you add a reference to some statistics around that? I found this, although it mostly contradicts your claim (with the exception of gun deaths due to assaults on people in the age range 5-34): https://web.archive.org/we
140.
▲
by
jka
4y ago
A theory: the number of firearms (which translates into how accessible they are) isn't a linear scaling factor in the problem. Comparative population could be relevant, although also doesn't explain the statistics you reference. T
141.
▲
by
jka
4y ago
Supporting dragontamer's claim regarding number of firearms: According to a report[1] by Small Arms Survey in 2017, there were an estimated 120 civilian firmarms per 100 people in the USA: https://en.wikipedia.org/wiki&
142.
▲
by
jka
4y ago
Nice - perhaps there's some kind of equivalence (or at least similarity) between lenses and those migrations. Thanks for the response!
143.
▲
by
jka
4y ago
Eh.. probably because I learned of lenses from Ink & Switch in the first place: https://www.inkandswitch.com/cambria/
144.
▲
by
jka
4y ago
Do you have any plans to handle schema changes for the content stored within the CRDTs as the clients evolve? (I've been puzzling over that question during some local-first dabbling; I have a feeling that lenses[1] -- or something like
145.
▲
by
jka
4y ago
Sorry, I was unclear: that's what I meant, too. You would find cookie consent options in your browser settings (for example, near "Privacy Settings"), and you would configure your rules there (with sensible defaults). You sho
146.
▲
by
jka
4y ago
Posted after searching around to find existing examples of source-control for low-code platforms (re: discussion at https://news.ycombinator.com/item?id=31508130 ).
147.
▲
Source Control in Node-RED
(binnes.github.io)
2 points
by
jka
4y ago
|
2 comments
148.
▲
by
jka
4y ago
Potential risks: - Vendor lock-in: if each low-code platform offers a different set of components and workflows, then it may be difficult to move to another if, for example, product cost becomes prohibitive at a later date. - Dishonest plat
149.
▲
by
jka
4y ago
The EU's ePrivacy Regulation[1] has (or had - it seems to fluctuate) a goal to move cookie consent into the user's browser settings. There has (perhaps predictably) been significant lobbying against that by entrenched industry p
150.
▲
by
jka
4y ago
Unfortunately the arguman.org site appears to be defunct, and the JavaScript from the archived pages doesn't appear to load correctly when using the Internet Archive's Wayback Machine at the moment, but I would refer you to these
More ›