skysight-inc/HackerNews huggingface dataset:
well here is the rub, paper ballots are useless unless you can prove who is voting and yet we have nearly the same people yelling about how unfair it is to require people to prove who they are to vote.

you cannot have one without the other if your intent is to protect the system and to be honest you only need paper ballots as a receipt to allow verification in case of suspected interference. we have already seen that some paper ballot designs are more prone to fraud than others.
Yep. Paper totally rules here.

1. like paper money, anonymous - my vote should be secret.

2. Hard to do large scale fraud or manipulation - not being efficient or automatable is a feature guys...

3. Physically going to the polls, voting in public, yet private at the end really makes it hard to put pressure on people to vote one way or another. Compare that to voting electronically at home or in church or at work....
Oh, oops, yeah, I misread "some" as "same". Denoting what contract they obey is just the name, isn't it? T1 and T2 are names of contracts.

I guess what you can't do by just using the contract name is say that two arguments must be of the same type. Nevermind.
According to your own link Crimean Tatars constituted 20%
of the population in 1939, nowadays the number 12-15%.

I wouldn't call it 'greatly affected'.
Also means "weak" (in concentration) in Estonian though
They're upvoted because people can't resist making the same tired "see? we are over-reliant on {Slack,Github,Cloudflare,etc}!" comments.
And yet it is the first place I checked to verify my experience
100% agreed! I came at it from the angle of someone asking me about real-world applications of dynamic programming. DP is usually covered only in an academic setting, so there's one more plus for seam carving.
Apple Workers ‘Regularly Hear Confidential Details’ via Siri Recordings
No, the poster above is right. There was an article about this a month ago or so. Anyways, the TLDR is that vehicles need to charge more often than just nightly and not just at the main depot. Transit agencies need to build heavy duty fast charging infrastructure scattered across many locations in the city. This has been so far a large upfront cost which holds transit EV expansion at bay.
"Most of these things result in having to write more code and does not really prevent you from doing something stupid."

I see this accusation a lot, but it does not manifest in my code after years of usage (and, yes, I know Haskell and am pretty good with it, so it is not a lack of knowledge of the possibilities).

If you write Go in Go, it's a pretty good language for production code. It doesn't give you all the goodies, but it's got some stuff of its own that's pretty cool, like it's baby structural typing (I think it is still massively underestimated how useful this is in practice over languages that require you to declare conformance to an interface, this has major second- and third-order consequences to code bases), the syntactic ease of composition, and the select statement (channels on their own, meh, but put them in a select statement and they're very nice). On the whole I'd say it's usually a bit less slick than Python but noticeably more pleasant to work with than Java.

If you, on the other hand, want to write Haskell in Go, or C++ in Go, or Javascript in Go, you're in for a bad time. Certainly from this angle Go is a nightmare. It's not a good idea in any language, but it's fatal in Go.

(I'll also say it's hard to put a finger on all the details why, but it's a really easy language to refactor in. I've been handed 5,000-ish lines of "sorta OK code" from various code bases in Perl, Python, Go, and Java in my job, and of the four, Go is by far the easiest to go into and brush it up to a higher quality level.)
Working with limited information means making decisions that might turn out to be bad ones down the line. I agree with your statement, but the opportunity cost of figuring out the exact right problem to solve is inaction, and inaction is often worse than making a poorly-informed judgement.
Intel's Xeon Cascade Lake vs. Nvidia Turing: An Analysis in AI
At least one person in this thread is smart.
Paper, general waste and compost are collected at the house.
This is what happens when mega companies take over, they helped to make github what it is today just like every body else, and banning them without any notice just to see them suffer, that's low
This is the first Slack outage where it's really affected me. My team has gone all-in on Slack as our communication mechanism. Though now I get to walk around and talk to people in person, so it's not all bad.
Let’s FaceApp to what our Internet has become
See, I love it. I work for a mostly-remote company and before Slack we had an IM product but it was a 1:1 chat. Having an always-on chat room for the entire team, knowing other teams use the same product and I can pop into their chat room, spinning up channels for project teams, etc. It's been a huge boost to our company.

