Hacker Newsnew | past | comments | ask | show | jobs | submit | AnssiH's commentslogin

> Doesn't Amazon shipping have to go to the billing address on the credit card?

No, I've had stuff shipped to plenty of addresses.


It looks like the billing address restriction was a "thing" years ago, but is simply too impractical for modern day e-commerce. People want to do gifting, or get things delivered to temporary accomodations like vacation spots. They are relying on approaches like heuristics (sudden purchase for something expensive going to an unusual address), plus CVV verification to help ensure that the purchaser physically has the card (still allows theft, but adds a layer).

No, it was never a "thing," "mark as gift" has always been an option on Amazon to send gifts to family and friends.

Netflix added ad-supported plans in 2022.


On Linux, the maximum length was doubled to 256 in v5.1 (2019-05-05).


Windows95 also doubled the dos limit of a cmdline from 128 to 256 in… 1995.


> In Valorant (similar to Counter Strike), at the start of the game you have 60 seconds to buy your weapons and abilities for the round. Valorant/CS is typically a best-of-13, and before each round is a 60 second "buy" period.

Valorant's buy phase is 30 seconds, with +15sec at start of match and halftime.


No, it is not true, just a common myth.

In the seller documentation they say they can track the source of commingled inventory - they achieve this by never putting them on the same physical shelf location.

Also mentioned by Amazon spokesman in e.g. this article: https://archive.is/ra6RT

> Amazon can also track the original seller of each unit


A fair point and important distinction, but so is the difference between "we CAN" and "we WILL/DO". That "myth" didn't come out of thin air. It's a result of of amazon not doing that unless they felt it financially prudent to do so/until enough people bitched about it.

The OP article is exhibit A for how common of an issue this was.


> Launchpad marked it as "This bug affects 1 person.".

That just means no one has clicked "affects me too" button yet (after logging in).


It is not fixed.

In the thread you linked to people are confusing a typo correction ("mas fixed" => "was fixed") as a claim about this new issue being fixed.

The one that was fixed is this similar old issue from years ago: https://issuetracker.google.com/issues/172048751


Oh, that's unfortunate, very confusing thread.


> But it just doesn't work like that for DOCSIS or GPON where the cable modems or ONTs these days do much more than just media conversion - SIP, PPPoE, IGMP, etc. even if they don't do Wi-Fi (so ISPs don't call them "routers" - except SingTel, which uses "ONR" to distinguish these units because they are in fact routers for IPTV and SIP).

At least in Finland the norm is that you can use your own DOCSIS modem from any manufacturer, you just tell the ISP your modem's MAC address.

Not for GPON, though.


I'm not a subject matter expert by any means, but the 8311 Community Firmware group has made great strides on their SFP+ ONT FWs. The majority of users are using their WAS-110 implementation for XGS-PON to ‘bypass’ the ISPs ONT/Gateway device, in the states there's a lot of users doing this on AT&T Fiber, but the Discord community has a large global following with users around the world reporting success. They have some users on GPON, its a bit of a different bypass but people have been successful. I run a bypass directly into my UDM-Pro using a WAS-110.

https://pon.wiki/guides/masquerade-as-the-att-inc-bgw320-500...

Discord: https://discord.gg/8311


Same here in the US. You can bring your own DOCSIS modem to any cable internet provider.


For me, Comcast only allowed a few models. Because it requires full control. They uploaded a Comcast firmware on it. And they warned me that after that the device is basically stuck to only work with Comcast. This was around 2017.


That sounds odd - I wonder if it was a relic of your local infrastructure. I used my own DOCSIS modem with its own firmware on Comcast around the same time. It was a generic Arris Surfboard.


Comcast's list of approved devices includes (or used to at least) some of the more common Arris Surfboards; I also used one when I had Comcast service. You probably also used one that was 'compatible'.


The list of compatible devices was simply a list of all devices that supported DOCSIS 3.1 at the time.

At no point was my firmware swapped out, or anything of that nature.


AFAIK the Android binary blobs are generally userspace, not kernel drivers.


AFAICS this is about exploiting race condition bugs that require a large number of requests to be processed almost-simultaneously.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: