skysight-inc/HackerNews huggingface dataset:
> Can you trust the reviews?

I can't tell if your comment is intended to be a counterargument (it seems to read that way) but you're actually agreeing with the point I was making:

Personally speaking re-branded products doesn't really bother me however the way reviews are abused does.

I think your link is a little disingenuous in the way it's worded too because I don't think Amazon actually remove or alter any reviews themselves. What I think happens is sellers contact customers and ask them to remove bad reviews in favour of a refund (or whatever). At least that was how negative reviews used to be purged a few years back. Of course you could still argue that Amazon should take a more proactive stance to customer bribery (just as Amazon should against fake reviews too) but I'm just directly addressing the phrasing "Amazon has altered or removed reviews" as seen in your citation.
I think there's a subtle fallacy about functional programming vs low level. Mostly due to the usual benefits of garbage collection style of memory management. But I find stack languages very functional in nature, it's when things grow and you start using lots of data structures that you lose sight of fp principles. Especially if you consider that FP Map/Reduce will be provably compiled to a cute choreography of localized (globally invisible) side effects. I'd like to claim that pre 80s programmers were doing a lot of that by hand without thinking about it.
Tenants are people who occupy land or property owned by someone else. Tenets are principles or beliefs, with the connotation that they're strongly held principles.

I agree with your point, I think there should be a new visible-source (semi-free?) license that includes commercial fees to make it easier for people to evaluate these things without stepping onto a mine.
RStudio with using Rmarkdown is also popular. Both workflows are language agnostic.
If you want to provide the source to your software, you put the code on the Internet and you're done.

You don't need to even choose a licence. That only comes in to play if you concern yourself with downstream users that care about licensing.

It really only becomes complicated when you want to release it and _also_ monetise it or restrict its use.

Licenses exist because of how this is ultimately at odds with how software actually works - it's basically legal DRM.

(I think licensing has valid uses in the current environment, but it's worth keeping in mind how absurd it is as a concept, it's basically a massive hack).
The argument could be made that compile-time processing is highly appropriate for the static inputs of a program, and, at the other extreme, obviously can't be applied to the dynamic inputs. (Terminology from https://en.wikipedia.org/wiki/Partial_evaluation)

Of course, the raytracer source code is the dynamic input of a compiler. The Futamura projection perspective suggests interesting options here for e.g. specializing raytracers in relation to particular scenes.
15TB 3.5-inch Western Digital Helium Hard Drive
Happy people aren’t great consumers. You only buy when you feel like your life is missing something that will get you to happiness.

Therefore, Marketers’ job is to create a lack in you. To make you feel “less than” as you are currently.

That does seem like the same thing a bully would do.
I'm afraid the incentives are not there - and we won't do any of those things - but at some point the system will bounce back, and hopefully it will self-regulate, rather than spiraling out of control. You can already see it happening, the hurricanes are getting worse and more frequent in USA, Italy and parts of Europe are hit by floods; An occasional reactor melts down. I'd say just enjoy the next decade as much as possible, who knows, maybe it won't last even that long.
Have you considered using merkle proofs? This way the data you will submit on-chain will be relatively small and stable and you can provide the proofs directly on the front-end / client side.
It's worth mentioning the debt Lua owes to Self and Newtonscript. An extraordinary amount of Lua's syntax and semantics is directly lifted from these languages. Newtonscript in particular seems to be a template for a great many of Lua's interesting features.

What drove me away from Lua is its philosophy of providing minimal tools in which it is possible, but never easy or convenient, to do work in various programming modalities. Polymorphism, namespaces and packages, arrays, unicode... these things all can be done, but require significant head-standing and in many cases a lot of boilerplate. Even proto-style OO, which you would imagine would be Lua's signature feature, involves lots of rigamarole compared to languages (like Newtonscript) where it is baked in and elegant.

I kept wanting Lua to pick a pony.

Throughout my usage of Lua, I've consistently gone back to Lisp, where I could change the language to make inconvenient things convenient when I needed to.
Yes and Power9.
The definition of abuse: use (something) to bad effect or for a bad purpose; misuse.

Advertising exists to get consumers to spend their money on a product they don't need (or a particular brand of a product they do need).

The argument is that if they're inspiring you to give them your money for something you don't need (in most cases, tricking you into thinking you do need it) that's abuse.
The resonant frequency of the atom is not arbitrary, it is a physical constant.

That's the key and the point: It allows to measure exactly 1 second anywhere in the universe because the resonant frequency of that atom is the same anywhere in the universe.