And since so many companies have settled on the same solution, when I'm working with a client I can join their Slack workspace too. That cuts down on the numerous quick phone calls and long email threads that we used to have.

Slack vs Teams vs IRC vs anything else, I don't care. It's not about the product. But my company (and most of our clients) didn't have this capability before Slack even though IRC existed for decades, so I'm going to give Slack some credit.
I've worked in organizations where exchange is down more than it's up. shrug
"destroy the skynet" john connor
The difference is that instead of being 90 degrees, it's >120 degrees.
"Some workspaces might be experiencing issues with messages sending and loading."

(emphasis mine) Is that marketing-speak to lessen the loss of trust?
Everyone Is an Entrepreneur – No Excuses
I really like it because it covers just enough on a number of topics and ties them together. There are many books which can allow you to delve further into specific subjects.
No, Slack is more like sunlight, which also exhibits a single point of failure for most orgs. While the sun does go down, it somehow seems more reliable.
> Blockchain for voting sounds like a terrible invitation to a terrible party.

I'm expecting a ton of down-votes into oblivion for the following...

Because you can "chip it" doesn't mean you should.

And, just because you can apply technology to something, also doesn't mean you should.

Time and time again we are shown how vulnerable computers and digital data are.

Voting should be done on paper in local areas overseen by people from each party. They all watch the ballot box. They all see who comes in. Together, they count the votes in front of everyone else and tally them on a piece of paper. Then, they call to their higher-ups these numbers, and so on and so forth.

This is the safest way for anyone to vote.
I have the exact same feeling.
I was using generics extensively in C# particularly. I don't miss them at all after having spent a lot of time working with and understanding Go. I can't help but feel it will just make the language far less attractive in the long run.
Lots of interesting ideas in this -- well worth the read -- but in the competition for most productive paragraph, I would guess the following would win:

"Having built a variety of apps, I now have some template or framework that I can copy from a previous project when I start almost anything new. I use Torus, my frontend framework, for all my web projects, and I have a template I copy for my backend projects and static sites. I have a lightweight slap-on CSS library for making things look good with low effort with blocks.css, and these templates and copy-paste snippets make getting started super quick, even with fairly involved projects. I was only able to release RecruitBot in 6 hours because I could lean on both my frontend framework and a backend I copy-pasted from Studybuddy, and because I could easily deploy it on a server I had available for my projects. This might not be the most glamorous approach to starting new projects, but it gets me up and running quickly with a new idea, and that matters more than anything at the start. Having these battle-tested tools that I’ve used over and over again within easy reach has been the single most helpful thing in being able to push out MVPs and prototypes quickly."
There's no way to verify you voted a certain way, making buying votes less reliable.
Mailservers are also down very often.

When a company switches from their own e-mail server to hosted Google Mail, their uptime improves.
Australia is a good, almost-habitable place and the time difference is quite a trip. Sometimes talking over video chat with my buddy it's daylight in both the US and Australia and we both say "huh?"
It is appropriate if Slack being down affects software other than Slack. We can learn how to avoid outages in our own products happening due to 3rd party services such as Slack becoming unavailable.
Blockchain = PoW/PoS + signed Merkle Trees

Blockchain - PoW/PoW = signed Merkle Trees

A simple example of the latter is a Git repo. You can just require the commits to be signed. Easy to work with, no need for new code.
A Chinese acupressure point search engine (Chinese input only)
But we had to learn everything about email. Every damn bit.

SMTP, relays, MX-records, SPF verification, DKIM signatures, spam filtering, reverse-DNS, blacklisting, "Internet Message Format", throttling, MIME-encoding, email-antiviruses, bounces, headers, log-parsing, rate-limiting, greylisting, RFC standards (and that no one follows them)... And of course - about IP address reputation (more on that later).

