plange

Donated by Joe Beda himself.

Gitlab states it wants to go public this year

https://about.gitlab.com/handbook/being-a-public-company/

men. people

Otherwise i agree. Having just spent a week on-site at a client, you just notice a lot more problems (or start to understand the details of previously identified problems) that are in your capacity to fix.

They are starting in a garage https://blog.jessfraz.com/post/born-in-a-garage/

Read up before you make unfounded claims

Already happened. OpenNIC had to move the users from .free over to .libre

http://www.salimvirani.com/facebook/

https://www.cnbc.com/2019/08/23/facebook-releases-new-cambri...

http://www.theguardian.com/technology/2014/jul/06/we-shouldn...

I agree with everything you said, but this movement has been going on for a long time but and has been very bad at... hisss.. marketing.

These are complex topics and people don't want to put in the effort to understand them so this needs some top-shelf selling power. And there's no money to be made. Just freedom (as in speech).

From the commit message:

0.0.0.0/32 is still prohibited, of course.

How is this different than ticketswap?

This is NIH syndrome. You're way better off following the standards, and likely implementing standard libraries to actually make use of them.

You can do both.

Worked at a startup that unfortunately went under, trying to reuse heat generated in datacenters. (saves on electricity spend on airco and saves on having to generate heat elsewhere)

Luckily some competitors still exist: https://www.cloudandheat.com/ https://www.qarnot.com/fr/home-fr/

ecosia.org

Journalists do that all the time, it's literally part of the job. Though it is rare to see because there are repercussions.

you should probably upgrade that kernel

Confusion prevention squad:

That is to get to 3.3.3.3 A 3.3.0.0/16 route takes precedence over a 3.0.0.0/32 route.

I think you mean:

That is to get to 3.3.3.3 A 3.3.0.0/16 route takes precedence over a 3.0.0.0/8 route.

a /32 is _more_ specific.

I had this exact same problem with the way i & my team approached our kubernetes clusters. I come from a network management background and in that space we all know of a tool called RANCID. A simple tool that logged into your switches/routers, made a dump & removed counters/oscillating data and stored it into CVS.

This predates infra-as-code.. it took years before someone wrote a clone that used Git instead of CVS

Made something stupidly similar for kubernetes: https://github.com/pieterlange/kube-backup

Thanks not only for making this, but also describing your process in a blog.

I use ngx_http_auth_request_module a lot and used haproxy a lot in the past but it's currently too limiting for my usecases - now i know it supports lua we're in a whole different ballgame.

They still haven't licensed their code, which makes it very hard to use.

There's some good resources out there, the problem here is that most people simply don't care or don't think it's part of their job to fix these things.

https://mozilla.github.io/server-side-tls/ssl-config-generat...

https://cipherli.st/

NAT is not security at all.

Classic mistake. Except it's not really a mistake, but a conscious decision by whoever was in charge at the time (with the main focus probably being growing the company and not hurting current customers).

How do we fix that though? Standards seem like the only solution but they either don't move fast enough or the early birds (in this case amazon, but another prime example is microsoft) become so entrenched they set the standard themselves.

My own answer up until now has been to work in linux and open standards jobs (now kubernetes) but this requires increasing amounts of effort.

Unstable over testing? Really? Why? :-)

I've been running stretch on a lenovo carbon x1 for the last 2 years and it's been one of the first problem-free experiences running linux on the desktop (linux user for.. 18 years). Really awesome. Thanks!

The easiest way to do that probably results in a callback to Big Daddy G every time I access anything sensitive and I'm cool with that.

Why?!

I'd wager we haven't seen the last bug yet, if ever.

You are completely right up to the point that people are able to update their phones.

Nothing in life is free.

Quality software doesn't create itself out of thin air (yet, if ever). That means someone has to make an investment.

You don't have to invest in the upkeep of the foundation of your house, but if some bugs, say termites, were to sneak in you can't blame the original builders for the donated foundation.

Please downvote for the bad analogy.

Yes, possibly.

Sorry, i wasn't trying to imply they shifted blame. But atlassian does bare the legal&moral burden of securing their product here.

Then you would be fine with the standard boilerplate "your data is secure with us"?

I'm happy they say this.. now i'd like some sort of proof :-)