pjjw

bless, but hearing people say this version is "better" makes me want to walk into the sea.

this is pretty devastating for signal

this comment section is one of the worst cesspits of oldbrain i have seen on this hell site.

ignore trolls who insist on using tautologies to bend language to superficially make a point.

i can't help but very lol @ kubernetes as the successor to borg :0

craig got a whole new york office. he did well.

favorite thing about it is their use of the pragmatapro font on the website

Dollars to donuts these guys got hacked. Still pretty shitty the appeal process was busted.

i think it's funny seeing analyses of twitter that act like the problem is that the product needs tuning. the problem is they need to make money, and as-is there's basically not much good reason to pay them for advertising over facebook, who offer much better targeting.

Any reason the python support was ripped out? I've got my suspicions about not wanting/not being able to properly release the python packaging method in use internally, but I'm curious if I'd be tilting at windmills to try and get it to output pexes.

Yep, and that bit of JS you are distributing _is_ a decoder. I've been bitten by this before, and it resulted in buying the MPEG-LA a few ferraris a month after they noticed and we were popular while we worked to create an alternate solution.

Good times.

additional close system: https://github.com/jschauma/jass

this solves the large team problem, too- it fetches membership data and ssh pubkeys from ldap. great if you have it, but only exists in large organizations.

this of course doesn't do the gitwork for you, but it does avoid creation of another set of keys to be mismanaged.

did you contact your account rep or go through support? if the former, that makes sense. ours is traveling..

amazon's response on this has been absolutely disgusting. we pay for their enterprise support, and that team is completely unaware. last night they advised that if i wanted this fixed in a day i should consider terminating my own ssl. i set that up, and as soon as i was about to cut over, i noticed that our elbs were fixed.

as of now, support is unaware there is a fix being rolled out.

i would have been better served not speaking to them, let alone paying for aws support.

many do by employing the openssh maintainers to do that. it's the best way to contribute to openssh without contributing to theo.

there is. it's search by username. unless you're talking about android, where the answer is "real soon now!"

you really think he's still alive? the whole thing smelled so strongly of suicide, especially given the quantity and character of his output. many creatives go this way.

there are quite a number of them, especially in academia. the support contracts are ludicrously expensive in some departments i work with.