skysight-inc/HackerNews huggingface dataset:
>> There's a lot of technical debt that needs to be paid, but it's getting better.

You should just leave these sort of statements out of your introduction. It's generally assumed all projects have some degree of technical debt, and you'll lose more users (i.e. most) than you'd gain (i.e. 0) by trying to treat the subject with candor.

In other words, don't sell yourself short. Speak directly to why someone would want Sortix right away. In your intro, speak as if Sortix exists, fully formed, and complete. Let people come to their own conclusions about the quality.

For example, I'd rewrite the opening sentence from

Sortix is a small self-hosting Unix-like operating system developed since 2011 aiming
to be a clean and modern POSIX implementation.

To

Sortix is a clean and modern POSIX implementation.

Believe me, I've never released a project that I thought was complete. That's not because I've never released a project, it's because I'll probably never consider any of my projects "complete". There will always be more to add, more to take away, more to do. It adds nothing to my description to call my projects incomplete. The game is thus figuring out when to cut my engineering-self off and engage my sales-self.
BT extends cybersecurity offering to connected cars
Big name conflict: http://en.wikipedia.org/wiki/BIND
Why does the logo critter have trapezoid feet?
Not sure how it works for Windows but the Linux source is available which could give you an idea:

https://github.com/Kilian/f.lux-indicator-applet
>“Consumers depend on us to make sure that competition is fair and open, and it’s my responsibility to make that happen.

Really? Then why not go after banks, energy companies, telecom giants...?

As a consumer I have the choice to choose to trust google when I search for a product, however I have only two choices when I choose my ISP, or no option at all to choose my electricity provider.

Consumers don't depend on "them" to have fair and open competition, it's the companies that depend on the governments to have unfair or nonexistent competiton.
HTTPS certainly is not cache friendly. Is there an easy way to extend https to handle heavy cache use cases (to improve caching behavior across clients)?

For example:

Assume: file.data exists and is already encrypted with enckey=K, deckey=D, algo=X, etc

Client -> https://www.example.com/file.data
<-> <protocol between server/client to get deckey, algo, etc needed to decrypt>

<- transfer of file.data (from cache) without further encryption but still in the scope of the outer https. The response would carry appropriate headers to indicate where the "plain" data starts and how long it is. At this point, you can use a packet filter and see the encrypted body of the file but not the https headers or anything else.

- Client recognizes this valid https session response but takes the inner sections without further decryption. The inner section would need to be marked (as in a multi-part section), and https response headers would need to indicate which byte range of the body should be read as-is and decoded with key deckey.

Again, I am hoping for some sort of extension to https to make it cache friendly.

Advantages: File is encrypted once (or as needed if policy requires it) and caching proxies can serve the file without re-encryption per user session response.

Disadvantage: Likely need to change http/s in some way to wrap and mark plain data.
Nope I'm in the Netherlands, but we have similar rulings, e.g.: need 3 clients per year at least for contract not to be considered 'employment'. I'll need to lookup if these type of 'retainer agreements' can affect this. Cheers for bringing this up.
Yes i am a podcast avid listener :)
Good to know you able to pull off nicely this web app without much coding knowledge, i am very impressed.
I know which phrase you're referring to, but if you read it in context, it's apparent this is an exception case, because the very same section talks about cacheable, stateless requests and responses.

All of REST's constraints are about encouraging cacheability and "visibility" to intermediaries. Intermediaries should in most cases be able to see which resource is being requested/returned, read the method, read the content-type and other headers.

All of this is not available during an HTTPS session. So "HTTP + a bit of HTTPs" is REST + a dose of realism.

But "HTTPs-only" is something else entirely.
.. is lovely: https://users-cs.au.dk/~sortie/sortix/screenshots/sortix-nee...
> Until there's a free, easy, maintainable, and actually existent solution to SSL certs, enforcing HTTPS-only is just downright extortion.

