fjni

This is absurd. Would she be able to sue Block/CashApp? She should. For millions and millions of dollars.

That is a lesson meta engineers shouldn’t have to learn this way.

> I hope it is interesting or helpful

I think you're wrong. I think it's embarrassing. Though I might be wrong.

Bathhouse in New York wrote about this. Not sure they still do it to this day.

https://help.abathhouse.com/hc/en-us/articles/16748674443924...

The lack of genuine desire to understand each other is what is astonishing.

I don’t know where “the politician” went with that comment, but for me the more pressing conversation is whether we want a society where many are struggling and some make a billion dollars.

You benefited from society, clearly, which is not to say you didn’t work hard. But it seems entirely reasonable to me to ask you at that point to give back. We can knock plenty of people back to mere “hundred millionaire” status, they’ll be fine, and we can do a whole lot with that money.

I’d be genuinely curious about the data on this.

There are examples I can think of with a more traditional governance structure that did well: Apple, Amazon, Microsoft.

> Founded by alums of Tesla and the autonomous vehicle company Cruise, the San Francisco startup has received hundreds of millions in venture capital funding and is valued at $2 billion

Stop outsourcing the cost of your vision to the rest of society. Especially when it’s peanuts to you and meaningful to, in this case, the host of what they call an apartment and you seem to think is a test course.

Wait… railway runs on GCP? Didn’t they make a whole thing about not “building a cloud on top of another cloud?”

Or did they just mean that they’re not renting VPSs but only metal from the cloud provider?

In my mind I was so excited that there was another provider not just paying one of the hyperscalars but at a minimum colocating and owning more of their stack. https://blog.railway.com/p/heroku-walked-railway-run

Maybe it's because I'm idealistic in addition to being old, but I think a lot of this functionality was in fact added for explicit purposes.

A client sends the language header or the list of supported fonts not so that the server can "do whatever they want with this data." There is (or was) a real reason for it when we came up with these standards.

The fact that website providers, or more specifically ad-networks, have chosen to use these for other purposes is breaking that implicit agreement.

(edit) but you're probably right that i'm expecting too much.

Less diluted, but still: https://fundrise.com/vcx

> we find that lawmakers who later ascend to leadership positions perform similarly to matched peers beforehand but outperform them by 47 percentage points annually after ascension

If what you’re positing were true wouldn’t they have outperformed their peers before ascension as well

Both GitHub and Cursor’s response seems a bit lazy. Technically they may be correct in their assertion that it’s the user’s responsibility. But practically isn’t part of their product offering a safe coding environment? Invisible Unicode instruction doesn’t seem like a reasonable feature to support, it seems like a security vulnerability that should be addressed.

Interesting. So practically, they would have to hire the new applicant and then let go of the h1b worker because presumably they don’t have the budget for it?!

OP already hired H-1B in the past and that person is working for them now. OP is now in the process of doing a green card application for said employee. They can't move forward with the GC application because there are other qualified citizens/residents, but they don't have to fire the existing H1B employee.

That's how I understand OP, if that's legally true or not, I don't know.

Wouldn't you be able to deploy an app script website, which is hosted on "script.google.com" and make use of this?

This is such an ignorantly engineering centric perspective.

There is value in the larger organization being able to consume documentation and commenting on it and contributing to it.

There is conceptual value in some of these things, but I find it to be overstated and the downsides entirely ignored.

Most documentation systems have a version history.

And most documentation systems are far easier adopted by people other than engineers.

This is the equivalent of pointing out that figma has x, y, and z benefits and designers are fluent in it, so we should be using that for documentation.

Correct. Unclear wording on my part. If you build a product that is meant to be used by the open source community, you build features which are at odds with companies’ needs that care about keeping their code proprietary.

Github ux is an unmitigated disaster from an operational security perspective. In their defense, it did start out as an open-source tool. The fact that enterprises adopted it so blindly despite this is pretty interesting.

i suppose price/earnings ratio

I’d recommend reading “secrets of the temple.”

Though it will only validate your point.

> But as a matter of business ethics, you gotta tell people what you're doing with their devices.

I'm curious about this from a legal perspective.

Apple has and (probably is still) extending unpublished entitlements to developers that allow for behavior that is not publicly documented.

I don’t understand why you’re being downvoted.

Your point is absolutely correct and as far as I can tell you pointed it out genuinely, not facetiously. Edit: read other later posts here: didn’t know about the bacteria part. Learned something today!

This is absolutely not my area of expertise but intuitively there are two categories of energy sources: one which releases co2 (or other climate change impacting gases) and one which doesn’t. Wood, oil, gas, coal falls into the former. It’s just a question of time as you say until the loop closes. Solar, wind, thermal, etc would fall into the latter as far as I can tell.

What Andy giveth, Bill taketh away.

I genuinely enjoyed reading this. Thank you!

Something like 70% of water usage in AZ is agricultural [1] Somehow this never gets talked about. Somehow it's always "dumb to live in the desert" but growing water-intense crop... no problemo.

[1] https://www.arizonawaterfacts.com/water-your-facts

If you're ok with html-only, enjoy a throwback: https://mail.google.com/mail?ui=html

I'm not sure the ads would be in that UI.

I didn't know about that. That's cool.

This is great insight. Thank you for that.

I imagine lots of people are or have spent lots of money and time trying to figure out the type of data or connection from patterns as you say.

A more nuanced and correct statement would have been to say that it's much harder to do than it used to be, when you could just look at the mime-type or similar to figure out what to throttle.

You are correct. The port is part of the tcp header and my statement above is incorrect!

I think the era of traffic shaping as you describe it is no longer. Most connections are encrypted these days, a good thing. But that also means, me as an ISP in the middle, I only see the layer 4 packet. So I know where a packet is coming from and where it's going (and ttl and some other not really helpful data for this purpose.) I don't even know the port.

So I'm left with doing (dumb) traffic shaping by destination and target.

If I had to guess, I'd say that they incorrectly thought that some specific IP address (range) serves predominantly one type of data. So they throttle by the only data point they have, destination ip, and the collateral damage is everything else hosted on that ip address.