konklone

14 ms·

91.
by konklone 12y ago
That's actually the Google Analytics Reporting API's formal syntax: https://developers.google.com/analytics/devguides/reporting/... It's pretty handy, since queries are so commonly exactly that
92.
by konklone 12y ago
Should be fixed momentarily, if it's not already. Thanks for pointing that out!
93.
by konklone 12y ago
Just speaking for myself here, but what makes sense in terms of legacy client support for e.g. taxes or health care may be different than what you need for a set of technical resources.
94.
by konklone 12y ago
That's an interesting point. I'll be straight, it's lifted right from https://istlsfastyet.com . And cio.gov is in the HSTS preload list [1] so (once the list makes it into stable channels) the chances of the domai
95.
by konklone 12y ago
Convergence and DNSChain are two interesting proposals to replace the CA system. IMO, it's more important to emphasize the idea of secure origins, and HTTPS hits that note. TLS could be swapped out, the CA system could be changed, but
96.
by konklone 12y ago
It's worth noting that HTTP(S) has broadened outside of the web, in the sense of web browsers. Most native mobile apps, and lots of APIs used by desktop apps, etc., all use HTTP to get their job done. Definitely doesn't cover ever
97.
For Public Comment: The HTTPS-Only Standard(18f.gsa.gov)
8 points by konklone 12y ago|0 comments
98.
The HTTPS-Only Standard(https.cio.gov)
189 points by konklone 12y ago|94 comments
99.
FTC.gov is now HTTPS by default(ftc.gov)
6 points by konklone 12y ago|0 comments
100.
by konklone 12y ago
Boo on all who downvoted this bit of snark.
101.
Signal 2.0: Private messaging comes to the iPhone(whispersystems.me)
2 points by konklone 12y ago|0 comments
102.
by konklone 12y ago
There's not a master plan, but there's several promising lines of work happening. Hopefully 2015 will be a fun year. Tomorrow, I'll be on Federal News Radio in the morning, preaching the gospel to DC commuters.
103.
by konklone 12y ago
The preload page says Safari uses Chrome's list too: https://hstspreload.appspot.com/
104.
by konklone 12y ago
This is fantastic news! And they decided to include the Chromium HSTS Preload list too. I've submitted something like ~30 domains to the list, and having them covered in newer versions of IE automatically is a very nice thing.
105.
The first .gov domains hardcoded into your browser as all-HTTPS(18f.gsa.gov)
4 points by konklone 12y ago|0 comments
106.
by konklone 12y ago
I tell this story all the time to people. It's so magically great, and the developers are a national treasure. I think of 18F and USDS in part as pieces of an effort to make this kind of result less of an anomaly, and the kind of thing
107.
by konklone 12y ago
You'd be surprised how much of a difference a single person, engineer or not, can make on the inside, with enough persistence and vision. If you care about policy, you put in the time, and you know what you're talking about -- you
108.
by konklone 12y ago
https://www.federalregister.gov is a favorite of mine in the federal government, and an inspiration (they launched with a full JSON REST API in 2010!) -- but just so it's clear, that's not an 18F project. The code fo
109.
Open data needs HTTPS too(konklone.com)
1 points by konklone 12y ago|0 comments
110.
by konklone 12y ago
It's a product of 18F (of which I'm an employee). The US Digital Service folks are awesome, but a totally separate unit. 18F is in an independent administrative agency, the GSA, the Digital Service is in the White House.
111.
ISIS hacked CENTCOM(twitter.com)
10 points by konklone 12y ago|2 comments
112.
Installing Debian 8 on a Dell XPS(github.com)
2 points by konklone 12y ago|0 comments
113.
by konklone 12y ago
For some extra clarification: this is the official list, as released by the General Services Administration, the part of the government that runs the registry. Some of these -- the domains for the federal government's executive branch
114.
A Complete List of .Gov Domains(18f.gsa.gov)
84 points by konklone 12y ago|16 comments
115.
Slack is now forcing users into arbitration(konklone.com)
124 points by konklone 12y ago|2 comments
116.
by konklone 12y ago
Yes. Not just inside government, either.
117.
by konklone 12y ago
Er, so I take this back? Ilya Grigorik rang in and told me I wasn't distinguishing between request and response headers: https://github.com/18F/tls-standards/issues/24
118.
by konklone 12y ago
Sadly, we still do. Requiring SNI remains a tough sell. That's one of the biggest limiters in our HTTPS setup on saving costs and being better stewards of IPv4 space.
119.
by konklone 12y ago
> By demonstrating by example and by explanation of what's already possible in current rules, 18F can boost the stock of the buried geeks hiding out in many of our government agencies. You nailed it.
120.
by konklone 12y ago
> You claim the second most important reason for using HTTPS is my privacy, yet you share all pages I visit with Google analytics. I think that's a totally fair point. Our use of Google Analytics isn't changing any time soon, b

More ›