Are there any open source tools to tackle some of these? Given the maturity of email marketing I would expect some pretty robust free tooling available.
But what about money?
No money, no fun, no company
Part of it is that, yeah, but part of it is the "nobody ever got fired by buying IBM" principle. In a corporate environment, you use what's established, period. Using something else is incurring unnecessary risk. Obscure languages have smaller ecosystems and talent pools, and ultimately, usually cost the company more money in the long run.

So sharpen your Java, C#, and/or Node skills.
It's not just about chat. It's also about the integration we have set up with many different applications. I'll check this out hopefully it integrates with stuff!
Those books weren't lived by millions of people.
Urge ICANN to reconsider removing .ORG price caps
Well, since ( according to ) Slack is the be all and end all of business communication and killed email, I can only imagine the absolute caos throughout the World that's going on right now.

I expect an economic downturn worst than the Depression in the 30's.
> but I'm not sure if complex designs like this are likely to be embraced by the community.

Spoiler alert: It won't.

If you think the Go community had a strong reaction with `if err != nil`, just wait for this one.
While email as a whole is indeed federated, email service for a single company is usually not, that is you have a single provider and when that provider happens to have technical issues your email might be down. While obviously you could use other provider (or even free email) almost immediately to send emails, you will not be able to receive/access emails that are sent to your primary address/domain until the provider resolves their issues.
Removing Slack app fixed the issue. Very weird coincidence.
It doesn't really matter how open and federated email is if all mail in/out of your mailbox has to go through one provider. If my company's Exchange server went down, email would stop.

Likewise for Internet service... if my local AT&T connection went down, it doesn't matter how open and resilient the Internet is, I'm not getting online until it's fixed.
The full picture looks pretty grim. I think y’all miss out on the bigger picture cus y’all hit these ideological blinders, very peculiar to HN.

For example, the article is very explicit about why recycling is not working - it has to do with economics - and y’all talking nonsense about GMO bacteria and energy use.
Definitely sarcasm
Why? I can read the grey for the most part, which doesn't seem too hostile.
Would the mistakes compile?

In many cases having a simpler less powerful language increases the amount of code you have to write. In this case it would be one place to fix, if the function was implemented for n different types then a mistake would have to be fixed n times. If Go Contracts reduce duplication they help at eliminating an anitipattern.
Try going and depositing $50k in cash at a US bank (let alone orders of magnitude more) and tell me it was a pleasurable experience. As someone who’s withdrawn and deposited multiple large amounts of cash (largest being in 7 figures range), I can say it’s a real pain.
Note that West Virginia did not pay for anything. The project was paid for by a rich guy [1], Bradley Tusk.

[1] https://statescoop.com/meet-the-guy-paying-for-west-virginia...
Many politicians do similar because there is little practical incentive to sacrifice the short-term for the long-term. You are typically judged by the economy here and now, not 15 years away. Thus, shorter-term decisions create debt and pension problems down the road.

Do we blame the person or the incentive system?

That being said, the world is entering a recession, and the USA cannot hide from that forever. It will catch up (or down) to it in a year or two.
"before that the inbound email is scanned for viruses (ClamAV)"

We moved away from ClamAV because it detected less than a tenth of virus samples we tested in practice. Simple things like EXEs, ISOs, VBAs and JS attachments.

VirusTotal uploads showed the same single digit detection rate for ClamAV.

I thought ClamAV was a better scanner, have things stagnated?
Now imagine if I'd copy-pasted that code for every builtin int and float type; there'd be ~ 36 errors.
There's a lot of misinformation in this thread, from GitHub CEO [1]:

"It is painful for me to hear how trade restrictions have hurt people. We have gone to great lengths to do no more than what is required by the law, but of course people are still affected. GitHub is subject to US trade law, just like any company that does business in the US."

"To comply with US sanctions, we unfortunately had to implement new restrictions on private repos and paid accounts in Iran, Syria, and Crimea.

