Recent submissions

Comment · 10 years ago
Comment · 10 years ago
I'm waiting for the day this is just a library you pass an image to and it returns an array. No, not a SaaS. Then on my own pump.io, diaspora, redMatrix etc. it just works. My data, my images, my network. I'm not against the tech at all though. Neat
Comment · 10 years ago
I run a gitolite[0] instance on my server. It's great so long as you have another way to deal with issues and love the terminal. Access control is a breeze.

I feel like Gitlab is heavy. Gogs is neat, but incomplete. If you don't need/want bloat, gitolite works well.

[0] gitolite.com

Comment · 10 years ago
Comment · 10 years ago
I turned off the notifications. Didn't need to know every time a cookie blows up.
Comment · 10 years ago
Comment · 10 years ago
Firefox lets you do that natively too. Self destructing cookies deletes the cookies after you close the browser tab, not the entire window. If the browser doesn't provide complete isolation between tabs, this'll make it so the cookie isn't there to harvest from. You can set each site to tab/browser/never too.
Comment · 10 years ago
* Self destructing cookies

* Better privacy

* uBlock with EasyPrivacy list

* Https everywhere

Comment · 10 years ago
If this is true, it's unfortunate. Things like flux should have a small footprint and a small working domain. I'm willing to spare some complexity for usability tools, but always end up getting off the bus when it gets too heavy.
Comment · 10 years ago
I agree. It's helpful, but by no means novel or interesting beyond being a tool in the utility belt. It gets more attention than other tools far more interesting.
Comment · 10 years ago
Comment · 10 years ago
Oh you're right! We need EME'd web assembly so Facebook can hide everything behind a proprietary binary blob. THEN the user will really be free from themselves and their own stupidity. \s
Comment · 10 years ago
I think this whole thing is a bad idea. They won't allow a scary opt-out button because some software could turn it on, don't allow about:config because it could be flipped, don't allow a build flag in stable because malware could flip it and build. I mean... by that logic, couldn't someone reskin and redistribute alpha or the 'unbranded' with malware? Firefox is so afraid of malware, yet it encourages users to store their passwords in plain text in the browser?

It really feels like a landgrab and not anything anyone has been asking for. Firefox has to compete with the Chrome web store, but you can't burn your house down to save a room. What's left if Firefox becomes some centralized market akin to iOS, Windows Store, Play etc. Forced AMO signing flies in the face of the decentralized web. "Malware happened" and "Chrome does it" aren't really answers.

I think getting backed into a corner has made Moz take risks with their ideology. Hopefully they give developers and users a lot more time to deal with the upcoming changes.

Comment · 10 years ago
That's true, and you're right. Just a shot in the dark. Maybe someday one of the trendier email clients will support markdown rendering natively in their editors.
Comment · 10 years ago

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton