adambrenecki

> in connection with our provision of the Service.

This is pretty much boilerplate legalese that's generally intended to mean "you can't upload a file to your public folder, then sue us for copyright infringement because that file is in a public folder".

Lawyers seem like to cover their clients' asses as much as possible, but for a service like this that's designed for privacy-conscious people it'd do them well to step back and think about how the license comes across to privacy-conscious laypeople.

From what I've seen of Keybase, from back when they were just an alternative to the PGP Web of Trust to now, I don't think they're genuinely planning anything nefarious (but they'd still do well to have a ToS that reflects that).

There's a bunch of other tools[1][2] that do this sort of thing already, although all the ones I've seen display file size as a sort of flame graph/pie chart hybrid (imagine a flame graph wrapped around a circle).

This flat representation is probably better because it doesn't exaggerate the size of deeply nested files, but I find the example in the article a bit harder to read.

[1]: https://daisydiskapp.com/ [2]: http://www.jgoodies.com/freeware/jdiskreport/

This is a neat idea; it's sort of an entity-relationship diagram or class diagram for API resources.

In fact, if your audience is familiar with these sorts of diagrams, I wonder if it'd be more readily scannable if you denoted the cardinality of the relationships with the sort of notation you'd see in ERDs or CDs? (Personally, I'm a big fan of Crow's Foot.)

By the sounds of it, you'd use this as an overview and use something like Swagger for the actual details of each endpoint.

(For that matter, if you output the diagram in a format that supports hyperlinks like SVG or PDF, you could link from the diagram directly into Swagger.)

I kind of wish there was a ALGPL; a license that works like the AGPL in terms of access over a network being considered use, but could be used unmodified as a library in non-GPL-compatible software like LGPL libraries can.

Sadly, I doubt the FSF will ever write such a license, given how they discourage use of even the LGPL unless absolutely necessary.

> red tape

...

> Such technology is illegal because jammers are likely to affect wider areas and other frequencies than those they are intended for. They can also result in the disruption of emergency and rescue radio services in the public area.

Oh fuck off. This isn't red tape, this is the law doing exactly what it's supposed to: protecting public safety and people's access to an essential service.

I'd love to see this principal bleating about "red tape" to the coroner after one of her students is hit by a car out the front of the school, and dies because nobody can call an ambulance.

(Well, no, I'm glad that this nonsense is being nipped in the bud before something awful like that happens, but that's exactly the scenario this idiot is setting herself up for.)

Existing certs (those with a notBefore date before Oct 21 [0]) are still trusted by Firefox. New certificates are not.

