pessimism

The law involves confiscating valuables and money, but it does so much more than that, including, but not limited to, increasing the waiting period for family reunification.

People put it in quotes, because they think it gives them an excuse to use the misnomer, which is bad journalism on their part.

It’s basically in the interest of the administration that people only thought the bill concerned jewelry confiscation, as it distracted from all the other heinous things in the text.

The former bill, which has since become law, is L87 (ie Bill 87).

His former boss and predecessor Anders Fogh Rasmussen was Bush’s biggest supporter and ditto on the Iraq War.

He has a vested interest in ignorance of the past—so much so that he shut down the investigative committee for the very same war as one of the first things when he won the election last year.

Oh yeah, that’s just quoted text from the original article, which deals with the phenomenon: https://ndarville.com/blog/2015/12/04/web-fonts/. It’s not directly relevant to the aforementioned article. :)

GIFs are so stupidly easy to use and distribute that I sometimes can’t wrap my head around how convenient the format is.

A while ago, I tried to be a good nerd and convert some GIFs to HTML5 video, and I crashed and burned pretty hard: https://ndarville.com/asides/webvideo/.

I gained a new appreciation of GIFs that day.

That said, it would be great if we got a compromise where browsers can load only the first frame of the GIF and play the reminder on click or touch to save all the loading and data—on both sides, really.

If anyone has a good library or a pro tip for making responsive charts, I’d love to know; I am somehow still having trouble implementing it:

* http://bl.ocks.org/ndarville/11094667

* https://github.com/ndarville/d3-charts/issues/11

I love public transportation, and I love how good Denmark is compared to other countries.

But this is not to say that we haven’t had absolutely execrable forays with our trains: https://en.wikipedia.org/wiki/IC4.

What I mean to say is that, sometimes, public transit is less something to “figure out” than something to “get right”. We got public transportation right, but we’ve been doing our darndest to fuck it up on multiple occasions.

You get a message in the top bar to “upgrade”, but you can’t click it, and if you’re not a nerd who follows tech news, you wouldn’t know that Microsoft want you to use the new Outlook app instead.

So the effectively broke all Exchange/Google-related updates for people at work and home, since the app stops to fetch updates—I stopped receiving e-mails from what I can tell.

Can you describe the service? It’s blocked in my country, apparently.

It’s an old list by now, but I keep updating it; you can also contribute to the original list (http://news.ycombinator.com/item?id=4924647) on which this was based.

I’m sure you have more great suggestions for what can go on the list; new models keep popping up with companies like Patreon.

Feel free to—also—post your suggestions on the Gist. GitHub currently does not support notifications for gists, so don’t get mad if I don’t get back to you. :)

I once used a SaaS—or whatever you call the abstraction on top of that—and ended up paying $80 for a “sample” EC2 instance of theirs that was just idling, after I had activated it a month earlier.

Soured me on trying out new platform services pretty damn hard.

Communicating the progress of a project or feature is something really important I think open-source people need to realize, when they have a fairly non-technical audience.

I think GitHub milestones are central to productivity and communicating progress to a base of interested parties, so I would recommend focusing on milestones specifically—also to encourage their use—rather than showing one huge list of issues by default. It’s fairly disorienting, even to me as a regular GitHub user and contributor.

Those cards take up an awful lot of vertical space, which I don’t think is going to scale well with a large project. Look at project like Bootstrap: https://waffle.io/twbs/bootstrap. Because you load the issue on scroll, I can’t even get an idea of how many issues there are from the size of my scroll bar. Milestones are the main way for repo owners to manage a large number of issues.

From what I could tell, you can sort by milestones using a filter, but for some reason, the list of milestones wouldn’t load?

A while back, I created a small never-to-be-finished project called milestones.js to involve a general audience in the progress of upcoming features—taking advantage of milestones: https://github.com/ndarville/milestones.js. At the bottom of the README are some related projects that might be of interest to you as well.

In other words:

1. Find out who you want your users to be.

2. Find out what they should be shown.

3. Focus on milestones, GitHub’s killer productivity feature.

4. Fit more issues vertically; the card metaphor isn’t that important.

5. Know that the dynamic loading of issues on scroll is working against you from a UX perspective.

Funny you bring up the aspect of saving the trees, because I followed up the post with a suggestion for how Google can reduce the waste by taking more control of the print experience in Chrome: http://www.modrenman.com/2013/05/01/save-the-rainforest-goog....

More than anything else, I just wanted to bring attention to something I think many people don’t know about, because I think it’s mostly a case of people not minding printed web pages rather than them not caring.

Over the many hacks (breaches, as companies prefer to call them) we’ve come to see, as a user who at times felt nervous about how I was affected, I have tried to write a simple guide for how companies can disclose a hack in a way that will assuage my concerns in the best way possible: https://gist.github.com/ndarville/5072091.

I originally intended to convert it to a disclosure generator, but I haven’t had the time.

I hope it can be of some help to you in dealing with this awful situation, and I’m terribly sorry this happened to you.

Any people here who go to the dentist?

   Specifically, the American Dental Association's 
   guidelines for heathy persons suggest that
   
   * children receive 1 x-ray every 1-2 years,
   * teens every 1.5-3 years,
   * and adults every 2-3 years.

I was personally very surprised and alarmed by this.

A while ago, someone compiled a list of Web and Mobile Revenue Models: https://news.ycombinator.com/item?id=4924647.