Public repos remain available to developers everywhere – open source repos are NOT affected."

"The restrictions are based on place of residence and location, not on nationality or heritage. If someone was flagged in error, they can fill out a form to get the restrictions lifted on their account within hours.

More info is on our policy page: https://help.github.com/en/articles/github-and-trade-control...
"

GitHub is just complying with US trade law, it's not just because they're a US company, any company doing business in the US also has to comply.

[1] https://twitter.com/natfriedman/status/1155311121038864384
See, we're over-reliant on HN for making these types of comments!
I agree wholly on the second point though I will say as per the weight thing, the Model 3 actually weighs about 150 pounds more than a BMW 3 Series, its direct competition. Not a really light car but also not crazy heavy as claimed. The same goes for the Model S whereas its competition the MB S-Class, Audi A8, and BMW 7 Series all have similar weights.
They are heavy cars for sure, compared to most compact cars, but that's more of a factor of their size and class rather than their drivetrain. Future BEV's will gain range from lighter drivetrains so it's def. a goal they will be seeking.
> - How will identification work?

In my mind this is the hardest problem to solve.

> - What is the proof-of-work scheme?

It doesn't necessarily need to be proof-of-work and I'd think it makes sense to piggyback off a different trusted network of some kind.

> - How can you be sure that every vote ends up in the ledger? Transactions usually get lost and sometimes takes few tries to reach to miner.

Do transactions actually get lost all that often? In my experience, transactions propagate the network pretty reliably and quickly. You can then look at the number of confirmed blocks to reliably check if its in the ledger.

> - Most important property is that not a single vote should be traced back to its caster. Blockchain is all public, how are you going to anonymize everything? IP addresses of transaction owners are already open.

IP addresses aren't stored, and the actual transaction could be layered on something like Tor to prevent tracing. You could also have physical voting centers. The important thing is that individual voters can verify their own vote.

One big concern I'd have that you didn't really touch on is around management of keys. In addition to identity verification, how do you handle theft of keys? If a key is stolen, how do you handle disputes to whats in the ledger? I would trust tech savvy people to keep their keys safe, but what about people who don't understand technology?
Once you've become familiar with the basics of the language, I highly recommend taking a look at C++ Core Guidelines

https://github.com/isocpp/CppCoreGuidelines
Notably, like the proposed Australian bill, this rule in Belgium does not apply to transactions between consumers, e.g. a transaction between two individuals for a used car sale.

https://www.nbb.be/docs/ts/enterprise/activities/notes_coins...
When I learned Clojure, I also needed to learn about Maven, and POMs, and JARs, and the Java classpath, etc — and encountering all that stuff for the first time at the same time I was learning Clojure meant that I sometimes couldn't tell what concepts were part of Clojure, and what concepts were part of the Java ecosystem. This wasn't helped by the fact that the bulk of the "how to compile Clojure" documentation was written assuming a Java background (thus, assuming people would recognize the familiar Java stuff) — and when it wasn't, it didn't bother trying to explain what parts were handled by Java and why, because it assumed you didn't know Java so why bother explaining all that Java stuff that'll be foreign to you, let's just gloss over it. So the result was that I was unable to learn how to deal with the Java ecosystem parts of being a Clojure developer, so I had to go learn about the Java ecosystem separately.

Contrast with ClojureScript — It has the same problems as above, but substitute JS for Java and NPM for Maven, etc. I was coming from a web background, so I could easily tell the JS-world from the CLJS-world. That familiarity helped me tremendously in getting up and running.

