alyrik

13 ms·

1.
by alyrik 3y ago
I'm mainly excited that you can just deploy a generic tool like Bacalhau across your cluster and have it as a platform to manage your logs and a whole bunch of other workload/management stuff, rather than needing to install a mill
2.
Another TLS security thing I'd never heard of and should have been doing forever(sslmate.com)
1 points by alyrik 3y ago|0 comments
3.
by alyrik 6y ago
> The author is worried about the overhead of the three-way handshake, but the overhead of setting up TLS is far worse. Oh, "TLS sucks" is a whole separate blog post for another day ;-)
4.
TCP Sucks(snell-pym.org.uk)
51 points by alyrik 6y ago|59 comments
5.
Don’t fund your online business with ads (It’ll only make everyone hate you)(snell-pym.org.uk)
2 points by alyrik 8y ago|0 comments
6.
How dotmesh lets you manage change using branches(dotmesh.com)
1 points by alyrik 9y ago|0 comments
7.
by alyrik 9y ago
Performance: A bit meh at bulk bytes-per-second snapshotting, particularly when the vault is accessed over ssh, as it's latency sensitive (send block, wait for response, get next block, send, wait for response, repeat - rather than str
8.
by alyrik 9y ago
I aint'n't dead :-D Largely, Ugarit is ticking along nicely in my production setup, doing backups of my servers; when I get time I work on (a) performance, which is still weak in some cases and (b) archive mode, which is a fun spa
9.
by alyrik 14y ago
Oh dear... I once logged into the postgresql database of a very busy hosted service in order to manually reset a user's password. So I started to write the query: UPDATE principals SET password=' Then I went and did all the stuff required t
10.
by alyrik 15y ago
A cheap NAS made from a Raspberry Pi model B (the Ethernet one) and an off-the-shelf USB external HDD.
11.
by alyrik 15y ago
That's a good point - version control and build/release process management are all too often reinvented from scratch after initial painful experiences in the field!
12.
by alyrik 15y ago
Check out what RainStor does to compress relational data by a factor of 20-40 or so (that's 95%-97.5%): http://www.youtube.com/watch?v=rIsVcaMaAgg&feature=playe...
13.
A handy tool for sharing resources in a team(snell-pym.org.uk)
2 points by alyrik 15y ago|0 comments
14.
Compression tames Big Data on Hadoop(rainstor.com)
1 points by alyrik 15y ago|0 comments
15.
by alyrik 15y ago
It's a general question, but the linked article explores it from a few angles of different kinds of career :-) It agrees with your points - a split into applied and theoretical would probably be a good thing. The programmers I work with in
16.
What is the value of a Computer Science degree?(snell-pym.org.uk)
5 points by alyrik 15y ago|7 comments
17.
The upcoming revolution in cloud storage(snell-pym.org.uk)
1 points by alyrik 15y ago|0 comments
18.
Lords of a New Economy: Who is really in charge of Bitcoin?(snell-pym.org.uk)
2 points by alyrik 15y ago|0 comments
19.
Bitcoin does not pose a threat to law and order(snell-pym.org.uk)
54 points by alyrik 15y ago|18 comments
20.
by alyrik 15y ago
SOCKS gets you end to end (though it's arguably not "real"!) by letting you have listening sockets (which NAT doesn't). There is indeed a scaling issue with NAT/SOCKS as both need connection state on the gateway device - but, I suspect, the
21.
by alyrik 15y ago
Yeah, I'd like easier peer-to-peer communications, too. Which is why I suggested setting up SOCKS as a competitor to NAT, as it lets the client ask the gateway device for an external IP/PORT to do peer-to-peer communications over... without
22.
by alyrik 15y ago
I've run IPv6, to try it out... I just didn't bother setting it up again next time I replaced things, as it gained me nothing, so I didn't want to repeat the effort. So it's in my best interests to wait until I have to. Which means I'll con
23.
by alyrik 15y ago
I've seen the "IPv4 will get more and more expensive, and more and more sites will provide IPv6 connectivity, and (for some unspecified reason) clients will put out the effort to get IPv6 connectivity for no near-term benefit, and then when
24.
by alyrik 15y ago
Of course, what I'm proposing here - fixing the problems with NAT as a way of making IPv4 address exhaustion not be a problem for clients - doesn't help with IPv4 exhaustion for servers. What would I propose for that? * Using them more ef
25.
by alyrik 15y ago
I agree... the problem is, how are we to get a single global namespace? I have serious concerns with IPv6's practicality, even with 6in4 et al. Is trying to implement it just flogging a dead horse? If somebody comes up with a way to actuall
26.
by alyrik 15y ago
Interesting point, that... Addresses being scarce and valuable would play into the hands of large ISPs who already have a lot of addresses! Discuss! :-)
27.
by alyrik 15y ago
Yeah, but what benefit is there as opposed to just sticking with NATv4 or SOCKS? The real issue here is running out of IPv4s. We don't really need more IPs for clients - NAT fixes that problem (I just argue that SOCKS could be a better solu
28.
by alyrik 15y ago
Adding SOCKS to NAT boxes and to client devices is easier than IPv6, I warrant; SOCKS is a dead simple protocol, and the client can be slid into the sockets library without the app having to care. And that's it. There's no need for ISPs to
29.
IPv6 versus NAT (and a proposal to bring back SOCKS)(snell-pym.org.uk)
23 points by alyrik 15y ago|22 comments