Compare with a previous definition of the second as a fraction of the solar day... A solar day isn't in fact constant and, in any case, once you leave earth it means nothing at all.
I get where the author is coming from but if your frontend team is already proficient at making SPAs then going SPA from the start actually simplifies things and buys you room to maneuver. The backend team can focus _just_ on the server side and the frontend team can just request the needed APIs. Additionally you can now reuse the API you just built with other systems. If your Widget Management Interface™ is a MPA and you your Automated Widget Building Factory™ to know when to produce more widgets then you just got a new project. If it's an SPA then you just give the Factory a user and have it use the API.
Lively (YC W17) Raises $11M in Series A Funding
I assume this is tech-shaming... some giant product owned by the (second?) richest person in the world has some obvious flaws. Trying to embarrass Amazon into fixing it (like Facebook, Twitter, et al) by buying one of the addons services that prevent blatant abuse is a strategy... and possibly a profitable one both as a customer and acquiree.
> Reddit's forced UI change

To be fair, it isn't really a "forced" UI change, as you may disable it in the settings or use "old.reddit.com" as URL.
A lot of items period are like this. I've seen my same fridge with an LG, Electrolux, and Whirlpool logo on it. My grandpa worked at a factory (here in the US) that made chocolate-covered cherries and mid-shift every day they'd have a switch-over on the boxes to switch which brand they were producing. The boxes were the only thing they changed, the chocolate and the cherries were still the same. Even car companies do that, the Chevrolet Aveo was made by Daewoo and branded as a Chevrolet, Daewoo, Holden, Pontiac, Ravon, and Suzuki.
> The revenue question is more a matter of ideology

Practically, it’s a matter of raising taxes or cutting services. That’s what makes it a tough platform to run on.
“Apache+Commons Clause” does imo not pretend that it is free/open-source. It's a free/open-source license combined with a restriction. I think this is or should be plain for everybody who reads the license.

In a way I can accept that 'Commons' is being used as a restriction in order to restrict monetary profit. With land, air and especially water there are also restriction in place. E.g. there is much critic if a multinational comes and bottles the water and (in some places) impairs local usage. Rules are then necessary.
tangle and weave, by knuth
So, here's the key text of the Commons Clause:

Without limiting other conditions in the License, the grant of rights under the License will not include, and the License does not grant to you, the right to Sell the Software.

> Ultimately, people want to keep their code open, develop in the open, bring in contributors, make it easy to adopt and audit their code, etc.

The Commons Clause doesn't really change any of that from the base license. It says so explicitly - "Without limiting other conditions..."

> They also want to eat and have a home.

This is the very thing that the Commons Clause tries to prohibit: "the License does not grant to you, the right to Sell the Software."

In other words, it's a way for the maintainers of a project to say that they get to sell the software, but nobody else does.

Which, hey, I develop proprietary software for a living, I'm fine with doing that in the general case. What I don't like is trying to mix that kind of restriction into an open source license. Because then what you're saying is, you want other people to contribute code, and you want to be able to benefit financially from those contributions, but you expect it to be a one-way street. There's a basic principle of fairness at play there.

If you want to do that kind of thing, I'd say it's much preferable to go with something more like the oldschool "dual GPL/commercial licensing" approach. Or, if it fits your needs better, something like one of the non-OSI Microsoft Shared Source licenses.
https://commonsclause.com/

>People can develop software out in the open and say "use it as it is, for free!", "use it as part of a new product, for free!", but also say "please do not sell this software as it is" and "please do not make and sell an almost-identical product using this software".

The Common Clause isn't about preventing shovelware, it's specifically about restricting the user's freedom to sell any derivative work--it straight up says in the 1st FAQ that it's to transition existing actually FOSS projects to non-libre software.

Also that's just the way SirCmpwn writes!
for Hammerspoon, we ended up building a fairly large abstraction layer that takes care of all of the repetitive/fragile stack operations for us, and it's improved our productivity significantly. Wiring up new Objective C objects to Lua is now very simple, but we can still fall back to the Lua C API when we need it.

There are still quite a few places in the code though, where some complex stack operation is happening and each line of C/ObjC is surrounded by a lot of comments that describe the expected state of the stack at each step, and there have been a lot of situations where I've ended up having to sketch the stack on paper as I'm reading code, to figure out why something isn't working.

So, I think I'd say that the C API is not comfortable to use, but it's also not very complicated. It's somehow managed to be simple, but hard, if that makes any sense.

Edit: If anyone cares, our Lua abstraction is all written in ObjC and is called LuaSkin. It lives in the Hammerspoon git repo, but doesn't actually depend on Hammerspoon at all, so could be extracted and used by others (it's MIT licensed). The API docs are: http://www.hammerspoon.org/docs/LuaSkin/Classes/LuaSkin/inde...
Hours... and natural resources, including fuels used to generate electricity and provide transportation for ads themselves and all the supporting industries. For instance, meatspace ads involve graphics designers, printing shops, producing and moving paints and paper, and moving the final ads to their destination (and then moving them to landfills).
I like R for many things, but Python just keeps getting more compelling, particularly given the excellent machine learning packages. As these sorts of toolchain elements get better and better, and as more people realize that there's a benefit to simultaneously training researchers to run code as well as stats, I suspect we'll start to see an exodus from pure R solutions.