(WoSign could theoretically backdate the notBefore date on new certs to make them look like existing certs, but Mozilla have said that if they catch WoSign doing this they'll distrust their root totally.)

Other browsers are taking similar measures, but I'm not sure on the details.

[0]: https://blog.mozilla.org/security/2016/10/24/distrusting-new...

The closest the industry came to what you're describing, unfortunately, was Pebble. They were cheap (IIRC the OG Pebble was around $99); while they didn't last _multiple_ weeks you could get 7-10 days out of a charge depending on model.

I use my Pebble Time Steel pretty much exactly how you're describing; to glance at the time, weather, and notifications, so I can keep my phone on silent in my pocket.

Apparently nobody except you and I want that, though :(

This is really sad; Pebble had probably the best products on the smartwatch market, and I'll be disappointed to see them go.

They were the only smartwatch manufacturer that could claim anything close to 10 days of battery life. They were the only smartwatch manufacturer that made devices that were water resistant and really meant it. (That is, they're all rated to 3-5 ATM and tested the same way regular watches are, you can actually use them in chlorinated or salt water, and they didn't try to claim that your "water resistant" device's warranty was void if you got it wet.) They were the only smartwatch manufacturer that made devices that had an always-on display that's actually any good (with the possible exception of the just-released Gear S3; I've yet to see one in person but it sounds like Samsung are getting there). It's a small thing, but they were also the only smartwatch manufacturer that didn't take themselves too seriously, filling their UI with cute icons and animations that made the watch fun to use. All that, and their products were significantly more affordable than some of their competition.

Oh God, that sounds an awful lot like two more Australian systems: the Queensland Health payroll debacle, where a bunch of health workers were paid incorrectly or not at all. Or the National Disability Insurance Scheme debacle, where healthcare providers haven't been paid, resulting in small business owners having to take out huge amounts of personal debt just to pay their employees, and sole traders unable to provide services their clients need to live day to day while still keeping a roof over their own heads. (They're both IBM projects too.)

I have text editor commitment issues; I change editors somewhere between bi-weekly and bi-monthly. Some of the reasons why I switch to and fro:

- Visual Studio Code—pull factors: Better performance than Atom. Solid language support for Python, and excellent for JS and TypeScript, and the Language Server Protocol means that the UI is identical no matter which language you use. Looks good. Push factors: Not as customisable as other editors, especially visually. Startup time still leaves me wanting.

- Atom—pull factors: Infinitely customisable; basically the Emacs of the 21st century. Looks good. Push factors: Git integration is nowhere near as good as VSC (ironic considering its authors), and I've yet to find a Git plugin I really like. While it's not unusable, the performance isn't the best.

- Sublime Text—pull factors: Performance. The ST dock icon often doesn't even get to finish its first bounce animation before it's ready to go, and it can handle large files amazingly. Push factors: Stagnation, both in the editor and the plugin ecosystem, compared to Atom and VSC. (It seems like this has been improving a bit lately.)

- Chocolat—pull factors: Really beautiful, native Cocoa UI. Buffer list in the sidebar instead of tabs and command-click for split windows is really neat, and I wish more editors worked this way. (VSC and ST can both be configured to get half-way there, but they both conceptually differ with Chocolat on how splits work, and I prefer Chocolat's approach.) Push factors: Less extensible, and worse plugin ecosystem, than anything else on this list. (You can't even provide a third-party autocompletion engine.) Not cross-platform, so I can't use it on my Linux box at work. Configuration is through a GUI only, so difficult to keep under source control and sync across machines. No complete-as-you-type. Hasn't had a release since June. Actual text editor widget seems kinda janky sometimes.

- Vim—pull factors: Modal editing. (All of the others have Vim-emulation plugins or a Vim mode, but they have varying levels of usefulness. Chocolat's can't even easily do key remappings last I checked.) Rich plugin ecosystem. Push factors: Vimscript somehow manages to be the only language more puzzling and hideous than Bourne/Bash shell scripts, although to its merit it doesn't have a keyword called 'esac'. GUI mode is essentially an in-process terminal emulator.

There's a few more I'd like to try, like Brackets, Coda (I love the idea of having terminal emulator tabs in your text editor! I'm not sure if I like how web-focused it is though), and CodeRunner; and a few more I've tried before but not stuck with for any length of time, like TextMate and BBEdit. I also used PyCharm at work for about six months, but stopped when the VSC Python extension started getting good and haven't gone back since. But those are the ones that I've actually used in earnest for a decent length of time and still regularly switch between.

> Can the conclusion stand if the arguments are not correct?

It can; arguing it can't would be an 'argument from fallacy', itself a fallacy.

Put another way, I can make up a totally absurd, incorrect argument that the sky is blue, but the sky is still blue. I can also make up a totally absurd, incorrect argument that the sky is green, but it isn't. An argument that doesn't hold water doesn't say anything useful about the conclusion either way.

Sites like Mint do this to retrieve your banking history. Asking for banking login details seems to be the standard way of doing that sort of thing. (Don't get me wrong, it's still terrible, but it's not like the banks provide an API you can log in to with oAuth or something.)

This is different; mwave is a retailer, all they're doing is receiving a payment.

> The state would then penalize those schools by cutting triple the amount of money wasted from the 2017 budget.

Budget cuts to public high schools—money that's used to pay for the staff and resources needed to actually teach kids, by schools which often don't have much budget to go around in the first place—as a form of punishment, because lawmakers disagree with administrators' decisions. And somehow the _students_ are the childish ones?

The problem with mail-in voting is voter influence. When you vote at a polling place, you're guaranteed to be able to vote in a booth on your own, without other people or party advertising to influence you. With mail-in voting there's no way to stop voters' controlling spouse and/or cult leader from influencing their vote or even voting for them.

I think the Chrome behaviour (display invisible content for a while, then after a timeout render using fallback fonts) would be a happy compromise were the timeout not three whole seconds.

font-display: optional and font-display: fallback (as linked in the article) look like promising solutions to the problem (both recommend a FOIC aka 'block period' of 100ms), but it'd be even nicer to set the exact duration of the block and swap periods in CSS.

Cannot reccomend GitUp (http://gitup.co/) enough. It's open source too.

That said, I use it differently to you; I use a graphical Git client mostly to view and browse around the commit graph, and I generally make commits and stuff like that from the CLI. I think it's pretty simple to do commits through GitUp as well.

Perhaps, but when it comes to PHP's niche—websites—it's easier to _get started_ than basically any other language.

Got a simple Hello World PHP site? Open your SFTP client, drag and drop, done.

Got a Hello World Python app? You have to know about WSGI adapters, process monitors, usually some sort of reverse proxying, how you're going to handle your static files, and so on.

Oh, and let's not forget that to even get to that point, you needed to use a framework of some kind, which meant wrestling with Pip and virtualenvs; you can't just 'echo "Hello World"'.

I'm picking on Python here because web dev in Python is my day job, but the story is similar for many other languages.

I think it had more to do with GitHub than anything else. In GitHub's early days, they put a lot of effort into marketing Git (e.g. the now defunct "Git Is Better Than X" website), because they needed people to use it in order to use GitHub.

It's reserved for multicast DNS, which is what Bonjour uses.

Apparently the A10 chip has two high-perf cores and two low-power cores, sort of like what ARM call "big.LITTLE". So yes, sort of.

Experimental, yes; You can download nightlies of Servo at https://servo.org/, which use Servo together with browser.html, a HTML+CSS+JS-based browser chrome developed for the purpose of showing off Servo.

Why not have the dataset name as a fragment in the URL? For instance:

    http://demo.noms.io/cli-tour#sf-fire-inspections/raw

Glancing over RFC3986 [1], fragment identifiers seem to be pretty much made for what you're trying to communicate with :: - separating a subresource (the dataset) from a primary resource (the database). Unless I'm misunderstanding something?

[1]: https://tools.ietf.org/html/rfc3986#section-3.5

Englebart's chorded keyboard entered a single character for each chord. Most chorded keyboard systems type multiple characters or entire words in a single chord, which is how you get people doing 3-digit WPMs, and how court reporters and captioners on Stenotypes can keep up with speaking.

Of course, if you wanted to do programming on a chorded keyboard the chords you need are totally different, but apparently it's still very doable: http://plover.stenoknight.com/2010/04/writing-and-coding-wit...

So, does this make (for example) visiting a website over HTTPS illegal? Or does it compel Hungarian ISPs to MITM their customers? It seems to imply one in one sentence, then the other in the next.

> Also, the new "gluten-free" diet fad scares me,

As a coeliac also, I freaking love the fad. Back when I was first diagnosed around 2004, it was nearly impossible to find GF bread mix. Now, I can buy 6 different brands of ready-made GF bread within a few km of my house - 7 once they finish building the Aldi down the road - and the larger supermarkets even have an entire aisle of gluten free stuff.

People that choose Python _chose_ a language that doesn't have static typing.

People that want to write code that runs in a Web browser are locked in to Javascript, so they're "locked in" to JS; I can't think of a platform where the only option is to use Python.

I've switched from PyCharm (based on the same IntelliJ Platform as IDEA) to VS Code, and it's so much faster to work with. That said, I've found that it's not nearly as good at all the code intelligence stuff as PyCharm is.

I've never used IntelliJ's Go tools, but VS Code is much better at that stuff in Go than Python. (I believe it uses third-party open-source tools in both cases; code intelligence for a statically typed language like Go is probably much simpler which probably helps.)

The best way to look at VS Code is as an IDE minus the 'integrated' bit - instead of having the core editor and UI bundled in with all the code intelligence stuff for a specific set of languages, it's a text editor with a code intelligence and debugger UI, that calls out to out-of-process plugins to do the heavy lifting.

You can use the new AWS Certificate Manager[0] with CloudFront[1], which you can attach to your S3 bucket. The docs aren't brilliant, though.

[0]: https://aws.amazon.com/blogs/aws/new-aws-certificate-manager... [1]: http://docs.aws.amazon.com/acm/latest/userguide/gs.html

In theory, `pex` can do exactly this. (In practice, I had a brief play with it and couldn't get it to work, YMMV.)