> Referring to solutions that are under construction doesn't cut it. If you're that passionate about it, contribute to the SSL cert solution yourself instead of to the endless calls for HTTPS-only

Right. In similar threads, I've seen a lot of people linking to Let's Encrypt[0]. The idea of that project is great but, at best, all we can do now is discuss how to enforce HTTPS once Let's Encrypt (or something comparable) is available. Anybody who runs a small, personal website that generates no revenue would essentially be screwed if it were enforced before then, as (and someone can correct me if I'm wrong here) there aren't really any affordable options at this point for people who don't have much money to throw towards their site.

[0] https://letsencrypt.org/
From what I can tell, they're only resellers, the companies that actually issue the certs are GeoTrust and Symantec.

In any case, I know it can and does happen, I just don't agree that it is "far from difficult". Having to hack an SSL provider is out of reach for the vast majority online thieves and casual snoopers.
Saving a Plane That Saves Lives
Guaranteed income without having to do any work? Sign me up! You can crank low focus jobs like email and get paid to do it. I don't know why you wouldn't want a retainer.
Getting rid of Apple Spell (annoying red underline)
I highly doubt the target audience care about that..
ReSharper mostly, sometimes Visual Studio's code analysis functions.
Quicklisp: On Beyond Beta, Talk at European Lisp Symposium 2015
>Have you considered the alternative?

Yes and they are better.
i'm using Hangouts, Telegram and Line... why should I use WhatsApp? These App all have more functionalities and are "free".
The way I see it there are 2 problems with HTTP

1. Allows passive snooping (not always a problem)

2. No way of knowing whether data has been tampered with (always a problem)

Would be nice if there was a way to stop 2 (e.g. checksum sent through HTTPS), but allowed the caching benefits of 1
Yes, you should do it. Don't forget to bill for commute time & expense (I mean factor it into higher cost for the client, do not make it explicit).
It's also good to discuss what happens if you're ill and should not be commuting to clients' office - you just don't bill them for onsite mode.
This is great news, how to use old technology when it's the best solution for the present problem. It would also have been great to have a schema of how the terraces actually work.

If you're curious like me, here are some pictures of the actual terraces: https://www.google.com/search?q=Tigray+terracing
Anti-Test 'Opt Out' Movement Makes a Wave in New York State
"The common denominator among the homeless I know is Lack of Suppport from family members! Most of us have had some rough patches(nervous breakdowns, gaps in employment, addiction issues) and usually have some family member that helps out. These people had no one to turn to."

This. I've spoken to many homeless people - mostly in NYC but in other cities too. Whenever I ask about their family they always tell me that their folks woudn't pick them up. I once called the son of a drunk middle aged man on Brighton Beach. He didn't seem too particularly concerned when I told him I knew where his dad was.

I want to make a website where people can see profiles of homeless people, hear their story and sponsor them. I would have a very low cost operation: rooms in cities for homeless people, with a shower, computer, and food (soup etc). Homeless could use the room but would need to register their name, photo, biometrics (fingerprint etc) and progress through a program that would be a bit gamified. The steps would be somewhat personalized but essentially include the following tasks:

Register
Go make an appointment with a psychiatrist
Go meet someone who will help buy clothes, shower etc.
Get a cellphone and an address
Talk to a career counselor
Apply for government assistance, with help
Get an education or a job

They would receive cards and we'd see what they spend on. Their cards would be loaded with more money as they complete challenges. They'd be self motivated with 90% assistance from the program. I am a big believer in "smart tools" that make motivation easier and take care of 95% if all the research and logistics. The homeless person shouldn't have to figure out what they need in their backpack, what programs exist in their city and how to apply or take advantage of them. This hould be done by experts. And motivation should be optimized also, with human servie providers helping do evaluations and customizing.

I also believe in metrics and reporting, which the public funding the website would receive as people get off the street get a job and their stories of success.
The Coffeeware License
MIT sensor detects spoiled meat
Just hover a magnifying lens above one hand in a very sunny day and you'll be recording a very cute pic of that day, on your hand.. :) Stick that lens to the wall and you get a 100% self powered 1 pixel camera.
> without all those side effects.