The real question is when (and whether) new social scientist stats courses will start teaching Python stats toolchains, rather than R. That seemed to be an inflection point for R (as folks moved away from SAS), and could be for stats-centric Python too.
For now, it's very similar. The main difference is that OpenTimestamps is a bit more opaque. Basically, you get a confirmation, and then you can validate stuff on the site.

I try to provide full instructions how to verify everything without CryptoProof site at all, just tracing the transaction.
Yeah, I've had this discussion with a lot of developers over the years with regards to DRY as well. I've seen people refactor code to fix "DRY" problems and the code ended up increasing in size due to the "deduplication" and increasing in complexity. When asked, "well do not repeat yourself isn't about reducing LoC".

That is technically correct, but is it then about increasing code size and complexity? Sometimes
The argument really comes down to whether to curtail the liberty and veneration of independence that defines this century.
Introducing the PiDog2 (HW watchdog and power management for Raspberry Pi)
Well, we can see how well the Japanese are doing with their "scientific research" whale killing, which is really bad as they are using it as a excuse to continue the practice. Similar loopholes will be found here, for example: if i capture a rhino and send it to a farm for 1 week, is it now a animal that we can do "research" on? What about 1 month?
They were littering before, but not as frequently, as sometimes there was a bin nearby.
I get that, but I'm asking why we adhere to that? I'd be more than happy to change the definition of "Open Source" if it means that more companies will participate, as doing so won't entirely rob them of most of their income from that product.

In fact, I'd consider it a significant improvement over the concept of "open core" that has been becoming more and more popular, where the core 80% of a product is open source, but the last 20% isn't, making it so you need to either pay or build that last 20% yourself to use the software.

Contrast with an "open source, except you can't sell it", you'd be more likely to get the whole 100% of the software "open sourced" (as in all other aspects of open-source code, without the ability to sell it), people not using it for profit can benefit immensely, and those who are using it for profit can license it like anything else.

Ostracizing the latter because they don't adhere to strict definitions seems wrong, especially when pretty much all of the alternatives (aside from going full GPL/AGPL) means there is less code out there usable by people, and less users will have the ability to see the code they use.
Probably "frontend api dev" doesn't fully describe what I meant. The point I'd split the two roles is in an environment where it's a client side application being built as opposed to a website. That's the point when being good at making things look right visually, and making them work coherently and in a maintainable manner, becomes a skill in itself.
Just a consideration: Isn't it at least somewhat plausible that some products attract people who are satisfied more easily and thus write good reviews? In this scenario, lots of these reviews might be honest, but nevertheless not helpful to you, since the good review only implies that you will be satisfied if you are of a similar demographic.
Sorry for the slow response. I've used it only on Safari on my mid-2015 Macbook Pro 15" and it works well. Video is a little choppy but I blame that on my abysmal 10mbps upload speed on the host network. Desktop animations seem to work fine as well.
Privacy and security are intertwined. I believe Signal's decisions are based on the objective of making secure communications easy.

If they catered to what some people want (no phone numbers and federated network) then the regular user would have different options to use Signal. Which one is the correct one? Are they all the same? No. if you decide to develop your own client (like the LibreSignal example), do you trust that the client is secure? If the end application has vulnerabilities, then the communication privacy is compromised. That's why I say they're intertwined. Even Signal suffered from this same thing with the Desktop client. It is not an easy problem to solve, and that's why Signal does not want to have random people creating custom client apps and having them associated with the project, as it could confuse non-technical users.
Jupyter = Julia + Python + R
Andrew WK on why he listens to death metal:

> This was something I'd heard in other music, but only in small spurts—the screeching wail of James Brown, the frantic drum solo before a song's big finale. Usually, with other bands or artists, they would build up to a moment of intensity, like the crest of a wave, and it would hit hard, but be short-lived, fleeting. But it became clear to me as I listened to these death metal CDs, that this entire genre was based on extending that explosive feeling for an entire song, an entire album, an entire career—not just a quick crescendo or a peak that served to counter the bulk of more subdued music. In death metal, that high mark was starting point. It used the furthest extreme of other rock music genres as its base line, its foundation, and pushed forward from there. It's specifically designed to exceed excess. I was spinning in ecstasy.

https://www.vice.com/en_us/article/gvvb34/andrew-wk-on-death...
Great! Doctoral papers now in 300 characters. That may be possible in APL.
The depth of community
When you submit a message, I locally generate a file you can download (or copy to clipboard), that contains the message, hash and the release it will go to.

For text messages, I could also generate a special link. Good idea!

Edit: to follow up on your other question, I found a bunch of other services like that. Most of them are paid per proof, though.

