kosinus

14 ms·

91.
by kosinus 9y ago
One of the ongoing narratives here on HN and elsewhere is that there's ‘a new JavaScript framework every other week’, as if that's a bad thing. A bit further down the thread, Sebastian says: > Revel in fragmentation and duplica
92.
by kosinus 9y ago
https://wiki.debian.org/ReproducibleBuilds
93.
by kosinus 9y ago
My experience with Ansible is that I have to write a dozen lines of yaml just to ensure permissions on a bunch of files. (But Puppet and Chef scare me even more.) The tools in this space feel like very thick abstractions on top of commands
94.
by kosinus 9y ago
This is a capturing API, I guess? Using webrtc-adapter, all of my webrtc code instantly worked. Though it doesn't seem to want to connect to firefox peers.
95.
by kosinus 9y ago
I also wonder if a weak link could pose a threat. Say, Attacker knows User is a member of Site X, but Site X fails to implement checks and/or rate limits properly. Attacker brute forces master password by spamming the login endpoints.
96.
by kosinus 9y ago
You're not alone: https://twitter.com/brianbondy/status/862368140369567744
97.
by kosinus 10y ago
Most of our builds are 'basically' Node.js / npm or PHP / composer, so reasonably contained build processes. It looks simple on the surface, but once you start running CI for a while you notice all the dependencies on th
98.
by kosinus 10y ago
I don't know. We tried looking for alternatives when we were a bit down in the gutter with our Jenkins setup, but were even more disappointed with the other options. Instead, we now use Jenkinsfiles everywhere, or pipeline scripts wher
99.
by kosinus 10y ago
I've never hit te rate limit on LE. Seems to me you need to be running a public site that gives each user a subdomain, or similar setup, before you run into such issues. You don't need a HTTP server to do authentication, it's
100.
by kosinus 10y ago
That was 1.15, I believe. :-)
101.
by kosinus 10y ago
Pretty much, yes. I think that assumption turned bad a really long time ago? Interruptible sounds like a very strong requirement. Just being able to wait for the result sanely is enough, I think. A process may then decide to lose interest h
102.
by kosinus 10y ago
There's Servo: https://servo.org/
103.
by kosinus 10y ago
I actually like these release notes? The commits are an extra, and messages are always clearly worded, in my humble opinion. I guess the commit list is the first thing that pops out when skimming, but it's less important than the notab
104.
by kosinus 10y ago
One thing that bothers me is the 'relational databases are good enough' statement, that is repeated in other contexts as well. But especially here, where we're talking about reducing complexity, it feels off to me. PostgreSQL
105.
by kosinus 10y ago
This'd be awesome, and there are very few providers which offer this. When looking into this, I could only find HE and BuddyNS. Everyone seems to be inventing their own custom API for this, which I guess is the 'modern developer f
106.
by kosinus 10y ago
SCTP may see more usage in the wild because of WebRTC.
107.
by kosinus 10y ago
Works fine on Firefox and Chrome, on all systems except iOS. (On iOS, all browsers are Webkit shills.) Safari currently lacks support everywhere. http://caniuse.com/#feat=rtcpeerconnection
108.
by kosinus 10y ago
Or rebase. Don't hide merge fixes in merge commits, keep your changes relevant when read in context of current master. Unless you're working on a topic branch together with another dev, but I find that rarely happens in practice.
109.
by kosinus 10y ago
I'm not sure what codec those products use, but I wouldn't be surprised if Slack went for Opus. Seems like it's the most popular choice these days, with little competition. (Discord also uses Opus.)
110.
by kosinus 10y ago
Rabobank in NED uses QR-like square codes with color. While it generally works well, it breaks down when you try to scan from a screen running f.lux or night shift.
111.
by kosinus 10y ago
Pretty much! 1 and 2 are typically a form on the site using Portier (relying party). There's also less emphasis on branding; as a user you will rarely see Portier mentioned.
112.
by kosinus 10y ago
That's a really good question, because there's no plan yet. In fact, Portier currently doesn't allow more than 15 minutes for verification. Lots of services already depend on email verification during signup or password recov
113.
by kosinus 10y ago
Here is the relevant ticket: https://jira.mariadb.org/browse/MDEV-10465
114.
by kosinus 11y ago
Absolutely true for regular passwords. In the specific case of the blog post, it can work however, because it's just the numeric two-factor part.
115.
by kosinus 12y ago
Not even that is enough. My train of thought was: "This is the Java thing, right?" But I wasn't sure, and it's not mentioned anywhere in the opening paragraph of that page either. Java is not mentioned until "The
116.
by kosinus 12y ago
I tend to declare vars with their context. Especially in functions that are (unfortunately) longer than usual, having all vars at the top makes for a mess. But I don't think the `let` syntax is going to be a problem for people who writ
117.
by kosinus 12y ago
If you're saying, a bug should always be investigated downstream before reporting it upstream, then I agree. If you're saying, there are scenarios where segfaults caused by upstream code are not upstream bugs, then I disagree.
118.
by kosinus 12y ago
For reference, `this` in Node.js is `exports` in whatever module you're in. It's only `global` in the REPL.
119.
by kosinus 12y ago
We built a similar JavaScript library to create and apply JSON patches: https://github.com/Two-Screen/symmetry The format is not formally specified in any way, but it looks like the biggest differences are that we 1) m
120.
by kosinus 12y ago
Or the server/client both implement custom compression on top of VNC.

More ›