floatingatoll

That’s an awfully dismissive broad-brush viewpoint about homeless people, that isn’t supported by studies of — and social support of — homeless people around the world.

“We mine things to make cash flow”?

Amazon won’t accept returns of low-value or misdelivered items, and instructs customers to throw them into their wastebin for a refund rather than have to process them.

7 months ago, 624 comments were posted in a discussion about Amazon returns neither being painless nor simple. My favorite is this write up noting that returns are only processed if your predicted future revenue exceeds the return requested: https://news.ycombinator.com/item?id=27333273

But in general, Amazon won’t honor their purchase protection policy for high value items without extensive argument and delaying tactics, which puts shoppers at risk for precisely the purchased that most need protection.

Amazon’s a flea market, and flea markets operate so cheaply by neither vetting sellers, nor inspecting goods, nor taking any responsibility for sales outcomes. Amazon will do everything in its power to avoid those duties because their retail profit model is to dodge human responsibilities such as those for labor savings.

Buying from a “fulfilled by Amazon” trusted vendor won’t necessarily help either, because Amazon also bins all products with a given UPC into a single bucket, no matter who the seller is.

Erm, I don’t think we’re describing the same sides of the flow, but I trust you’re right anyways. Apologies for my confusion.

(And Plaid noted that they vastly prefer to oauth to banks, and do with many other banks, but that Venmo won’t accept oauth and demands credentials.)

I assume this is /s and I laughed when I read it. Well played.

I’ve been in at least five roles in eleven years at my current company, and projects frequently poach me for weeks or months at a time, sometimes leading to role changes, sometimes not. It’s not everyone’s cup of tea, but I enjoy it.

And their confirmation of that is out today, with an iOS 15.2 bug reported to Apple as well.

https://www.theverge.com/22878885/verizon-att-t-mobile-apple...

Your wish is granted by w3/css-color-4:

§ 12.1 Color space for interpolation https://www.w3.org/TR/css-color-4/#interpolation-space

Disagreeing with the concepts of software patents doesn’t mitigate Google’s theft of them. Google knew they were stealing patented works when they did so. I don’t own any Sonos or Google products, and I’m still annoyed with Google for knowingly stealing when they could afford to pay.

Ultimately, the title rules cannot be coded into programming logic and fully documented; they’re a mix of predictable (No Studly Caps) algorithms, submitter’s edits, and moderator’s edits. Human judgment calls are expected - for example, titles should be edited to be succinct when necessary, but never to present the submitter’s opinion. Criteria will not always be applied consistently, each submitter and moderator is a different person, and not everything is seen and fixed when it’s slightly or greatly wrong.

There is not a lot of difference between http3 and a VPN protocol that can bundle and transport multiple bidirectional channels asynchronously, especially when considering the restriction “only uses http protocols and none other” — a quality that many Apple services share with Private Relay.

It’s absolutely speculative to consider http3 a viable replacement for ”a VPN”, as many consider Private Relay to be^, but that’s not due to any technical limitation. We could benchmark Squid-over-http3 versus Wireguard VPN in various latency and packet loss scenarios today (if implemented), and get productive and interesting results. We could do the same with varnish / nginx versus openvpn / pptpd. Whether or not it supports CONNECT is worth noting, but is no obstacle for “let’s assume that everything is HTTP”, as appears widely applicable to both Apple’s services to their customers, and a significant majority of consumer VPN traffic, today.

Have those benchmarks been performed yet? Are we all doing it wrong by using wireguard et al. to Mullvad et al. for 99% HTTP traffic and we just don’t realize it yet? I look forward someday to finding out the answer :)

ps. iOS carrier APIs and functionality are NDA’d so I don’t have any other information or useful examples to offer, as my experience with carriers as their customer is very limited. Perhaps others will know; apologies.

^ I haven’t seen an FP yet titled “If it can’t carry SSH traffic, it’s not a VPN”, but certainly there’ll be one someday. I can’t predict when, though, anymore than I can guess when someone else will realize to seriously ask, supported by benchmarks and encapsulation overhead charts, “Should tcp be deprecated in favor of http?”. (I have no opinion on what the correct answers are at this time.)

ps. Everyone who’s reading this story and discussion, go read the report that T-Mobile only forces Private Relay off for customers who are enrolled in their content-filtering product:

https://tmo.report/2022/01/t-mobile-blocking-icloud-private-...

You could ask the mods why directly about the pig heart article, if you’re seriously interested, using the footer contact link. I wouldn’t do this for every edit and expect a reply, but it seems like asking them to chime in here for a single case study would be simpler and more factual than guessing at reasoning, and I imagine they’re probably willing.

In the US, big Carrier A implements the full array of iPhone capabilities for carriers under Settings > Cellular; big Carrier B does not. Most people aren’t aware of what they’re missing, but for example, when implemented by the carrier properly, the cellular data usage heading is “this billing cycle” instead of “however long it’s been since you last clicked Reset Statistics manually”; and Settings > Phone > Call Forwarding has an iOS native UI rather than forcing you to dial 1980s-style *#12##0112636382* modem strings into the dialer.