I put the list on GitHub and updated it with new concepts I found interesting every now and then: https://gist.github.com/ndarville/4295324.

There should be something there to pique your interest.

Please ban comments empty-linking to Wikipedia articles.

At the very least demand they contain, say, ten characters of contextual wording to discourage this lazy kind of argument.

As someone with severe dust-mite allergy (that went undiagnosed until I was 18), please consider cleaning your space—regardless of who you are. Clean houses are more than status symbols.

As someone with open projects on GitHub that may or may not be a future source of income (lol), specific and succinct language on the licensing is probably your best way to ensure adoption of your product.

I just cannot be bothered to risk using an icon font in a GitHub repo only to have to bleach every trace of it, because I misunderstood the license or the author’s intent.

To help remember just how the hell the most popular “free” font icons are licensed, I created a gist: https://gist.github.com/4443939. There is no way that overview looks simple to anyone.

This is what I as a developer think about as the very first thing, when I see a collection of free-asterisk icons.

The cognitive load of parsing the legalese, especially from the standpoint of someone with zero jurisprudence is a huge toll and reason for my personal bounce rate on similar products.

Consider what the point of your free icons are (portfolio vs. seeing your icons everywhere), and how you wish to stand out (quality vs. licensing).

They say cache invalidation and naming things are the hardest thing in programming, but licensing is definitely up there; at the very least, it is something most people in the field do not—but should—understand.

+++

tl;dr: If you launch a set of free(*) icons, crystal-clear licensing should be at the top of your checklist.

@Brown_Moses (https://twitter.com/brown_moses) is one of the best people to follow on these subjects.

Eliot is an interesting example of one a single well-connected individual can accomplish in the digital age: http://www.indiegogo.com/projects/the-brown-moses-blog/x/255....

His feed is a bit of a firehose feed, so I recommend you only follow him, whenever you need to immerse yourself in an ongoing story.

The things going on in Turkey are so insane, they have to be seen to be believed.

EDIT: His YouTube playlist with videos of the clashes: http://www.youtube.com/watch?v=zvUktDH-OBM&list=PLPC0Ude....

I get a 500, when I try to sign up using GitHub.

Happens at

    https://crate.io/social-auth/complete/github/?code=123

Any idea why the prerendering fails?

http://i.imgur.com/pxijNnq.png

http://i.imgur.com/QxcNIeO.png

Thanks for the help, by the way. :)

You should check out Microcosm (http://microco.sm/), which is my favourite of the upcoming paid forum CMSes out there.

The API documentation for Microcosm is seriously impressive, especially at this stage: http://microcosm-cc.github.io/.

I have my own pet project at http://pony-forum.com, but it’s more of a hobby project at the moment. But I think it’s also too early for non-technical users to use the CMSes listed in the article; they’re more like alpha or beta versions at this point.

I tried implementing it for my blog’s pagination, but I definitely don’t see the zero-second latency Google report in the video, and it doesn’t seem any faster at all.

Can you tell me if it’s actually working from using the pagination at the bottom of the front page, or the pagination inside the permapages: http://pygm.us/1e9KHCYt. (Link fixed.)

Exactly. It’s why I hope people will see this not so much as a new frontier of telecommunication nor telecommuting, but “telepresence”.

It’s not a medium; it’s a physical proxy.

I hope people will see it as more than a convenience for working remotely.

I would consider it an outright bug, if that were the case, so I wouldn’t worry about that.

I haven’t added any photos to my favourites, so I can’t test it for you, alas.

@YahooCare are very quick to reach out, if you direct any questions at them, as shown in the last of my footnotes. It’s actually really weird, albeit a pleasant surprise, to see a big company respond and reach out to users in 2013. :)

Thanks. Got a bit recursive there.

I wrote a thing about how your favourites are public and searchable with not opt-out on HN: https://news.ycombinator.com/item?id=5756487.

Other than that, Flickr is one of the most privacy-conscientious services I know—which is why it took me by surprise that there weren’t controls for my favourites.

Flickr’s (general) emphasis on privacy and ownership rights are their main features to me. Maybe those are just hold-overs from the early days when monetizing your users’ data weren’t in vogue, though.

I just thought of a way to check: archive.org.

It does indeed show that favourites were available from the user page: http://web.archive.org/web/20130501115607/http://www.flickr.....

As a result, I removed the paragraph from the OP. This is what it read, to anyone visiting just now:

    In addition, your favourites are now a single click 
    away for users in the redesign of your user profile. 
    It’s entirely possible this was the case before, though.

Links/footnotes:

[^1]: http://www.forbes.com/sites/kashmirhill/2011/10/13/how-flick...

[^2]: http://www.flickr.com/search/?w=faves&q=sex+or+boobs+or+...

[^3]: http://idgettr.com/

[^4]:

    http://www.flickr.com/search/?w=faves-[[ ID ]]&q=sex+or+boobs+or+butt+or+porn

Indeed; it’s been around for ages in Opera, and all you have to do to use it is press Space at the end of a page to go to the next one. I think they planned to use the attributes to support native swipe gestures on touch devices, but that never took off, unfortunately.

You can try it on my blog at http://pygm.us/vwR2WSYJ or a thread in NeoGAF: http://www.neogaf.com/forum/showthread.php?t=559996.

Something Awful used to support it, but they broke it by making the Last Page button the designated `next` destination, unfortunately.

It’s really the only way to go through pagination-heavy content. Anything else is way too tedious.

Everyone with a blog should implement this. It’s just silly not to.