The situation for CLJS is even better now with things like Planck and shadow-cljs (and Shaun Lebron's cljs/tool and Cuttle before them), since those tools mean you don't even need to install the JDK to get up and running with CLJS (as it should be, I'd argue). The situation for CLJ is a bit better thanks to the CLI tool. But the problems above could have been well handled by the classic non-technical solution: really, really good official docs. That's been getting better (thanks to Alex), but I'm pretty sure it's still going to be more painful to get up and running with CLJ or CLJS than Ruby, Node, etc., sadly.
Alternatively, there's also Rocket.Chat, which is also open source, you can self host it or pay for the cloud plans (which have special rates for certain kinds of organizations, such as OSS).

https://rocket.chat/

Disclaimer: I've done a GSoC project with them last year.
I agree with a lot of what you're saying but, to an extent, I find it even more mind boggling, because not only is the human capital misallocated to at best, local optimization of superficial products, but the market most likely would reward people if they focused on other problems.

It just feels like people are suffering from a massive streetlight syndrome where they feel like the only valuable thing they can contribute with their skills (which includes the ability to control unprecedented computing power) is more inconsequential mobile apps.

It reaches an even more ridiculous point when you consider that Silicon Valley is considered "hubristic" by a lot of pundits. What?! No! Silicon Valley's ambitions are underwhelming at best. We should expect a lot more from it.
This looks like blogspam or collecting a bunch of blogspam articles and turning it into a book.
Here's my experience in Germany:

My polling station is less than 200m away. I have never waited more than two minutes to vote. All voting is with a pen on a paper ballot.

Once the precinct closes, you are allowed to stay and observe the counting. Because each polling place serves only a couple hundred voters, it is easy to follow the counting. As long as it is possible to do so without interfering, everyone can observe so closely they can read the actual ballots and verify that they are sorted into the correct piles. You can then watch the counting of those piles close enough to verify the count.

Later, you can go online and look up the row for your precinct in a spreadsheet.

This is end-to-end verifiability, and it is neither expensive nor unable to scale: A national election in Germany will see about 40 million voters.

What's most important: Unlike blockchain or any other online voting scheme, the whole process is easily understandable by everyone.

In times were every institution is suspected to be corrupt, being merely safe is not enough. It needs to be safe in a way that does not rely on experts in cryptography to say so.

I have seen only one valid objection to using this process in the US: It is far more common there to have elections with dozens of individual races and ballot issues. Germany usually has just two individual questions to be voted on, and maybe five when local and national races fall on the same day. Considering this, it would still be possible to use the process for the top X races on a given election day.
One with dirty dishes laying everywhere, one neat and tidy.
> Worried delivery drivers are eating orders?

Well, I wasn't …
Charging infrastructure seems likely to be a bottleneck, too. Not everyone can charge at home (on-street parking, apartments, etc). And then there’s the demands on the grid as an increasing number of people get home in the evening and start to charge their cars
... and Rust does unify both of these use cases with traits, that is, what you're referring to is a "trait object", which is the same thing as Go with regards to interfaces. The difference is when you use a trait to bound a generic, in which case they get monomorphized and become "direct calls" in the OP's parlance.

I haven't re-read it recently, but https://softwareengineering.stackexchange.com/questions/2472... did contain a pretty great explanation of how these things relate.

It's also worth noting that we also saw some confusion from people not realizing these two use cases for the same feature, and so added some syntax to differentiate the two.
Thank you - hadn't come across that one.
Samsung 4K Monitor..I've found some of them on Amazon at around 300-350€
I think he's using it to show the ludicrousness of the system software has become. I haven't heard of any subscription shovels, have you?
Grothendieck's Récoltes et semailles (Harvest and planting)

One of the most underrated mathematicians of the 20th c.
Downdetector reporting a lot of AWS complaints simultaneously.
You Have a Moral Obligation to Claim Your $125 from Equifax
>you will not be able to receive/access emails that are sent to your primary address/domain until the provider resolves their issues.

You won't be able to receive new e-mails, but if you use a local client like thunderbird, you can still access your old e-mails.

With slack down, I can only access the messages that I (luckily) have cached locally.
Except that email has built in retries and feedback. Also it's expected to be async, so if a server is down for an hour, most people don't even notice.
Weird, it took me to a status page saying they were having trouble.