https://stampd.io

https://proofofexistence.com

https://blocksign.com

https://www.blocknotary.com

https://opentimestamps.org (Free)

https://notary.bitcoin.com
I'm going to take a wild guess that it has something to do with electron de broglie wavelength somehow being resonant in certain lattice structures. Twists in graphene layers are known to create a morie pattern giving it a quasi-periodic structure at much higher length scales than simple atomic lattices. This is likely related.
How is it more opaque?
The article is a bit light on technical details. I found some specs here:

https://hpc.llnl.gov/hardware/platforms/sierra

Summary:

* 190,080 IBM Power9 CPU cores

* 17,280 NVIDIA V100 (Volta) GPUs

* 125,626 peak TFLOPS (CPUs+GPUs)
Careful with GZip and SSL, though - your payloads become vulnerable to the BREACH attack.
Having NLTK and SciKitLearn in the same environment as my stats tools is... tantalizing. And if I could write Markdown-to-TeX docs straight from Jupyter, rather than the R -> TeX tables/variables read into LaTeX I'd used before, that'd be a massive win.
Sure, but what's the end goal? That we all end up like caged chickens? We could probably cram in lots of people that way.
The Apache Foundation says it has gotten confused questions about this almost immediately and has asked that this combination not be used (it's own "brand guidelines" say to only use combinations like this if users are granted additional rights, not if the user is restricted further)
increasing control over every bit of tech and manufacturing in their entire stack.

Bandai might be a part of it, but it was also do to Adobe, Microsoft and Metrowerks basically forcing Apple into the directions that Apple didn't necessarily want to go -- Those companies could use the dominance of their tools to limit things that Apple may have wanted to do.
Can you beat Amazon at this point? If Amazon sees a threat, they can easily use their pricing power to force it out of business. They don't mind losing money as a means to pressure competition.

I think you'd need to play a different game altogether if you wanted to carve a new niche. What that looks like, I'm not sure. Maybe a shopping site that builds carts across various retailers and orders from the least expensive?
I like your observation on loss of intimacy.

I don't know if this properly translates to English, but in the Mexican metal scene (I don't know if this would generalize to other Spanish speaking regions) I've heard the term "comercial" used to describe when a band has gone mainstream, or "sold out"... It sometimes carries a similar connotation of being too popular.
This is true but who read these licence ? Agree, continue, next, move on btw I don't give a shit.
OP, are you on Android or iPhone? The advice would be OS specific.

In general, use encryption, with a good passphrase[1]. Fully power down your phone in dangerous situations, like when crossing the border or pulled over by law enforcement. Practice data minimization. For example, turn on Signal's disappearing messages feature - do you really need to look back more than a week at your chats?

Install a VPN since you'll be using a lot of suspect wifi.

And personally, I avoid logging into anything super sensitive (ex: retirement account) unless I'm at home.

https://theintercept.com/2015/03/26/passphrases-can-memorize...
"we aren't necessarily looking to disintermediate the banking system?"

I gather that.

It's just an emotive idea that will likely resonate with boty a) those interested in UBI, who more often than not believe the current financial regime is repressive and supports banks and b) cryto currency types who loathe banks and classical currency controls more for anarcho-libertarian reasons.

It's marketing.

Because you are not a classical product, you gotta be a movement, you want to give some emotive impetus! Most people need a call to arms against some faceless regime, it's more powerful than a call to charity. You can drop it after a while.

These motivational inclinations are real with the early adopting crowd. Anyhow, just something to think about in general, really.
> Ultimately, if I choose to, I will license my project however I want. If I want to restrict others from selling my product I will do so.

I don't think you're in the minority here.

> Calling it Apache 2.0 + Common Clause makes sense, it's an extremely well known license and it's easier to start there and then say "but with some restrictions".

You may be in the minority here. Marketing what you're selling under the name of something else with the deliberate goal of tricking and confusing your users is scummy.

You are free to make a bicycle sharing app, and you are free to refer to it colloquially as "Uber for bikes", but when you start putting your app in the app store under "Uber+ Bikes" then you're heading into scam territory.
I don’t know, but I found this: https://patents.google.com/patent/US8407580

Also: https://www.theatlantic.com/science/archive/2018/04/the-scie...

“The notebook interface was the brainchild of Theodore Gray, who was inspired while working with an old Apple code editor. Where most programming environments either had you run code one line at a time, or all at once as a big blob, the Apple editor let you highlight any part of your code and run just that part. Gray brought the same basic concept to Mathematica, with help refining the design from none other than Steve Jobs.”
15TB HDDs: Western Digital Unveils the Ultrastar DC HC620
good point. The story said they were saving photos. Maybe the site of choice didn’t optimize their photos for performance?
You could try protesting in China? Especially about their power plants.

https://www.wri.org/blog/2017/04/interactive-chart-explains-...