Does your carrier implement this? If not, will you switch carriers? It’s unclear what degree of importance you assign to your expectation, as it could be anything from “for the tasks I care about” to “in every possibly way without exception”. (For me: It’s not important eniugh to switch carriers on its own, though it’s certainly a factor if I have greater reasons.)

Apple could simply reimplement APN and iCloud Files and etc over their own Private Relay connections, so that any carrier who blocks Private Relay ends up blocking all push notifications to all Apple devices. They have not yet done so, but if they do, either all US carriers will have to collude to block it — which could reasonably be considered anti-competitive behavior and would attract immediate governmental review — or they'd all have to allow Private Relay, as otherwise they'd bleed millions of customers due to being hostile to iPhone.

It seems safe to assume that Apple doesn't like user APN traffic being tracked any more than the rest of their traffic, and so I would imagine this is essentially the roadmap for all Apple Services provided to their users over the next few years.

It's also possible the Beta is just to see what happens when they make the traffic visible and possible to block, and having seen the carriers tending towards "block anything that inhibits tracking", they might simply target Private Relay 2.0 as "HTTP3 over 443/udp to http3.apple.com" and have that be an N-way reflector point for all customer-provided Apple services, including Private Relay and the rest as different channels over that multipath HTTP3 layer. They chose to implement Private Relay in a way that could be detected, and are measuring how neutrality-hating carriers respond. Assuming it's their final answer is not a bet I'd take.

Okay, so, is there a relative comparison of available union pricing plans and their offered features and the cut they take per paycheck? We have this for AWS/GCP, and for app stores, so what’s the equivalent in tech unions?

Is it possible to take a page from the "YC Standard Deal" model and create a "Union Standard Deal" for tech workers, that offers an opinionated and non-comprehensive view of the basic necessities that any tech worker union should demand?

Tech is known for shooting the moon, but if we can stand up opinionated examples of "minimum viable bargains", maybe that would help everyone grasp what's being proposed, and contrast the MVB with their local union's offerings.

Folders have tabs, keyboards have spaces

There are many cultures that strongly value parents, elders and extended family, and Covid is 'a cold' that could kill random loved ones in their extended family, such as their favorite grandmother or their aunt's best friend. For a teenager, being the vector of infection that leads to such a death would result in critical emotional trauma and lead to a much higher risk of suicide — a fact they are well aware of, given the significant uptick in suicides within their age group since Covid began.

They may be teenagers, but they're not wrong to attend to the minutiae; whether for selfish or for social reasons, that awareness may be all that is keeping them and their loved ones alive. It is cruel and unjust and wrong that they alone are attending to the minutiae of masking, but here in the United States our social support systems often require them to bear that responsibility, as the adults responsible for them often do not.

Maybe it's a pre-production prototype, repurposed to fit a need :)

Here's the CTO reply later on in this conversation.

> Plaid CTO here. We’ve worked closely w/ FIs to move towards standards like OAuth & App2App to remove the use of credentials. A vast majority of our traffic is already going through these APIs today and we're working with more and more banks to enable OAuth.

Plaid is contracted by Venmo (and many others) to provide a bank-agnostic API to Venmo, and either uses credentials or token-based or app-based methods depending on how competent the bank is. Apparently Simon's bank only offers the credentials method.

I would upvote your Show HN about whatever made this site worth creating.

Yes (DOS 6, cpu Intel 8088).

Contacting the mods with this feedback would let them clear up all the dupes and merge conversations, using the footer contact link. Otherwise they might not see this.

Please forgive the insult of my choice of wording — I made up a phrase on the spot and it is clearly unacceptable. I’m sorry. In any case, we disagree, so I won’t try to offer a replacement as the intent of my viewpoint has already been conveyed adequately.

TIL, makes sense. Didn’t think of it as “combusts inside the engine” versus “combusts next to the engine”.

“There’s no visible pool of water, must be fine”

None of those are in the same “likelihood of death to a person who has common sense” risk category as the high-voltage Mercedes front compartment. See also the various other replies along these lines, such as:

https://news.ycombinator.com/item?id=29801119

Another way to look at this is, “are there any consumer-serviceable parts within the compartment?” and “are there instantly-fatal wires/terminals within the compartment?”. The pair of answers “no” and “yes” for the Mercedes demand a wholly different approach to risk management and safety design than a gas engine, whose pair of answers are “yes” and “no”.

EV high-voltage are not consumer-serviceable, as a regular consumer cannot be expected to understand high-voltage safety practices. Yes, some consumers know how to service them, but the necessary safety practices that are generally commonly understood for gas engines are not commonly understood for electric engines, and are regulated differently as a result.