Show HN: Wiv.js – A library for a more wiggly div - <AUTHOR> https://jjkaufman.github.io/wiv.js/ <comment><USER2> move these things into initWiv() and cache them:

        var speed = parseFloat(wivCurve.parentNode.dataset.wivSpeed)
        var height = parseFloat(wivCurve.parentNode.dataset.wivHeight)
        var tightness = parseFloat(wivCurve.parentNode.dataset.wivTightness)
        var thickness = parseFloat(wivCurve.parentNode.dataset.wivThickness)
        var ctx = wivCurve.getContext("2d");

do this once on init, the canvas context remembers it anyway:

        ctx.strokeStyle = wivCurve.parentNode.dataset.wivColor != undefined ? wivCurve.parentNode.dataset.wivColor : "#FF0000"

don't convert numbers and strings all the time, use numbers and init them to 0

        //current frame is tracked on per wiv basis. This is to help with speed calculations
        if (parseFloat(wivCurve.dataset.count) > 100000) {
            wivCurve.dataset.count = "0";
        }
        wivCurve.dataset.count = (wivCurve.dataset.count ? parseFloat(wivCurve.dataset.count) : 0) + speed;

parseFloat(wivCurve.dataset.count) also is used a lot in that loop.

And don't set unneccessary canvas state, this should happen only once per draw loop iteration: [edit, actually, as I said above, the canvas contexts remember it individually, so do this once in initWiv(), and not in the draw loop at all, yay!]

        ctx.lineWidth = thickness;

That's all just at first glance, but I bet you, this would help with slow laptops and whatnot :) Such "small" things really add up when you do them 60 times per second * number of borders. I don't know if setting the canvas width or height to the value it has anyway to clear it (instead of clearing/drawing a rectangle explicitly) is still a useful thing to do, but you might try that as well.

<comment><AUTHOR> Thank you for the thoughtful code review. It is already running smoother

