netik

Ah, the old "think of the children" method to get censorship bills passed. Works every time.

Unconstitutional from day one, if it remotely passes, will be a short ACLU fight.

There is so much wrong with this article I don’t know where to start.

Apollo’s GraphQL with built in pub sub and JSON over websockets solves most of the issues brought up here with little work.

Somewhat true, but the splitting of pixels / bayer filter work is something that gets corrected later in either post/RAW processing or otherwise.

When we apply that work to screens, our eyes can't really post-process and correct for these errors.

I guess we need to keep in mind that index of is going to report file creation date, and it's hard to know when the file actually entered the web vs. "Was created, someone left it on disk, and then started a web server."

I still have emails in my homedir from 1990. Ugh.

Alembic | https://getalembic.com | San Francisco (SF Bay Area) | Eventually Onsite, remote right now.

Is looking for Sr Software Engineers with solid experience with large datasets and security (NodeJS/GraphQL/Apollo)

Technologies include Social Media APIs, Druid, Postgres, AWS, Vault, and much more.

Our leadership team of industry veterans has been around the block with tech giants (Google, Twitter, LinkedIn, WPEngine, Cambium Networks). We are backed by seasoned investors including Village Global – of which Bill Gates, Mark Zuckerberg, and Reid Hoffman are LPs.

Jobs: https://getalembic.com/careers/

Apply here: https://twothink-inc.breezy.hr/p/79be86f531db

or email your info to john(at)alembicteam(dot)com

Aside from pissing all over WeWork, which given their immense losses they probably deserve, This article could have been summed up in a couple of short sentences.

There's a lot of words and effort going on here to make Kafka sound immensely complex (and dare I say Kafka-esque?)

The article continually chides Kafka as overweight, hard to setup, complex, blah blah blah. None of these things are true in modern day deployments.

Three instances of Kafka, Two ZK instances, and you're off and running. All of that will run in docker and the docker images will stand themselves up if you let them. You need even less for developemnt.

Postgres is a bit more complex given that you've got to manage machine sizes and database schemas.

But even with that being said, the article gets one thing right. For average data use, most any system will do and some startups are over-engineering their stacks.

I think my main problem with this is the intermixing of higher "application" level features like surveys and forms with lower level protocol features like "message transport."

This seems like a bad idea and goes against years and years of open systems design.

If you actually have the time and you go to the royal museum at Greenwich you can see that all of Harrison‘s clocks are still functional. It’s one of the most beautiful things I’ve ever seen as an engineer

It’s hard to say Facebook’s targeting is completely garbage while at the same time understanding that Cambridge analytica, Trump, and others were able to use their micro targeting to sway elections.

Obviously the targeting works. But,like most software, I’m sure it is buggy. Probably both sides of this are true.

The keyword in these charges is "information asymmetry." That's exactly what is going on here. Yet another crypto scam to benefit it's founders.

Timestream hasn't even really been generally released as best I can tell. We wanted to use it, went to TimescaleDB, and then ended up going to Druid to improve performance.

Seriously, If you need to do this at scale, use Druid. It's much more efficient for time-series data.

It looks terrible and lacks any sort of decent UI/UX, and this will kill adoption.

Of course, it's funny to see this on the same day as https://opensourcedesign.net/ reaches the front of hacker news. Maybe they should get together.

why shit on this? it’s great software and works well

resolve is the best and I am so happy with Blackmagic as a company. They really leveled the playing field for small video producers like me

It's 2020, I feel like this is some sort of fresh hell that I managed to somehow miss.

Isn't this the same multi-terabyte leak from 2017?

https://fortune.com/2017/06/19/deep-root-analytics-voter-dat...

Or is this another one?

I suppose in a way they are monetizing/selling the use of your data because they're collecting it and selling the aggregation of that data back to advertisers.

Sure, it's not a selling of the raw data record but with advertising and targeting an advertiser can get pretty close.

webcam control panel. it’s meant to adjust and control logitech cameras but it resets the camera back to defaults (no gain, no exposure) every time a piece of software restarts the driver.

it’s wretched and ruins every zoom call.

see, this is where things like apollo client shine.

one part of the page makes a request and the rest of the page gets to use the data because now it’s in the local object cache.

I get what this article is saying but there is a lot more to graphQL than reducing network RT. It’s about replacing statically defined REST API responses.

As a prior commenter wrote, it’s making the backend more flexible when the front end devs change their mind.

The moment the device connects to Unifi, without your permission, they have your IP.

Then again, they had it when you downloaded the update, and when your devices check for auto update, so, you’re not getting away from this data collection with an opt out button.

The important thing here is that this fixes the cold cache problem. for good.

i love memcached a lot, it took too long to get here and this wasn’t the primary use case of memcache

You’re giving zero context here aside from “there was a whiteboard and it was horrible.”

What happened?

Age has nothing to do with it - if you can’t communicate.

You’re giving zero details here aside from “i failed the whiteboard interview and it was horrible”

What happened?

Maybe it’s you.

This is basically what GDPR is designed to stop.

Sadly they followed the path of nearly every surveillance capitalism startup out there.

1. Breach user trust by acting without user consent. 2. Market it as a service. 3. Eventually get caught. 4. Offer an apology.

Rinse, Repeat.

I don't have any real complaints about the steps they took to correct this. I have complaints about the fact that they did it in the first place and didn't consider the users. I also take offense at their investors who continued to invest while knowing this was going on.

Article reads like an overview of 2008 technologies, but offers no actual, new solution to the existing solution that fuels Twitter and other social media sites.

Twitter initially ran everything in the cloud. I should know, I was employee 13. It was much cheaper to build our own server hardware and move to our own server and network agreements. Peering and transit is cheaper at scale, as is commodity hardware.

All of this discussion about the company here (which isn’t responding in a correct and honest way) and not much discussion on the root cause of this problem.

The journalist and the 40+ People were victims of a credential stuffing attack which means they used the same password on multiple sites.

Had they used a password manager to roll a new password per site and had deliveroo had proper rate limiting, this attack would have been mostly mitigated.

There’s not much excuse for this behavior.