It's recommended you check your liver function when taking modafinil.
SX – Stack Exchange mode for Emacs
Without looking anything up, I'd guess "compose-,-c" and "compose-o-a", for the first two, and that turns out to be correct.

I had to try a few things for the degree symbol, but I guessed it on my third try (it's "compose-o-o"). Once I knew that, my first guess for ¿ was "compose-?-?", which also turned out to be correct.

But as the other reply said, you can always look them up if necessary, which you'd almost certainly have to do with the Mac's system of "option + some arbitrarily selected key".
Using Z3 theorem prover to prove equivalence of some bizarre alternative to XOR
RSMQ: A lightweight Redis based message queue for Node.js
Our Prodigal Sun: Searching the heavens for our sun’s family (2013)
Interesting, but well cut from the story. Clumsy, preachy, doesn't add. That's what editing is for. If you skip the editing stage, you end up with Ayn Rand.
StartSSL has been around for a long time, and issues free certs (with a $20 fee iff you need to revoke it before expiration).
A Robot That Bought Drugs Online Is Now Free from Police Custody
It's not "alternative to whatsapp", it's "alternative app monetization strategy".
I'm using it because everyone else is on WhatsApp.
Huh, I hadn't even considered that as a reason. Oh HN, I am disappoint.
There is nothing about niche audiences that make them particularly forgiving consumers. Quite the opposite, actually. Niche audiences tend to be the most critical. Don't readily hand them ammunition to dismiss a project early.

A niche audience might look past silly logos, or even adopt them wholehearted as part of their "other" identity. But they are still consumers and still need to be marketed to. In this case, a bad logo is better than no logo.

But bad copy is just bad copy.

Most people won't actually use any particular project they read about. Most of early-stage marketing (and posting links like this to link-share sites like HN) is about gaining mind-share. You're investing time now in getting your name out so that--6 months from now--people who will eventually become your core users will say to themselves, "yeah, I remember hearing about that."

And when they say that to themselves, they are going to retain that mental picture of the project from when they first heard about it. If that picture is "incomplete, pie-in-the-sky", then they will continue to think of it as that. You now have to fight against the long-tail of converting people over to the new normal of your project being "complete".

Granted, if Jonas Termansen has no interest in having users, then he should just ignore my post completely. But then, why did he prop up a website for his project, a project he's labored on for 4 years now?

If you put that kind of effort into something, you owe it to yourself to not sell it short.
Of course, but my point is that you know this going in. The assumption was that you'd buy the company not because it was so insanely profitable, but because you reaped a PR benefit. So you buy the company for the sole reason that you look good for paying everyone well, and then take away all the money to increase profits. This makes no sense -- you look far worse PR-wise for revoking the raises than any benefit you originally got from buying them in the first place, and PR was your reason for the deal. This is like buying Santa's workshop so kids will like you and then executing all the elves.

You should have just bought a profitable company in the first place.
Those are not feet: the critter is a space snake that fell on Giza.
Beg to disagree, for two reasons.

* No two places can be silicon valley, just because of the twofold effects of concentration and competition. I.e. SV is what it is not only because of culture, but also because all big IT corps have their headquarters their, and they simply can't have two headquarters.

* Not all places are best of as clones of SV. In particular, if you don't have a widespread educational and technological infrastructure, but rather any other form of assets, then it may well be better just to try to be something else than SV (e.g. a mining/industrial/financial/cultural centre, or just a place people go to sleep). The real world makes money, too.
The idea of donating 2 days a month seems great but I feel the site isn't arming developers well. These are some example questions that might come up in conversations:

1. Depending on your work environment, you may work in a place with lots of legacy code. After all, why should an employee work on open source when we could be improving our legacy codebase and slowly modernizing it?

2. How do we know the work contributed will be brought to use (aka merged in)?

3. Can and how do we donate to project X instead providing your time? We have some tight deadlines and we need everyone on board.

Marketing to your employer you need 2 days a month seems like a nonstarter. As in programming, start small, build a strong foundation and iterate. See what works.

Maybe you could start with 2 hours per week (1 day month) and see how that goes. This will get you, the developer, and the company who employees you comfortable with this arrangement.

Companies like to feel comfortable.
Messaging/chat are inherently bad apps for advertising anyway. This post was also from 2012, before selling to Facebook for 19B.
TLS/SSL actually supports authentication/signing only, it's just that most browsers don't accept it by default: http://www.hamwan.org/t/SSL+without+Encryption
That sounds like a smart company.
and I know they're already beholden to domain registrars but that's not really a good argument against adding an additional, arguably unnecessary cost to someone who just wants to run a hobby website.

You are not required to have a domain to have a website; just using an IP address works fine too, and - more importantly - unlike what would happen if the proposal to ban plaintext goes through, browsers don't give big scary warnings if you use an IP instead.
Using Closure Space to Create Real Private Members in JavaScript
Download your Google search history
> I don't know if the medical culture is different where you are

France, where the situation is as described above. Select groups are trying to raise awareness of the issue for children so that they don't end up being classified as spoiled brats, but last time I checked there's basically squat for adults.
I accidentally did something similar quite a few years ago when I stupidly set up a grep to run updatedb every two hours. There was several months lag as well between when I did that and my computer started locking up every two hours for a few minutes. And embarrassingly, it took me a week or two to put it together.
Well yes, none of them would actually have their own name on said certs. But all of them had API access to make symantec or geotrust issue certs. End result is the same.

Having been involved in all of the hacks I linked, I wouldn't describe them as anything extraordinary.
HTTP has quite good integrity of the data you requested

Not for the values of "integrity" that include the possibility of intermediate tampering. You have no indication that the request received by the server is the one you sent, nor the response that you received is the one that the server sent.
The largest Buddhist settlement in the world
>42 accepts almost anyone

Not true :(
Even though I thought I completely blew the preliminary tests I then received a mail telling me I wasn't accepted.

Although as an aside, my female friend who gave up before finishing and completed less of the tests than me got in, so I'm not sure I would even want to be accepted now but still, there is some heavy pruning going on.
> creates app that leeches your contact list and spam people to o install the app in your name

> post about hating advertising

you can cut the irony/hypocrisy with a knife. what's next? a post about how he loves client interoperability? heh.
> Until there's a free, easy, maintainable, and actually existent solution to SSL certs, enforcing HTTPS-only is just downright extortion.

Note that the proposal this comment is in regard to a propasal to ban HTTP for websites of the federal government. It does not mean you have to stop offering HTTP for your own service.

I think the government can afford a couple of SSL certificates, and the privacy and authenticity improvements are well worth it when communicating with goverment institutions.
So suddenly everybody is rushing to build a human dispatch service for everything, and the end result will be that there will be one winner, who cashes in a big percentage of every transaction in the particular market segment. The actual AI can wait, because what matters now is the cornering of the market.

As you can see, this development does not make me happy.
Summertide, by Charles Sheffield. There isn't a lot of deep argument to screw up, but the visuals are impressive (2 planets orbiting closely each other in the road to a catastrophic quake/tsunami, alien artifacts from millions of years ago, really weird alien races).

That should be the ultimate criteria, is hard to translate right a deep argument to TV (and sometimes the translation includes "sponsored message" from government and groups of power that damages the book message), but books with good visuals may be perfect for that media (and if are not great, run low risk of corruption)

Would hate that great books like Hyperion end having the same fate as All you zombies or Mimsy were the borogoves.
>> Due to many institutions having policies against FTP and peer-to-peer protocols,

This is the problem. Your organization needs to stop cargoculting IT policy. Perhaps banning HTTP will be enough pain to make that change possible.
Ask HN: How did you meet your co-founder(s)?
Curiosity.
Candy Crush Saga v1.50.0 Apk for and Android Download
Principles for effective risk data aggregation and risk reporting
Gocharm – Implementing Juju Charms in Go
This should be obvious. Concierge style services married to digital communication and software dispatch, it's a natural combination.
> But dynamic typing is terrible for large code bases.

Yes, you can get into a lot of trouble very quickly as your codebase grows if you don't have a heavy security blanket. But the more Ruby I write, the more typing looks like Linus from Charlie Brown's blanket.

Because you don't need a monolithic code base any more. You can break it up into smaller pieces that interact with each other using POD objects.

When I start to have type problems in Ruby, I start looking around for a domain concept that I need to extract into a gem. The codebase never grows to a point to where it becomes a serious problem.
IDEO: How the technology that powers Bitcoin might reshape the music industry
I agree. Lifting 30kg is "easy". Lifting 30kg a dozen times isn't that hard. But the moment you have to carry the weight around a lot, or lift it into weird positions, it's an entirely different thing.

I do power lifting. I'm an advanced lifter (but not quite competitive levels) for my weight class and age. I e.g. deadlift 180kg raw (without equipment/belts etc.).

Yet carrying my 25kg son around gets exhausting after a few minutes, and that's when he's cooperating and holding on. I can do it for quite an amount of time, but not without being a wreck afterwards.

Most people don't have the strength or endurance to carry 30kg of dead weight around for long in any position, but more importantly, even if you can carry 30kg around on your back or clutched to your chest, does not mean you are able to do anything useful with that weight, such as being able to lift it up to chest height and push it into place, or rotating it to slide it into awkward spots, or any number of other things.

E.g. being able to overhead press 100kg still means I'm just barely able to safely push a 30kg server into place high up in a rack without assistance - precision movements or moving into positions that affect your balance or leverage in any way very substantially reduces the amount you're able to lift.

Increasing the amount of time you can carry a weight around, or increasing your ability to move the weight into various positions alone will be a big deal.
Great idea. In terms of how to pitch this to businesses, one angle I haven't seen mentioned so far is to emphasise how improvements in open source dependencies not used by competitors could give you a direct commercial edge. For example in my previous company we had our own DSL for algo trading algorithms that used LLVM, whereas all our competitors solutions were Java based. Any performance improvements we contributed to LLVM would benefit us but not our competitors.
Another downside is that Free has been pushing for tiered internet access where you have to pay extra to access a specific website like Youtube.
And most people like their low cost so much that they don't even care if it means the end of a free and open Internet.
The browser, not the screenreader, does the rendering, figuring out what's visible, etc. The results, an "accessibility tree" which is sort of a subset of the DOM, are then presented through an accessibility API to screenreader software. Screenreader software is pretty naive, there might be some that initially assume a table is being used for presentation, not data, if it lacks good semantic structure (e.g. no <th> header elements). Case by case, it's hard to tell in which way the author is bad at their job, using a table for presentation or poorly marking up a table for data.

The stakes are much lower for Readability-esque algorithms, when they fuck up the user can just go back to the site's native presentation; screenreader users don't have that choice.
Could you not solve 1 by having an HTTPS index page with content hashes?
> The main benefit to me is that I can avoid homebrew and macports, which are utter garbage.

Would you like to elaborate on that?
For everyone who thinks CSS is just a collection of hacks (rightly so) etc., you should try playing with GTK+3. It borrows a subset of CSS, has it's own Flexy Grid model system etc. It will still be fair to call it a Work in Progress but I think it's layout system is quite nice.
""Just as the sun’s rays enliven us, PANTONE Minion Yellow is a color that heightens awareness and creates clarity, lighting the way to the intelligence, originality and the resourcefulness of an open mind – this is the color of hope, joy and optimism," said Leatrice Eiseman, Executive Director, Pantone Color Institute."

Wow, like watching Mad Men (60's copywriting :) )
Meet the man behind Google's Doodles