[https://github.com/jjkaufman/wiv.js/pull/5](https://github.com/jjkaufman/wiv.js/pull/5) if you are curious

<comment><USER2> Awesome! You're welcome :)

</comment></comment></comment><comment><USER3> This would have been absolutely huge on MySpace.

<comment><USER4> It might still catch on on [https://neocities.org/](https://neocities.org/)

<comment><AUTHOR> neocities is rad

[https://coughdrop.neocities.org/](https://coughdrop.neocities.org/)

<comment><USER4> Hey, you're the person who made this lib!

You're the one who is rad! Thanks for sharing this Christmas gift! :)

(also, I love neocities. Happily donate to it and using it unironically for sharing small things)

</comment></comment></comment></comment><comment><USER5> This is guilt-trippingly sweet, there's a certain charm I get from this, kind of like that of tacky Christmas sweaters or unironically used comic sans :)

<comment><USER6> How about Wiv.js _and_ Comic Sans?

<comment><USER7> WivSansJs

</comment></comment></comment><comment><USER8> I opened this on my Notebook, and it's Fan spun out of control!

it might be my ancient hardware, but this is rather CPU intensive it seems.

But the effect is fun, and cool non the less!

(on Linux, Xorg + Frirefox)

<comment><USER9> I suspect that Firefox is relying on modern-ish GPU features to make things "fast", but Mesa is straining the CPU to emulate those features, which are missing from your older GPU. (Software going "I'll use the GPU, that must make things faster!" is what finally pushed me away from using an x60 as my daily driver).

</comment></comment><comment><USER10> As long as it's not fast or turbo, this is actually not as bad as I expected. It's soothing, even.

</comment><comment><USER11> Ha! This is completely nonsense, and completely awesome. Description checks out. Well done!

</comment><comment><USER12> Thanks, I hate it.

</comment><comment><USER13> The blink tag of Web 2.0 has arrived.

<comment><USER14> It's already here: Material Design "ripple" effect.

<comment><USER15> The ripple actually looks good though

<comment><USER14> The ripple looks bad and is terrible for accessibility. Not everything on a page should move. Look up animation and accessibility.

</comment></comment></comment></comment><comment><USER16> It's cool, and I could see it making it's way into more lighthearted projects

</comment><comment><USER17> This is rad and obnoxious at the same time

<comment><USER18> The quintessential eighties.

<comment><AUTHOR> [https://www.youtube.com/watch?v=1tHAxxni8RM](https://www.youtube.com/watch?v=1tHAxxni8RM)

</comment></comment></comment><comment><USER19> Wondering if it's possible to increase the speed on hover

</comment><comment><USER20> This should have existed in 1994

<comment><USER21> It did. Here's my personal site from that era, complete with javascript "Layer" (in Netscape) (or DIV in IE3) tags doing the wiggling:

[http://jasonkester.com/](http://jasonkester.com/)

</comment></comment><comment><USER22> I have been looking for these kinds of things! A month ago I started building a similar project: [http://dsalaj.com/quirky-ux/](http://dsalaj.com/quirky- ux/)

But now I realize these things should also be collected to a list somewhere. I linked your project in mine for starters. Thanks for sharing! Cheers!

<comment><USER4> > _But now I realize these things should also be collected to a list > somewhere._

Like an _awesome_ list? What should it be called? _awesome-oldschool_ maybe?

<comment><USER22> Well... I've been thinking a lot about this terminology. On one hand it is useless/oldschool/ugly/trash/weird kind of effect, but on the other hand it can be extremely effective (like described in motivation of my quirky-ux (see talk by Vitaly Friedman of smashingmagazine)).

tl;dr ...websites with a lots of character which break best practice guidelines and design rules are able to capture audience better and produce better results (turnover, traffic, user retention, etc.)

So I ended up finding a neutral sounding word: QUIRKY - having or characterized by peculiar or unexpected traits or aspects.

I would gladly reformat quirky-ux to be primarely this collestion/list of quirky stuff, but maybe _awesome-quirky_ makes more sense or _awesome-quirky- ui_ or something similar...

<comment><USER4> Quirky sounds apt. How about _awesome-quirksmode_ as a historical reference? :P

<comment><USER22> Cool. I would say _awesome-quirks_ sounds a bit better and also avoids the confusion with the meaning of quirks mode, the compatibility feature of browsers. I have created the list: [https://github.com/dsalaj/awesome- quirks](https://github.com/dsalaj/awesome-quirks)

Please contribute! If you really prefer the name _awesome-quirksmode_ I have no problem with renaming the repo or adding you as a contributor so you can do it. Thanks for the feedback!

<comment><USER4> Hey, it's _your_ project, I just made a silly joke :)

</comment></comment></comment></comment></comment></comment><comment><USER23> That is amazingly cool. Not sure what I'd ever use it for, but it's awesome nonetheless!

<comment><USER24> It can be use for form validation. If user doesn't enter an input, we can "wiggle" it for 2 seconds (together with a red error message). Recently I did just that :)

<comment><USER23> Aaaww, yeah. I like that idea a lot. I might just use that in a project I'm working on. Thanks for mentioning that!

</comment></comment></comment><comment><USER25> (edit: this assertion is incorrect, I skimmed the code too fast) I had no idea that you can draw on any element, not just canvas ones ... I thought there was a semantic meaning there ... apparently there isn't?

<comment><USER26> Looks like it's adding a canvas element to the divs and positioning it to line up.

<comment><USER25> Ah yes I missed the var canvas line and just presumed the code was getting a context on the selected div instead, a feature I didn't know was possible (it isn't).

The canvas declaration is staring right at me now that I review it again. That's life...

</comment></comment></comment><comment><USER27> This should come built in in all modern browsers.

<comment><USER28> Browsers are getting too feature laden. Soon nobody will be able to write a browser from scratch. Instead, let users implement the features they need, or let them use libraries if necessary.

<comment><USER29> Yes, sure, but thIs is one of those things we don't realise should be a core, kernel-level feature until it's put on our Christmas dinner plate (by all means keep things like security/auth/etc in libraries)

</comment></comment></comment><comment><AUTHOR> Appreciate all the feedback. Merry Christmas!

</comment><comment><USER30> If there is an official Dr. Katz web page it should use this.

</comment><comment><USER31> Very cool - hopefully ads won't usurp this...

</comment><comment><USER32> Great stuff! Now let's see it for text next!

</comment><comment><USER33> Wiggle wiggle click me stanger Wiggle wiggle buy me flowers

</comment><comment> more-coffee Upvoting because it's wednesday.</comment>


Confessions of a Google Spammer - <AUTHOR> https://readthink.com/confessions-of-a-google-spammer-4f2e0c3e9869?source=linkShare-db37538f351-1479593053 <comment><USER2> Fascinating read. Makes me wonder what today's black hats are up to because there's no way that Google got rid of all of them.</comment>


Entrepreneur vs. Small Business Owner - <AUTHOR> http://aflanagan.com/entrepreneur-vs-small-business-owner/

<comment><USER2> Entrepreneur is a word used to inflate your self-image or ego.

Small business owner is a more matter-of-fact way to describe yourself (if you must).

It makes sense that he got a better response using "entrepreneur" because it sounds exotic and powerful, but I try to avoid using it in polite company.

A related story:

I once saw the CEO of a major insurance company get pulled in front of an audience by an entertainer. When the entertainer asked him to tell the audience what he did for a living, the CEO said:

"I sell insurance."

That's the approach I prefer for social situations...just maybe not when you're trying to make a sale.

<comment><USER3> So you consider an entrepreneur the same thing as a business person? They are two totally different things.

</comment></comment><comment><USER4> Worth reading just for:

 _Sales calls that start like this "Hi, my name is August and I am a small business owner…" typically end with the receptionist (or whoever answers the phone) getting rid of me as quickly as possible._

 _Whereas calls that start like this "Hi, my name is August and I am an entrepreneur working on a new start up…" have a high probability of getting me transferred to a manager or decision maker of some sorts._

Good tip. Thanks.

</comment><comment><USER5> Startup Entrepreneur vs. Small Business Owner is the "Hacker vs. Cracker" debate of Hacker News.

(Not to take anything away from an interesting little article, though).

<comment><USER6> Please elaborate on the "Hacker Vs. Cracker" debate, I seemed to have missed this one.

<comment><USER7> Here is a decent overview of the misuse of the term hacker: <http://blogs.techrepublic.com.com/security/?p=1400>

</comment></comment></comment><comment><USER8> I suspect the difference is in the perceived upside potential of the relationship. The news media has been conditioned to think of "startups" and "entrepreneurs" as being backed by VC money and taking shots at really big targets. Even if 98% of these bids fail, the ones that succeed are mentioned in headlines stating "So-And-So raises $500,000,000 and promises to be the next big Whatever.ly"

On the other hand, when you think of the small-business owner at the copy shop down the street, you see an upside of maybe expanding his one shop to three shops. The downside is that he'll welch on his bill if money gets tight.

Who would you rather do business with?

</comment><comment><USER9> A/B testing at it's best. The exact wording of your introduction also makes a difference depending on what part of the country you live in. In silicon valley, "startup" will perk up most people's attention. "entrepreneur" in the midwest will get a "what ?"

<comment><USER10> I'm actually in Vancouver, B.C. which I think is somewhere in between those two. I've been calling mainly real estate agents all week, and am really surprised that they are the ones who perk up at hearing the word entrepreneur.

<comment><USER11> Real estate agents are in business for themselves (the companies they work for are really providing a federation-like environment, with shared services). I suspect many of them see themselves as entrepreneurs too.

</comment></comment></comment><comment><USER12> Entrepreneur: one who starts a new business. often several in sequence, regardless of whether the earlier ones succeed or fail. often with a new product, technology, market or competitive advantage. could start small then grow to very large, or, in some cases, start large at creation (think spinoffs or multi-corporate-backed partnerships.) May take VC. May become a billionaire. Often seeks an exit in the form of an IPO or buyout, and often early enough in their career that they can move on to the next startup, or, to retire young.

Small business owner: you own a small business. you may not have started it. you might have bought it. it might be a franchise. it often is not innovative. typically a commodity product or service (apples, hair cuts, lawn mowing, etc.). it often will not scale up well. it is often a family thing and may already be on the 2nd generation. if it fails the owner/founder is more likely to go back to having a traditional job. May take angels, but almost never VC. May become a millionaire. Often seeks to maintain it as a lifestyle business, at most offloading operational duties to hired management in order to gain a passive income stream, but typically closer to traditional retirement age.

in practice? the line blurs, esp when people use the terms without making a consistent distinction.

Steve Jobs: entrepreneur

Uncle Bob and his lawn moving service: small business owner, NOT an entrepreneur

(my two cents)</comment>


Show HN: Handy Nginx configuration templates - <AUTHOR> https://github.com/timgws/handy-nginx-includes <comment><USER2> Caddy [1] could also be used. It is a server coded in Go, and is made for everyone (tech savvy or not). The configuration is really simple, and something that took ~100 lines to configure with nginx (let's say a proxy vhost), would only take ~5 with Caddy. Oh, it also uses HTTP/2 by default (if the user's browser supports it) and generates letsencrypt certificates automatically.

[1] [https://caddyserver.com/](https://caddyserver.com/)</comment>


Refactoring JIT Compilation [video] - <AUTHOR> https://archive.org/details/dconf2014-day02-talk02

<comment><USER2> I may be biased, but this was one of my favorite talks at DConf :3.

You can find the source to higgs on GH: [https://github.com/maximecb/Higgs](https://github.com/maximecb/Higgs)

More info is on Maxime's blog: [http://pointersgonewild.wordpress.com/](http://pointersgonewild.wordpress.com/)

And our subreddit: [http://www.reddit.com/r/higgsjs/](http://www.reddit.com/r/higgsjs/)

You can also stop by and say hello in #higgsjs on freenode.

We're looking for contributors of all skill levels if anyone is interested!

</comment><comment><USER3> Youtube version: [http://youtu.be/cJGNItlMWBM](http://youtu.be/cJGNItlMWBM)</comment>


Apply HN: Skein – Engineers Paid on Commision - <AUTHOR> Skein is a disruptive technology that definitively solves the KPI incentive problem for engineering resources.  No longer do engineering efforts have to be a nebulous pit with no way to measure the value of individual initiatives.  Skein is not only a platform for transparently determining the bottom line impact of engineering efforts, but it is a launch pad for a revolution in technology company compensation and culture.
Software Engineers of today are far more entrepreneurial and risk tolerant now than ever before.  Bring your sales and technology teams closer than ever before with Skein, and see endless rewards.
http://skein.io/
Skein is a dead simple technology with complex and far reaching implications, not sure how it will work?  Check out the faq:
http://skein.io/faq/ <comment><USER2> I found your description here a bit more difficult to understand than the description on the website.

I like the concept, as in having revenue streams that can be shared with the people building the product. You thought about things like house keeping tasks (and bugs etc). I can imagine that it's an easy way to clean up some technical debt, just divert a bigger chunk of the revenue towards those bugs.

Couple of things I'd love to see worked out a bit more. Maybe you mention them somewhere, but still:

\- How does this work in an interface? Sales people will not really go into git and see it, so I assume some kind of interface with sliders that match the streams+tags. Showing this can be insightful (a sketch can already give more insight in what you're actually building).

\- I assume there is some kind of holding period so that the 'bug' tag for example can be extended for a while, giving me the guarantee that those 20% of the shared revenue that went to bugs actually stays for a couple of weeks.

\- There is (obviously) a lot of weird scenario's possible here. Imagine a business requirement changing. I wrote a big piece of the functionality, but it becomes simpler. 90% of the code can be removed, someone else writes another 10%. How does this equate to money shared? I did all the 'heavy- lifting', but the other person made it workable in the current increment.

\- I can see this become really difficult to manage in larger teams and products, and possibly leading to unhealthy competition where people are enticed to work more against each other than with each other. Maybe there could be certain ways to make working together more attractive? For example, commits within a week from each other by different people attract some kind of bonus % to all involved?

\- In general, the idea is nice, but I wonder if the 'old fashioned' way of sharing profit with a normal bonus (hey, you guys did a great job) won't work better if applied correctly, although this could also be seen as a way of making the bonus structure work less politically colored, or at least more transparent.

<comment><AUTHOR> janpietrz. Thanks for your feedback! I'll address your questions in order:

\- The interface aims to be dead simple. From the developer perspective there is little interface (aside from reporting back to them what they have earned, which tags earned the most, etc). The developers are simply adding tags into their git commits. From a manager perspective, there are two main interfaces: 1. there is a path to define revenue streams (which can eventually integrate into native accounting software). 2. There is an interface that lists out the unassigned tags which you can simply drag and drop onto the revenue streams and set the commission rate. I can definetely provide more sketches if you like. I hope to update the website soon with more detailed screenshots.

\- There is a time weight component that is optional. One algorithm is a time weighted decay component that continues to value contributions over time even after they have been removed.

-Definitely, weird scenarios can come out of it. Skein isn't meant to be a one size fits all solution but rather a platform for companies to customize their own solution. Its also not meant to be a perfect solution, but rather a solution that is better than what we have now (which is nothing ;), which can be iterated on over time. In terms of the scenario you described simplifying the code is actually something that benefits everyone working on a particular feature because it increases everyones percentage participation, because the total percentage of code went down. This motivates people to refactor code more heavily. However, there are ways to customize this behavior as well. Time weighted algorithms could potentially help with you scenario. Also keep in mind, even though that first 10% of the code you wrote was largely discarded, it was also the first code, and probably contains the core components which if written well will not go away over time.

\- The target market for this product is mainly small to mid size tech companies that don't want to offer equity as a costly compensation that many engineers don't value in the same way that an investor or board member would, but still prompts motivation and rapid growth. The possibility of unhealthy competition is eclipsed (IMO) by the fact that engineers are now empowered to participate at a level they have never been able to before, and that is at the level of commission, which provides tremendous benefit and motivation. Therefore, the idea is to promote engineers to compete in a healthy measurable way that they can see and optimize to the businesses goals, rather than the current way which is very qualitative and not transparent, perhaps even in some companies a bit more political. I think your idea on offering additional bonuses to more collaborative efforts is a great idea!

\- Exactly. Skein also serves another purpose, while the compensation component is important it is entirely optional and customizable. Another main value add that skein provides is an insight into how individual initiatives (in this case tags made by developers) impact the top line of the company in terms of its relationship to different revenue streams. To this day that process is very much a black box. This allows us to move more towards "data driven product development" a concept that will prove to define and further the technology industry in years to come.

</comment></comment><comment><AUTHOR> :/ Any thoughts?</comment>


1 Billion-Year-Old Water Tastes 'Terrible' - <AUTHOR> http://www.theatlantic.com/technology/archive/2013/06/confirmed-1-billion-year-old-water-tastes-terrible/276946/

<comment><USER2> The headline gets your attention, but after reading the article, it makes perfect sense that water soaking up minerals from a rock for a billion years would taste pretty bad.

A very interesting find for the sake of scientific inquiry though.

</comment><comment><USER3> In the UK, there is an old Roman Bathhouse available as a tourist attraction. Along with your ticket, you get a chance to taste the water that comes from the same hot springs that powered the baths.

It is unbelievably disgusting. But watching the reactions of the people trying it is a source of endless fun.

<comment><USER4> I grew up near it (it's in a city called Bath, appropriately). It was a regular on the school trip circuit for us. Calling it a 'bathhouse' is accurate but sells it a bit short: it's an almost perfectly preserved complex: if you put a towel rack up you could open it for business tomorrow. To my mind, it rivals Pompeii in conveying an impression of Roman life.

It's well worth a trip for any non-Brits finding themselves in London on business: just a 2 hour train ride from Paddington station.

<comment><USER5> I will add, if you have access to a car, a great overnight trip (stay near by the night before) from London is to do the early morning, pre-opening Stonehenge visit (book it a bit in advance and you can get right up to the stones with hardly anyone around) and then head over to Bath for lunch and the afternoon.

</comment></comment></comment><comment><USER6> I find it amusingly ironic that an article about bad taste and billion-year- old water is in "The Atlantic".

</comment><comment><USER7> Go figure.

I would be afraid of what might be growing in the water, but I guess that level of salt would kill most anything.

<comment><USER8> -as we know it.

<comment><USER9> In which case it would probably die upon entering the human body, as it would find us miserably hypotonic.

<comment><USER7> Which one of us would find the other more toxic?

</comment></comment></comment></comment><comment><USER10> I'm glad to see that I'm not the only one who like to taste different things that other people would see as weird. I mean, if I found something extraordinary like water on Mars, my first though would be "How does it taste?".

</comment><comment><USER11> Kudos to her. Whatever makes science interesting, go for it. Maybe combine this with a gross-out reality show concept called "Eating the Earth" where competing geologists dare each other to eat that.

</comment><comment><USER12> So, she drank some of the water and is now postulating that it might have life in it?

Uhm... well, I assume this article has been written so long since the event happened that we know she didn't contract some terrible disease that mutated in there.

<comment><USER13> Anything able to live in there has never had a chance to infect any vertebrate, so it's unlikely that it would be able to infect a mammal. Mutation alone won't do the trick with no selective pressure for virulence.

<comment><USER14> Suddenly, I am reminded of the Rifters trilogy by Peter Watts. Available free to read thanks to Creative Commons: [http://www.rifters.com/real/shorts.htm](http://www.rifters.com/real/shorts.htm)

</comment></comment></comment><comment><USER15> I love how that as smart and scientific as we are as a civilization, we're still just primates deep down.

"We found 1 billion year old water! ... I want to drink it so bad."

<comment><USER16> "When all you have is 1 billion year old water, everything looks like a glass."

</comment></comment><comment><USER17> _" Now onto the bigger questions: Is there life in this billion-year-old water?"_

I'm guessing a Hollywood screenwriter is already working on the answer to this question.

<comment><USER18> I can already see the trailer: loud Inception-esque BRAAAHHM sounds, black/desolate landscape, shot on Red in 3D, weird syrupy water turns out to be alien goop... etc...

Oh, and throw in a robotic Fassbender!

... wait... I think I saw this movie last summer ;)

<comment><USER19> That just means you'll see it again soon.

</comment></comment></comment><comment><USER20> This reminds me of a sci movie about zombie infection or some such. This is always how it starts, finding some strange liquid, tasting it, spreading a plauge our bodies aren't adapted to etc.</comment>


The Disabled Fight for Health Care - <AUTHOR> https://www.theatlantic.com/video/index/533001/the-disabled-fight-for-health-care/?single_page=true <comment><USER2> (video)</comment>


Gmail doesn't allow SMTP connections via IPv6 - <AUTHOR> https://phunehehe.net/gmail-smtp-ipv6/ <comment><USER2> Your ISP is probably blocking SMTP-related ports inconsistently. Here's what I see from Comcast Residential:

      $ nmap -6 -Pn 2404:6800:4003:c02::6c

      Starting Nmap 7.10 ( https://nmap.org ) at 2016-03-27 17:38 PDT
      Nmap scan report for sc-in-x6c.1e100.net (2404:6800:4003:c02::6c)
      Host is up (0.18s latency).
      Not shown: 996 filtered ports
      PORT    STATE SERVICE
      465/tcp open  smtps
      587/tcp open  submission
      993/tcp open  imaps
      995/tcp open  pop3s

      Nmap done: 1 IP address (1 host up) scanned in 13.51 seconds

      $ nmap -Pn 184.108.40.206

      Starting Nmap 7.10 ( https://nmap.org ) at 2016-03-27 17:38 PDT
      Nmap scan report for sc-in-f108.1e100.net (18.104.22.168)
      Host is up (0.19s latency).
      Not shown: 996 filtered ports
      PORT    STATE SERVICE
      465/tcp open  smtps
      587/tcp open  submission
      993/tcp open  imaps
      995/tcp open  pop3s

      Nmap done: 1 IP address (1 host up) scanned in 12.86 seconds

<comment><AUTHOR> I don't like the idea that Digital Ocean can be doing something that weird :) But it seems like you are right. I'll drop them a note.

        $ mtr --report-wide 2404:6800:4003:c02::6c --tcp --port 993
        Start: Mon Mar 28 03:23:08 2016
        HOST: phunehehe-do3                      Loss%   Snt   Last   Avg  Best  Wrst StDev
          1.|-- 2400:6180:0:d0:ffff:ffff:ffff:fff1  0.0%    10    0.7   1.1   0.3   6.5   1.9
          2.|-- 2400:6180::601                      0.0%    10    0.3   0.3   0.3   0.4   0.0
          3.|-- 2400:6180::301                      0.0%    10    0.9   0.6   0.3   1.3   0.0
          4.|-- 2001:4860:1:1:2:82d::               0.0%    10    0.9   1.8   0.9   3.8   0.7
          5.|-- 2001:4860::1:0:518d                 0.0%    10    1.7   2.0   1.7   2.2   0.0
          6.|-- 2001:4860::2:0:ab29                 0.0%    10    2.2   9.5   1.8  64.4  19.6
          7.|-- 2001:4860::2:0:ab28                40.0%    10    2.7   2.4   1.7   3.3   0.4
          8.|-- sc-in-x6c.1e100.net                70.0%    10  127.0 151.6 126.9 200.8  42.6

        $ mtr --report-wide 2404:6800:4003:c02::6c --tcp --port 465
        Start: Mon Mar 28 03:23:30 2016
        HOST: phunehehe-do3 Loss%   Snt   Last   Avg  Best  Wrst StDev

<comment><USER2> Sounds like this, then:

[https://warrenguy.me/blog/ipv6-digital-ocean- crippled](https://warrenguy.me/blog/ipv6-digital-ocean-crippled)

<comment><AUTHOR> You are exactly right. Thanks again.</comment></comment></comment></comment>


How You Sleep is Who You Are - <AUTHOR> http://www.theatlantic.com/doc/200712/primarysources?wtID=33.3czt.11.3lcx ... scroll down to the title text, or 'Psychology' (sorry 'bout that). <comment><USER2> The more regular your sleeping schedule is, the more likely you are to be a "morning person". So if there is causation, it's probably the other way around: who you are determines how you sleep. That's pretty boring.

</comment><comment><USER3> '... His results offer new evidence that morning and evening types think differently. Early risers prefer to gather knowledge from concrete information. They reach conclusions through logic and analysis. Night owls are more imaginative and open to unconventional ideas, preferring the unknown and favoring intuitive leaps on their way to reaching conclusions. Social behavior diverges as well: Morning people are more likely to be self-controlled and exhibit "upstanding" conduct; they respect authority, are more formal, and take greater pains to make a good impression. (Earlier research also suggests that they are less likely to hold radical political opinions.) Evening people, by contrast, are "independent" and "nonconforming," and more reluctant to listen to authority'

</comment><comment><USER4> Are the guys who did the study early morning types or evening types? I remain sceptical...</comment>


Internet domain "www.youtube.com" was activated today 15 years ago - <AUTHOR> https://en.wikipedia.org/wiki/History_of_YouTube <comment><AUTHOR> YouTube was originally created as a platform for anyone to post any video content they desired. It was hoped that users could use the site to upload, share, and view content without restriction.

[https://interestingengineering.com/youtube-its-history- and-i...](https://interestingengineering.com/youtube-its-history-and-impact- on-the-internet)</comment>


Introduction to Machine Learning - <AUTHOR> http://alex.smola.org/teaching/cmu2013-10-701/index.html

<comment><USER2> CloudFlare is saying that the site may be down due to "excessive load." I was under the impression that this is one of the main reasons CloudFlare exists, to handle big surges in traffic like this one. Their intro video leads me to the same conclusion. Can anyone who uses CloudFlare shed some light on this?

<comment><USER3> CloudFlare doesn't proxy HTML pages, by default, because so many of them are dynamically generated. You have to add a page rule to proxy HTML too.

<comment><USER4> Thanks. I was actually under the impression that CF would do HTML as well, but I searched and you seem to be right: [https://support.cloudflare.com/entries/22036831-How-do-I- cac...](https://support.cloudflare.com/entries/22036831-How-do-I-cache-static- HTML-) So I'll try that out and see if it helps performance/bandwidth.

</comment></comment></comment><comment><USER5> Thanks for sharing. I can also recommend the CS229 Machine Learning course from Stanford, available on Coursera: <https://class.coursera.org/ml/lecture/preview>

<comment><USER6> Minor plug - if you're following the CS229A course you may find my notes useful

<http://www.holehouse.org/mlclass/>

<comment><USER7> Curious: what did you use to take the notes ?

<comment><USER8> Right on his homepage, he says:

> The notes were written in Evernote, and then exported to HTML automatically.

<comment><USER7> Oh, thanks. Don't know how I missed that bit before.

</comment></comment></comment></comment></comment><comment><AUTHOR> Alexander J. Smola's teaching the 10-701 Machine Learning class at CMU in the spring of 2013. All slides and video will be available online at the course website.

</comment><comment><USER9> On a related note, check out

<https://news.ycombinator.com/item?id=5424493>

We built a A nodejs native extension which allows you to use the popular CLIPS system to build expert systems. CLIPS is a productive development and delivery expert system tool which provides a complete environment for the construction of rule and/or object based expert systems. Developed at NASA in 1985, CLIPS is now widely used throughout the government, industry, and academia. Check out the online CLIPS documentation: <http://clipsrules.sourceforge.net/OnlineDocs.html>

<comment><USER10> Why did you use a dead rules engine? That system hasn't been maintained since 2007, as far as I can tell. I am serious. My client used it recently too. Why not use a news, faster engine like Drools or whatever JBoss is calling it now?

</comment></comment><comment><USER11> Google cache copy: [http://webcache.googleusercontent.com/search?q=cache:http://...](http://webcache.googleusercontent.com/search?q=cache:http://alex.smola.org/teaching/cmu2013-10-701/index.html&ion=1)

</comment><comment><USER12> Is it just me, or are half the resources (i.e., slides for most lectures) missing?

</comment><comment><USER13> I think this is an instance where HN's rigid title policy is a negative. It took me a minute to realize why this page, ostensibly a syllabus page for a university course, is relevant to a general tech audience. You have to scroll down past three subsections to "Resources" to realize that all of the lecture slides and problem sets, as well as videos of the lectures, are available for free. I just hope people aren't missing out on this great resource because the title can't be editorialized.

<comment><USER14> I like the Metafilter solution to that: rather than just submitting links, users submit links _and_ a short, 1-2-sentence explanation of why they think the link is interesting. I find it much easier to browse the submissions there as a result. Maybe the explanations could be hidden on the front page, but I'd find them very useful on the 'new' page.</comment></comment>


Squeegee Men Return to NYC As Jobs Fade - <AUTHOR> http://www.nydailynews.com/ny_local/2011/09/19/2011-09-19_city_awash_in_windshield_swipers_in_sign_of_desperate_times_under_squeege__again.html

<comment><USER2> You wanted change? Here it is your change...</comment>


Your project's RCS history affects ease of contribution (or: don't squash PRs) - <AUTHOR> http://mjg59.dreamwidth.org/42759.html <comment><USER4> Your commit history should be readable like your code and your tests. It's part of the final product you deliver to the rest of your team. It's easy to forget or ignore your commit history, which is probably what leads people to encouraging squashing all commits in a PR. Ugly commit history is a code smell.

I agree with the OP that it's a bad blanket policy. We are fortunate that git has powerful abilities to edit commit history (git rebase -i is my favorite). Rather than just requiring everything to be squashed as a matter of policy, maintainers should instead request that commit history be cleaned up if it's not presentable, IMO.

<comment><USER5> > Your commit history should be readable like your code and your tests. It's > part of the final product you deliver to the rest of your team. It's easy to > forget or ignore your commit history, which is probably what leads people to > encouraging squashing all commits in a PR. Ugly commit history is a code > smell.

> I agree with the OP that it's a bad blanket policy. We are fortunate that > git has powerful abilities to edit commit history (git rebase -i is my > favorite). Rather than just requiring everything to be squashed as a matter > of policy, maintainers should instead request that commit history be cleaned > up if it's not presentable, IMO.

For what it is worth, I think history is sacred. Never rewrite history (except in extraordinary circumstances and that too very rarely). Of course, do whatever you want on your local machine before pushing to remote but once you have pushed, stop worrying about it.

<comment><USER4> > Of course, do whatever you want on your local machine before pushing to > remote but once you have pushed, stop worrying about it.

This is what I'm talking about. After you push and share with others, I think you are absolutely right. Before it leaves your computer via git push to a shared location, I advocate that you should tidy things up. Thanks for clarifying...

</comment></comment></comment><comment><USER6> On the other hand, a couple years down the road, a generic pull-request-level comment (added feature foo) can be more useful than a bunch of noisy commits like

        - WIP: feature foo
        - fixed typo
        - whoops!
        - <USER2>
        - <USER3>

As is often the case with new contributors to open source projects.

In theory --no-ff merges give you the best of both worlds, but in practice, I traverse git history with 'git blame' or 'git log -p <filename>' neither of which do a good job of surfacing "this commit was merged as part of feature/foo".

Of course, all the info is there... But I haven't yet found a good UI for it.

<comment><USER7> In theory, this is why we rebase our history and make an elegant series of coherent patches. At least if "we" are the Linux dev team or something.

<comment><USER6> Yup, I agree that would be ideal. I think squash commits are a pragmatic way to deal with messy incoherent commits.

Plus it's easier to revert a squashed commit than a merge. (which is the index number of the parent I want?!)

</comment></comment></comment><comment><USER8> Some people clearly pay a great deal more attention to commit history than I ever do. The only difference this makes to me is that adding more hoops I have to jump through before you'll accept my patch makes it less likely that I will bother to submit one in the first place.

<comment><USER9> Regardless of your opinion, if you have any interest in code quality (hint: you should), then you should respect the contributing guidelines for the project you are contributing to.

Your argument / opinion as stated could have "commit history" replaced with "unit tests" and in many circles (for some reason), people are still making that argument. For a project to be healthy, a critical eye must be used for every change: from the code, to the tests, to the commit message. If you don't care about any one of these, you are saying you don't care about the quality of the software. I would deny your PR on principle. My project needs more quality than it needs more contributors.

Note that I did not suggest squashing is good or bad. My opinion on that is not related to the fact that you should _care_ about it and treat it as just as important as your contribution, and you should respect the project enough to abide their guidelines for contribution (unless your contribution is revising those guidelines).

<comment><USER8> Of course. I'm not talking about projects where I have already made a commitment to participate, though: I'm talking about the process before that, where there's some open-source project I am using or otherwise interested in, and I consider getting involved and contributing. The higher the initial barrier to entry, the more likely it is that I'll just shrug my shoulders and say "fuck it". A complex process for contributing changes, with lots of unusual fiddly steps about exactly how commits should be formatted, makes it more likely that I won't ever make that first commit - especially because the first commit tends to be something trivial where it's as much about dipping my toe in and seeing if I want to do something as about the actual change I've made.

So, yes, I certainly do respect the project enough to abide by their guidelines for contribution: but if those guidelines demand too much work of me, that respect will take the form of quietly walking away and spending my time on something else, and the maintainers of the project will likely never know I had any interest in helping to begin with. Guessing that there might be other people like me in the world, then, I suggest that having a complex and specific process for open-source contribution is likely to reduce the pool of devs willing to get involved, and it's worth considering whether the amount of work saved by requiring devs to jump through these hoops outweighs the obstacle that creates for recruitment.

</comment></comment></comment><comment><USER10> You should squash PRs. What you shouldn't do is indiscriminately squash PRs. Having a bunch of "oops, fix" and review fix commits lying around makes it harder for everyone too. It also affects bisection much more. "don't squash PRs" is just bad advice; it's more nuanced than that.

Split your work into bite sized pieces, and amend/squash the relevant fixups into these before merging.

Since these tasks can need knowledge of rebase, I offer to do them for new contributors too, which usually fixes that issue.

<comment><USER11> Use `git rebase -i` but don't squash PRs.

<comment><USER10> git rebase -i is one of the ways you can squash PRs and there are tons of cases where you should.

</comment></comment></comment><comment><USER12> I cannot disagree with this more. Commits should be feature-based, with thorough commit notes. A feature can be a one line change all the way up to something affecting hundreds of lines (or more).

High quality code standards (good variable naming, plentiful comments, etc) tell you what's happening at the code level. The commit history tells you what's happening at the feature level.

Don't pollute history with noise.</comment>


Ask HN: How do you make your blog posts last forever after your death? - <AUTHOR> Looks like HN community prefer to self-host their blogs. How do you make sure that your blog posts will still be accessible after your death? My late friend self-hosted his blog, and several months after his death, his blog cannot be accessed anymore as the subscription(s) expired. <comment><USER2> You could mirror your blog posts to a decentralized network like Secure Scuttlebutt, assuming you have a few friends who would be willing and able to follow your feed and thus mirror your content. Or it might be simpler to just email out a copy of each blog post to a little mailing list of people who care about you. Let them know that you'd like your legacy to remain public and they can probably coordinate among themselves to set up a public archive when the time comes.

</comment><comment><USER3> It is a very complicated problem. One idea I've thought about is to hide a server in the woods. You should be able to connect it with a pre-paid gsm sim card and for power have a large battery... The server should be hibernating and consuming minimal amount of energy while not serving requests.

A second option is to piggyback on other services, such as github, wikipedia (some allow personal pages in your own namespace) and various message boards. You could even mail your blog posts to Swedish government services as they would be obliged to archive it. People would "access" your blog posts by mailing the same government services and requesting all emails sent by saifulwebid on June 12, 2019 for example. Of course this idea doesn't scale and if enough people tried it they would change the rules.

Usenet posts should last a very long time too. But even those eventually vanishes and posts from the 80's are nowhere to be found.

</comment><comment><USER4> Set up a trust to pay someone to maintain them.

</comment><comment><USER5> 1\. You can't make anything last forever. Just a little while longer if you set things up correctly.

2\. Is your blog really that important, meaningful or valuable that it needs to be preserved after your death?

3\. Apart from technical solutions, writing things that people will read and share is the best way to preserve what you've created.

<comment><AUTHOR> 1\. How about posting it in a hosted solution like wordpress.com? Is it better in this case than self-hosting your blog?

2\. No, it is not (yet, maybe). But I'd like my writings to be accessible as long as possible after my death.

</comment></comment><comment><USER6> [https://posthaven.com/](https://posthaven.com/)

Sam Altman uses this.

<comment><USER7> Original discussion of Posthaven, [https://news.ycombinator.com/item?id=5229229](https://news.ycombinator.com/item?id=5229229)

<comment><USER2> Six years ago the founder said setting up a nonprofit foundation for the thing was a good idea but it doesn't seem to have happened. Their pledge doesn't mention anything about what happens when the current two people get bored of it or otherwise lose the ability to maintain it. I don't see any _clear_ reason to believe the ad copy about "lasting forever."

</comment></comment></comment><comment><USER8> Since a blog that won't be posted to any more is effectively read-only data, interested parties could receive a copy of that data to be viewed locally. It doesn't necessarily need to stay on the internet with a domain name.

</comment><comment><USER9> If you don't mind being seen in the wayback machine, you could just request your domain be scanned. [https://web.archive.org](https://web.archive.org)

</comment><comment><USER10> [https://www.pcworld.com/article/2933478/m-disc-optical- media...](https://www.pcworld.com/article/2933478/m-disc-optical-media- reviewed-your-data-good-for-a-thousand-years.html)

Any thoughts on these? If HN doesn't disapprove, you could buy these/burn your blog on them, and send them around the world. The simpler the format, the better.

</comment><comment><USER11> Obviously it will restrict the post-death reach of your blog, but the most foolproof solution would be to print our your articles and store them somewhere safe.

The average person can read a 100-year old book just fine. Digital storage changes too quickly. The average person can't really access information stored on floppy disks, and those were ~30 years ago.

</comment><comment><USER12> You could put them in the Bitcoin blockchain. That'll last as long as people are greedy, so probably a long time. Whether people will know they are there in the future I don't know.

<comment><USER5> Generally speaking, the purpose of something written is to be read. Putting text in the bitcoin blockchain is as good as writing it down on something durable and burying it deep underground. It might last a long time, but it's pretty pointless.

</comment></comment><comment><USER13> Posthaven, Archive.org, or Github Pages.

<comment><AUTHOR> Why not something like wordpress.com? I know this disqualifies the "self-host" part, but is it better in this case than self-hosting your blog?</comment></comment>


Rate my startup: Local servicer webpage + last minute YComb submission - <AUTHOR> http://www.kervu.com

<comment><USER2> Looks interesting, why does a typical user need craiglist analytics? What can they do with it?

<comment><USER3> I've only used craigslist (on the consumer side) while apartment hunting... With that said, but if I were to add a listing, it would makes sense (and be in my advantage) to track the effectiveness of my listings and optimize them for traffic and conversions

<comment><USER2> In what practical way could posters use analytics to generate better conversions? Its not exactly the same as SEO. If there is room for analytics and optimziation, maybe you should be building tools specific for craigslist?</comment></comment></comment>


You can't cancel subscriptions on Evernote - <AUTHOR>

Try it:  https://www.evernote.com/UpdateBilling.action
On the web version, after hitting cancel, it just goes back to the billing page without doing anything.
On the mobile version, it asks you to fill in a required field that is not visible, so you can't complete the form.
This is super shady, and borderline evil. <comment><USER2> And likely a bug. Did you think to contact Evernote before sharpening your pitchfork?

<comment><USER3> Definitely. They're not required to put a "Cancel" button on the web interface. If they wanted to raise the bar on work required to cancel they could easily force people to email support rather than putting a (..fake?) button up.</comment></comment>


This mystery object may be our first visitor from another solar system - <AUTHOR> http://edition.cnn.com/2017/10/27/us/mystery-object-solar-system-trnd/index.html?sr=fbCNN102717mystery-object-solar-system-trnd0418PMStory <comment><USER2> Every atom of every element heavier than iron is by definition a "visitor from another solar system", since it can be produced only by supernovae.

</comment><comment><USER3> watch for braking maneuvers....</comment>


Livestream: Making Humans a Multiplanetary Species - <AUTHOR> https://www.youtube.com/watch?v=A1YxNYiyALg&feature=youtu.be <comment><USER2> 28 minutes in, false start. Music giving way to hungry audience members grumbling about Elon Musk

</comment><comment><USER2> If I had to review the choice of music they played before the presentation started, I would tell people not to buy the album

</comment><comment><USER2> Okay, 21 minutes late, the music just got pretty wicked and Hans Zimmer-esque. Sweet.

</comment><comment><USER2> 27 minutes late, this is Old West vs. Matrix vs. Batman style symphony right here</comment>


The right time to refuse a search is always - <AUTHOR> http://peter-whittaker.com/the-right-time-to-refuse/

<comment><USER2> When someone says the "Well, if you've got nothing to hide..." argument around me, I immediate ask for their wallet/purse, keys to car & house and cell phone (with password/unlock pattern). The usual reply is something to the effect of "Why would I give those to you?" I respond with, "Because you have nothing to hide, right?"

Most of the time, the conversation quickly devolves due to the fact that I'm not the Police. Which is obviously irrelevant; but many people can't see the forest of their rights through the trees of an "authority figure".

Occasionally someone gets my point and conceeds that they, like everyone else, have things that are private.

</comment><comment><USER3> In the US, at least, the 4th amendment protections are significantly weaker at the border due to assumption of routine searches being "reasonable."

No clue what Canada's stance is on this, but worth knowing before you stand your ground with the border guard.

[http://en.wikipedia.org/wiki/Border_search_exception](http://en.wikipedia.org/wiki/Border_search_exception)

</comment><comment><USER4> Two relevant articles for those wishing to be more articulate about these points. We all should be concerned about citizens not realizing the problems derived from the "nothing to hide" argument:

[http://www.wired.com/2013/06/why-i-have-nothing-to-hide- is-t...](http://www.wired.com/2013/06/why-i-have-nothing-to-hide-is-the-wrong- way-to-think-about-surveillance/)

[http://m.chronicle.com/article/Why-Privacy-Matters-Even- if/1...](http://m.chronicle.com/article/Why-Privacy-Matters-Even-if/127461/)</comment>


The Best Entrepreneurs Know How To Fail Fast - <AUTHOR> http://www.feld.com/wp/archives/2009/04/the-best-entrepreneurs-know-how-to-fail-fast.html <comment><USER2> I'm highly anticipating a 37Signals blog post titled "The Best Entrepreneurs Know How to _Succeed Slowly_."

<comment><USER3> To be fair, they only came out with that post after the virtue of failing had been basically become received wisdom.

I'm still not sure what it means -- I hope it's fairly synonymous with "fail cheaply", or to me at least it's useless advice.

<comment><USER4> It means validate your idea quickly against real customers and do something else if they don't love it. Once you determine to do this, you find that many ideas you thought were great are total shite, so you fail fast because you don't do much development without validation. You are able to iterate through multiple concepts quickly until you arrive at one people love, and then you throw yourself behind it and get it built and get people paying.

The common mistake is to pick an idea out of your head, spend six months building it, and then find out nobody is willing to pay for that thing over the next six months after that.

Thats what fail fast means. Its the key to success.

</comment></comment></comment><comment><USER5> I read the whole thing, but you lost credibility at the first sentence. It's a proven myth that a failing at a start-up is no indicator of success at your next start-up.

The only "predictor" of future success in any world is past success. Give me a successful person with any reasonable background, and I'd prefer them to a failure as the leader of a company.

As Professor Paul Gompers says, "for the average entrepreneur who failed, no learning happened." <http://hbswk.hbs.edu/item/5941.html>

<comment><USER4> I would suggest that failing at a startup and demonstrating that you've learned from that failure would be a strong indicator of success. There's so many common lessons people learn.

<comment><USER5> Before just repeating the fallacy, why don't you read the HBR link I posted. As it turns out, what you say is just not true, when actually measured.

On what basis would you suggest otherwise? Anecdotal evidence from a bunch of failed entrepreneurs who want to believe the experience helped them?

<comment><USER4> I didn't repeat the fallacy, I characterized his talk. He's explaning that he learned an awful lot about metrics.

Failing is one thing, demonstrating that you've learned is another.

</comment></comment></comment></comment><comment><USER6> The best entrepreneurs know to not waste time reading this garbage and work on their startup instead.

<comment><USER7> To be fair, keeping up to date with information and learning new things is a must for a entrepreneurship. You really cannot decide if it's garbage before reading it.

But on a side note, I think web related entrepreneurs should definitely stop wasting time Tweeting and Blogging about their development, and instead actually do development.

</comment></comment><comment><USER8> I hate this "fail fast" advice, and just about the only place I've heard it is from VCs, who (a) don't like slow success, and (b) don't mind failure as long as it is balanced with successes in their portfolio.

The problem with the advice is that it obscures two of the most important qualities that a startup needs: tenacity and adaptability.

</comment><comment><USER9> Not fail fast, but more like know how to retool what you have into another business.

A friend of mine became a hugely successful used-laptop vendor because he learned the ropes of the industry while trying to liquidate the equipment of his failed business (he only had 20 laptops to sell and found the low prices buyers were offering for bulk used laptops vs the high street retail price for single units.)

If my current start up doesn't pan out, I have about 5 different business automation solutions I can take to the market .. or maybe even when it's successful ;-)

</comment><comment><USER10> Well, it really should be "The Best Entrepreneurs Know How To Learn From Their Failures"

<comment><USER11> How about "The Best Entrepreneurs Don't Fail"

</comment></comment><comment><USER12> So, he does raise a great point about being obsessed with metrics. This is key to building and running any stable business. Love your numbers.

I think good product people are combination of:

1\. obsessed with metrics

2\. knowing what to measure

3\. using these two things and their knowledge of their market to know what to make

I don't think just trusting your numbers and obsessive A/B testing is enough. It definitely helps though.</comment>


Is it time to develop some open source HDD firmware? - <AUTHOR> https://www.reddit.com/r/ReverseEngineering/comments/1g8kzc/hdd_firmware_where_to_start/

<comment><USER2> YES.</comment>


Headless unit testing of Raphael.js is possible, and it's awesome - <AUTHOR> http://www.trottercashion.com/2010/04/27/headless-raphael-testing.html

<comment><USER2> This is a bad example -- the unit test is just a recapitulation of the implementation! I hope the real tests aren't like this, in which case a real example would be a lot more convincing.

<comment><AUTHOR> Yea, the purpose of the test is more to assert that the correct things are being called on Raphael. Since the actual code is so simplistic, these tests really aren't testing that much. In our actual implementation, the tests are actually testing legit logic.

I think that more important point of the post is that it _is_ possible to test javascript graphics on the command line. That's something that's typically considered fairly difficult.</comment></comment>


Eboard Mail a new secure messaging platform - <AUTHOR> http://Eboardmail.com <comment><AUTHOR> I have heard all of your comments and issues regarding requiring a phone number for signup and some email addresses being recognized as invalid. I am working on this with my developers.

I am going to make the phone number field optional. Until that time you can enter all 0s if you don't want to put in your phone number. The reason for the phone number entry is to allow for purely informational SMS notifications. No actual message content is sent with the notifications, just that you got a new message or contact request. In the future I am planning a sandboxed app that would handle notifications.

I am also going to resolve the email address error. I will work on ensuring that all email addresses can join.

This is very valuable feedback and I appreciate it very much. If you have further feedback please don't hesitate to post. I take all of the comments seriously and want to get all issues resolved.

</comment><comment><AUTHOR> Eboard Secure Mail is a web based private messaging platform that is a more secure communication solution than current email systems. This is a change in the long standing paradigm of the current plethora of email solutions. To be clear this is not email. This is a system that gives you a familiar web-mail like interface but builds into it the ability to only send and receive messages from approved contacts. Along with it's secure push notification system for new messaging events, it provides a safe and secure solution to the chaotic, expensive and insecure email environment that individuals and businesses operate in today.

</comment><comment><USER2> Hah, it claims that my email address is invalid, even though I've been using it for at least a decade.

<comment><AUTHOR> Is the email address in the standard format? Let me know so we can resolve any issues.

<comment><USER2> What do you mean by "standard format" exactly? My email address is in the format email@example.com and I have sent messages from and received messages to that email address for at least a decade.

</comment></comment></comment><comment><USER3> Why do you hijack the back button?

<comment><AUTHOR> I can have that resolved. This is still in beta so I appreciate the feedback.

<comment><USER3> It's clearly intentional: the url has #no-back appended

<comment><AUTHOR> If it is really an issue it can be removed. I appreciate your feedback.

</comment></comment></comment></comment><comment><USER4> Phone number required?!! You have to be kidding!

<comment><AUTHOR> The phone number is so you can get SMS notifications.

<comment><USER4> Seems really redundant/invasive for a secure communication system! How about at least making it optional??!! What if I do not trust my phone to handle such notifications? So many points I can come up with why this is a bad idea.</comment></comment></comment>


I'm surprised they didn't add "Expert at moonwalking" to the skills list - <AUTHOR> http://www.jobstheword.co.uk/Job/Info/1186/Digital_Designer/Guildford/Allianz

<comment><USER2> Sounds like they just lost a jack-of-all-trades by refusing to pay him what he's worth as he improves... And now they're trying to find another for the same price.

Imagine their surprise when they find out that's actually a job for 3-5 specialists at those prices.

</comment><comment><USER3> Well, it seems right for the Huuuge salary they offer!

<comment><USER4> > £22,000 - £32,000 + bens

That's per quarter, right?</comment></comment>


Motorola takes aim at Apple and Samsung with new Moto X and Moto G smartphones - <AUTHOR> http://www.networkworld.com/article/2954292/opensource-subnet/motorola-apple-samsung-new-moto-x-moto-g-smartphones.html?nsdr=true

<comment><USER2> Look, I know standards are pretty low in the advertorial mill that laughingly passes itself off as tech journalism, but does no one proofread even the bolded attention-getting text, much less articles, any more? Current lead-in to the source article: "As a Google Google company, Motorola's Moto X design wow'd reviewers and consumers. Now part of Lenovo, Motorola's and new supply chain extends its proven design with very competitive prices."

Motorola was "Google Google company"? "Motorola's and new supply chain"?

The article's not much better.

Why not just link to the official announcement blog post _from_ Motorola [0] rather than something that's just as much of an ad, contains _less_ substantive information about the products, and is less readable?

[0] [http://motorola-blog.blogspot.com/2015/07/find-your- perfect-...](http://motorola-blog.blogspot.com/2015/07/find-your-perfect-moto- match-with-all.html)

<comment><USER3> The submitter user name shares many letters with the author of the article, so that perhaps explains why they chose to submit it over any alternatives.

They submit a lot of their own articles but I guess they are generally topical and not overly frequent. I'd prefer a more direct statement about the relationship between the submitter and Network World (either in the teaser comments they post or their profile), but there isn't much of an attempt to hide anything.

</comment></comment><comment><AUTHOR> Pure Android, extensive features, top-tier differentiated design at prices below industry leaders Apple and Samsung are intended to tease consumers to look at the line up and consider a direct relationship with Motorola.

Motorola's chief designer Wicks created innovative solid phones in earlier versions of the Moto X and Moto G. He's done it again with the latest phones released yesterday. It remains to be seen if Motorola can create a direct relationship with consumers using Moto Maker for customization, online services and social media.</comment>


What happens after you're arrested at a protest in New York - <AUTHOR> https://medium.com/@noralev/what-happens-after-you-re-arrested-at-a-protest-in-new-york-975bb34fb47c <comment><USER3> > This was super distressing for a lot of people, as those belongings usually > included wallet, phone, and keys. So after you are done at Central Booking, > you are basically left with no possessions or money, and no way to get into > your home or contact anyone.

Please, someone tell me this is fucking illegal.

<comment><USER4> This is standard fare for any police department ever.

It took me about 4 months to get my phone back from the NYPD, which was fun.

I love it when white people are shocked by their first arrest, because it (unfortunately) means something might get done. The system sucks. Now please scare other white people about it.

<comment><USER5> "I love it when white people ..."

It's unclear to me why race has anything to do with this. Are you implying that you expect non-white people to handle "their first arrest" more casually, as if it is something they are familiar with and know will happen?

If we really want things to improve, we need to stop complaining about how "white people don't see how bad it is for the rest of us." Focus on what we have in common, not what you arbitrarily perceive as what makes us different. The system is shitty for everybody. Your argument would have been just as informative and a lot more pleasant to read if it didn't begin by partitioning your readers by race.

<comment><USER4> I'm white. Systematic injustice has a funny way of being swept under the rug for years, decades and centuries when it doesn't inconvenience us or when powerful people of our race benefit from it.

Swaths of people go through this regularly or are targeted and treated, much, much worse than this guy for the sole virtue of being the wrong race. Somehow, many white people, especially those in the upper class, never have to see this injustice ever.

There's a reason MLK's strategy during the civil rights movement worked. It inconvenienced or scared white people into seeing the injustice of the system they are a part of and control.

Police brutality and injustice is a side of America we are privileged to be mostly excluded from. When it becomes our problem, the system at least attempts to correct itself.

As an aside, for many people I know, the whole police brutality meme really started brewing when it became common knowledge that cops can come into your house and shoot your dogs. It doesn't and didn't matter that has been going on for decades to those of the wrong race or religion, often with deadly consequences.

</comment></comment></comment></comment><comment><USER6> > _for every one of the 120+ of us in holding, there was also a cop who was > waiting there too, being paid overtime and trying to get our paperwork > processed so that they could go home_

Cops being paid overtime is a tremendous conflict of interest motivating them to arrest and to process slowly.

<comment><USER7> I doubt very seriously that any cop does not find the manual paper entry and time wasted a good thing. More than likely they wanted to go home just as bad as the "perps."

<comment><USER8> But it is a potential conflict of interest, hence it is something worth addressing, no? Especially it's in the best interests of both the cops and the people.

<comment><USER9> Then again, you could be seen as _punishing_ the cops for making a (possibly good) arrest by forcing them to spend long hours processing paperwork and not getting paid. Though, I do agree that the current situation is stacked in a bad way.

</comment></comment></comment></comment><comment><USER10> NYPD needs to be disbanded. If you have officers repeating the same conduct one just got charged with depraved heart murder for, it's out of control.

This stuff is simple enough. Get out of your escort, stand among the other normal people and do some dogfooding of the police experience. I guess nobody higher up wants to spend the day doing that, because at the end of it there wouldn't be anyone still employed at NYPD.

<comment><USER11> When they expressed insubordination by turning their backs on the Mayor, that signalled to me that they have no respect for authority. This is exactly the kind of people that do not belong on a police force. I can't imagine why they weren't all fired. They certainly don't deserve any of the respect that they get, nor their pensions.

<comment><USER12> What? They are allowed to express their right to free speech and expression as well, just as the protestors should be able to.

<comment><USER13> Legally, they do not have the right of free speech when in uniform. See Garcetti v. Ceballos: [http://scholar.google.com/scholar_case?case=6711908971660042...](http://scholar.google.com/scholar_case?case=6711908971660042297&hl=en&as_sdt=6&as_vis=1&oi=scholarr)

And as a matter of principle, they should not. When in uniform, a police officer is not a private person, who has rights, but rather a representative of the government, which does not have rights, but authority delegated to it by the people.

Further reading, from an actual lawyer: [http://blog.simplejustice.us/2014/10/18/ferguson-revenge- of-...](http://blog.simplejustice.us/2014/10/18/ferguson-revenge-of-officer- keith-novara/)

<comment><USER14> Neither of your links support your case.

In the first link, the case is about a memo written as part of the employee's role; a uniform is irrelevant (district attorneys don't wear uniforms, and the word 'uniform' is mentioned zero times in the document).

In the second link, the article _explicitly_ states: _" Wearing a badge doesn't forfeit the free speech of the person"_. It's abundantly clear that these police turning their backs on the mayor at a funeral over a political stoush between the parties are not acting as voices of the government. No reasonable person would even remotely think that the police turning their back on the mayor is 'what the government message is'. Those police are _clearly_ not 'speaking' in an official government capacity (and literally are not speaking at all).

I have no great love for the police, but the correct path forward is a fair view, not a knee-jerk 'fire them all on principle'. This thread is full of knee-jerk hysteria, but the irony is that so many people are calling for an end to multiple people's careers because, while not on duty, the were literally standing still while facing the incorrect direction. Ironic because it's supposedly a reaction against undue application of power, and yet the punishment for facing the wrong way is termination, regardless of whether or not that officer has abused power elsewhere.

<comment><USER13> > In the first link, the case is about a memo written on duty as part of the > employee's role; a uniform is irrelevant (and the word 'uniform' is > mentioned zero times in the document).

The facts are not identical, but the facts are sufficiently similar that you could cite that case as precedence for arguing that the facts in question here should be treated similarly. The lawyer I linked to certainly thinks so. Are you a lawyer?

> In the second link, the article explicitly states: "Wearing a badge doesn't > forfeit the free speech of the person".

You took that out of context. "Person" here means the _private_ person, not the cop representing himself as a cop. The paragraph goes on to say, "the speech of a person who presents himself in his official governmental capacity is no longer the individual's free speech, but the official person's speech. And the latter is not free."

<comment><USER14> Speaking of taking things out of context, did you read the rest of my paragraph, which talks about private speech versus official capacity, and matches the context surrounding my quote from the article?

 _in his official governmental capacity_ were the words - <USER2> funeral/protesting police were not on the clock on active duty, and as I said, no-one sane would confuse their message with a governmental message, official or unofficial.

 _Are you a lawyer?_

?

It's clear neither of us are. So what? You're still misreading the second article re: private vs offical personage. That article is not saying what you're claiming it says. And as a result, the first link you provided is also not supporting your claims. The lawyer you linked to says _absolutely nothing_ about uniforms - the term (and concept) 'uniform' appears nowhere in the article, but it does talk about the loss of freedom of speech when speaking in an official capacity.

And no, 'in uniform' is not the same as 'official capacity'. In none of these cases are they equivalent: the district attorney doesn't wear a uniform; Novara's phone call was about abusing his official capacity, and he could have been in the nude when he called, for all it mattered; the police turning their backs at the funeral are _clearly_ not acting as a government voice and couldn't be confused to be doing so.

</comment></comment></comment></comment></comment></comment></comment><comment><USER15> Perhaps it time someone built a web site where the opinions, comments, and especially actions/votes, of every politician running for office, from City Council on up, were tracked.

Scoring the politicians based on their support for the constitution and especially human rights, plus encouraging the vote, could fix this after just an election cycle or two.

<comment><USER16> How about try to increase voter turnout first? No amount of public education and politician tracking will be useful if only 1/3 of eligible voters actually vote.

[http://www.washingtonpost.com/blogs/post- politics/wp/2014/11...](http://www.washingtonpost.com/blogs/post- politics/wp/2014/11/10/voter-turnout-in-2014-was-the-lowest-since-wwii/)

<comment> vezzy-fnord Low turnout is an acceptable response to an inefficient system where majoritarianism, gerrymandered districts, ballot access laws, etc. culminate in a meticulous engineering of the odds being stacked against the voters.

Though, for some reason, voting and "democracy" elicit such warm conditioned feelings that people are willing to desperately scrape for examples of whatever small local victories they've secured in order to justify that it's worth going through the whole jungle. Electoral reform, though? Dead end.

</comment></comment></comment><comment><USER17> It's ridiculous that they're allowed to waste so much of our time, taking hours to fill out paperwork with pen and paper as if it's the 20th century. That needs to change. And police officers taking selfies with the people they arrested and boasting about it on social media should be arrested. So fucking unprofessional.

</comment><comment><USER18> > The police officers in the front of the wagon were taking selfie videos of > the crazy race-car style driving and posting to Snapchat stories that they > shared with each other and boasted about openly in front of us, laughing.

Mind blowing. The behavior part of the nation is completely up in arms about, they still see fit doing.

</comment><comment><USER19> It's out of print and kind of hard to find, but if you can get a copy of "Rough Justice: Days and Nights of a Young D.A." by David Heilbroner [1], it is well worth it. (Don't confuse it for the at least 10 other books whose titles start with "Rough Justice"...).

Heilbroner was a fresh law school graduate who took a job as a New York D.A., and then wrote this book about his time there. He started out handling misdemeanors, and there are a LOT of those. There's basically an assembly line, running all day and all night, to bring in those who have been arrested, get their paperwork to a D.A. for charging, get the arresting officer in to make a statement, and getting a hearing before a judge where the defendant usually pleads guilty and gets a fine.

The Public Defender has a similar assembly line going.

When his shift would start, he describes walking into the office, stepping over or around all the officers sleeping in the hall waiting to have their statements taken, then picking up all the cases that the previous shift was working on when their shift ended. Often he'd end up in court with a stack of cases he'd never seen, and have to frantically work to read the notes from the previous shift and skim the officer's statement as the case was being called.

When his shift ends, the cases he's working on are handed off to someone on the next shift, and almost always will be resolved by the time his next shift comes around. So there is no engagement with the case, he's just a cog in the machine, processing his pieces of paper as the pass through, and occasionally taking statements from officers, and reading from these pieces of paper in front of a judge.

Eventually he gets to handle felony cases, which for both the D.A.s and the Public Defenders are more like what they had in mind when they were in law school imagining what their jobs would be like--taking a case all the way from charging through to a trial, and actually making serious legal arguments.

It's quite an eye opener.

[1] [http://www.amazon.com/Rough-Justice-Nights- Young-D/dp/039458...](http://www.amazon.com/Rough-Justice-Nights- Young-D/dp/0394581911/ref=la_B001KDVXT8_1_1?s=books&ie=UTF8&qid=1430629926&sr=1-1)

</comment><comment><USER20> "My arresting officer walked me out the door and down the street past the barricade, where there were volunteers from New York Lawyers Guild waiting to provide information on legal resources, as well as donuts and coffee."

That must've been a sight of relief. What a horrible experience everyone had to go through. This is nothing short of intimidation tactic.

<comment><USER21> I don't know how I feel about that. I mean on the one hand, it feels like ambulance chasing, but on the other, they're providing the exact thing everyone leaving those cells needed. Food, drink, legal advice.

Do you think turf wars start with competing law-firms over that spot?

<comment><USER22> It's nothing like ambulance chasing.

Their work is pro-bono and the engagement technically starts a bit earlier than leaving jail. The lawyers guild is also the group that fields observers to record what demonstrators/police have actually done in protests.

Also the coffee/donuts are usually a separate set of people, lay volunteers up in the middle of the night trying to keep track of people to make sure they're processed quickly enough, or to give them said coffee/donut or a couple of bucks to catch the subway home. The keyword you're looking for is "jail support" [http://organizingforpower.org/jail-support- solidarity/](http://organizingforpower.org/jail-support-solidarity/)

</comment></comment></comment><comment><USER23> I have a really basic question: What crime was she being charged with? Protesting?

<comment><USER24> Have you considered that reading the article might give you an answer to this question?

<comment><USER21> It's easy to miss things. Sticking a piece of information in the middle of the 10th paragraph is a great way to hide it.

<comment> lloyd-christmas I respect that things need to be done, but I couldn't breath through the stench of an agenda/propaganda while reading half the article.

<comment><USER21> Could you tell me what the agenda was? I didn't catch it...

Other than making the NYPD look bad of course. That I got.

<comment> lloyd-christmas "...and the metal bench was designed to be cold and uncomfortable."

Yep. I'm sure they went out of their way just to make her uncomfortable. From reading the article, I picked up on a person that steps outside just hoping to be offended.

<comment><USER21> Ah, you're saying that her objective from the start is to make the NYPD look bad, so she's ham handedly complaining about things that are innocuous.

That's fair, I got the sense from your first post that the article had some kind of mystery undercurrent of anti-abortion sentiment or something.

</comment></comment></comment></comment></comment></comment></comment><comment><USER25> Yep and people are surprised when violence suddenly erupts against the police.

<comment><USER26> No, those people have guns. It's usually against the people in your community that had nothing to do with it.

<comment><USER27> Even in the places where the police don't have guns, like London.

</comment></comment></comment><comment><USER28> I'm not from the States - when this kind of thing happens, does it affect your future employment opportunities? Will it turn up on background checks?

<comment><USER20> it depends on the states. Some states offer more protection for applicants than others. It also depends on position too.

Basically, any arrest record will stay on your record for number of years including ones where the charges were eventually dropped. But in many states, employers are either disallowed or discouraged from looking at it.

If there was conviction, it will stay with you. There is no way getting around that and that will jeopardize your future employment prospect.

</comment></comment><comment><USER29> I honestly didn't think you could be arrested for protesting like this without at least a warning and even then if only if it turned violent...

<comment><USER16> From what I've read, there had been plenty of warnings all day.

>The group was on East 17th Street about halfway down the block when police took a stand and ordered protesters to get on the sidewalk. Before the march, while the group was in Union Square, police handed out flyers and used loudspeakers to warn protesters that they would be arrested if they didn't stay on the sidewalk.

[http://7online.com/news/more-than-140-protesters-arrested- in...](http://7online.com/news/more-than-140-protesters-arrested-in-new-york- marches-/687689/)

Here is the flyer that they were handing out: [https://twitter.com/Azi/status/593536703324905473/photo/1](https://twitter.com/Azi/status/593536703324905473/photo/1)

I mean, look at it that other way. People should not be able to openly obstruct traffic. If I were to go run out in the middle of Broadway and block traffic, I would probably be arrested. Just because someone is "protesting" doesn't give them free reign to violate the laws.

This is why public marches/protests require a permit. These guys did not have a permit to do so. See: [http://www.nyclu.org/content/know-your-rights- demonstrating-...](http://www.nyclu.org/content/know-your-rights- demonstrating-new-york-city)

> You may be able to march in a public street (as opposed to on a sidewalk) in > some circumstances. To march in a street, you must obtain a permit from the > Police Department. If you expect to have fewer than 1,000 people in your > march, you can apply for a permit at the precinct in which the march will > originate. If you expect 1,000 people or more or you prefer to use mail, > send your application to: NYPD Investigation Review Section, 300 Gold St., > Room 305, Brooklyn 11201. You can download a permit application from the > front of the NYPD's website

<comment><USER30> The right to peaceable assembly in the First Amendment of the Constitution SHOULD mean that the government cannot require a permit to do so (otherwise, it wouldn't be a RIGHT).

If a large number of people want to get from point A to point B, even on foot, an accommodation of normal traffic laws should be made to allow that.

Why the hell are police arresting peaceful protestors?

<comment><USER16> If I'm reading what you're saying correctly, this is EXACTLY how it works.

The protesters were allowed to peacefully assemble in Union Square. The protesters were allowed to peacefully march on the sidewalk to anywhere they wanted to go in the city.

What the protesters were NOT allowed to do is obstruct traffic and walk in the middle of the street without a permit. The people that were arrested were the ones that were walking on the streets and blocking traffic.

You only need a permit if you intend to march on the streets. It's the same as you or I needing a permit to host a parade through Midtown.

</comment></comment></comment></comment><comment><USER31> >> I was never read my rights

I thought this was only necessary if the police are going to question you.

<comment><USER32> I thought when arrested and charged with a crime.

IANAL obviously.

<comment><USER33> It appears that it is only necessary when there is going to be questioning/interrogation: [https://en.wikipedia.org/wiki/Miranda_warning](https://en.wikipedia.org/wiki/Miranda_warning)

Though, it seems as though the police can skip the miranda rights bit and interrogate, if they don't want to use subsequent statements or information in court. There's also the "public safety exception", which doesn't seem to apply for the situation in this particular account.

</comment></comment></comment><comment><USER34> For the data driven types, here is some data from the Economist:

[http://twitter.com/TheEconomist/status/594593671661641728](http://twitter.com/TheEconomist/status/594593671661641728)

</comment><comment><USER35> The system is beyond saving, it's only a matter of time until the people start rioting and killing cops as a personal vendetta... oh wait.

</comment><comment><USER36> This sounds like a totally positive experience compared to how it could have gone. Not to mention, a giant waste of money.

</comment><comment><USER37> Maybe the accelerometers in people's devices could be used to record rough- riding incidents. There should probably be "black box" devices in all police cars to prevent incidents like the one that allegedly killed Freddie Gray.

</comment><comment><USER38> > I just got back from 12 hours in NYPD holding. If I can get arrested (with > all of my white privilege and generally perceived non-threatening stature), > so can anybody. ... Obviously I don't know what happened in each person's > actual arrest, but I do know that the criminal charges overwhelmingly fell > to people of color and those with more masculine gender presentations.

One of the most distressing things I find about the language of 'privilege' is that it denies that women can have it as a group. In this last sentence, she recognizes that women can be privileged over men in some situations.

<comment><USER39> Privilege theory generally asserts that everyone has some privilege in some situations. It's just that there's a lot of imbalance between groups in terms of how often and how much your personal privilege benefits you.

I think you're attacking a strawman here. I'm sure there are people who say that women have no privilege ever and men have all of it all the time, you shouldn't judge the entire concept based on the angriest 15-year-old Tumblrers.

<comment><USER40> Why are you so sure that the 15-year-old Tumblrinas are not the true Scotsmen?

I mean, it's clear that you're defending a more reasonable version of the claim and GP is attacking a more unreasonable one, but it's not clear to me which of those is going to win out as the common understanding associated with the expression "privilege theory".

<comment><USER39> I think that the "common understanding" of pretty much any political idea, no matter where it lies on the spectrum, is going to be mostly composed of soundbites and tweets and memes, because those are the easiest to ingest and repost. It's easy to get a strawman idea from that, but to get to to the heart of an idea you need to read the TL;DR stuff too.

If you're afraid that the superficially furious people are going to win out over the reasonable, thoughtful people on issue X, then the best thing you can do is try to understand issue X and promote the reasonable approach to it. Just saying "All Xs suck as proven by this misspelled Tumblr post" will only further polarize the dialogue and help shout down (or radicalize) the reasonable people.

<comment><USER41> I love it when a conversation moves beyond the typical argument and counter- argument. Thank you!

<comment><USER39> You're welcome! I've been making a conscious effort to be less of a curmudgeon online these days. I got tired of being angry all the time.</comment></comment></comment></comment></comment></comment>


IPad & iPhone graph paper for designers and developers - <AUTHOR> http://blog.ablepear.com/2010/05/pad-iphone-graph-paper-for-designers.html <comment><USER2> Finally...something for those of us who still like to wireframe by hand. There are some nice apps for this for the iPad now, but during a brainstorm I still find it faster to express ideas on paper.

</comment><comment><USER3> Nice, thanks! These are helpful.</comment>


Ask HN: Whats your opinion about open office spaces - <AUTHOR> I work out of an open office space and often find myself distracted from the noise and people moving around. One strategy I use to focus on my work is listening to white noise using a headphone during work-which do not look like a sustainable solution. Am I the only person who finds the idea of open office space annoying and counterproductive. <comment><USER2> Absolutely hate open offices, and I find it depressing how every startup, agency and large business nowadays seems to use them. It's even worse when you're on the autistic spectrum, are an introvert or social anxiety, since the open office is basically tailor made to drive such people insane.

Makes me wish remote working was more common in general, as well as that bosses would stop being so obsessed with what's 'trendy' and think of their workers.

</comment><comment><USER3> I suffer from open office space as well. I share the office with marketing and sales people. Depending on what concentration level I need, I sometimes just stop working and wait for some silence or just go home.</comment>


The Invisible Touchscreen iPhone Is Now A Reality - <AUTHOR> http://jaxov.com/2011/05/the-invisible-touchscreen-iphone-is-now-a-reality/

<comment><USER2> I wonder whether this has any practical use. Touch screens already remove physical feedback and it's very hard to use them with your eyes closed when you can't confirm your actions in any other way than looking, unless you have accessibility software. Now, with this "invisible touch screen", not only can you not see the phone, but instead of moving your fingers on a smooth surface, you use something that is neither smooth or comfortable and it certainly isn't the same shape as an iPhone screen.

Besides all that, when the technology can detect any gesture, why limit ourselves to arbitrarily tapping our hand. It would be a lot more useful to just bind a few simple gestures to features that you use often.

<comment><AUTHOR> I guess your last point says pretty much everything.. What is interesting is not what they show here, but what can be done with it.</comment></comment>