I'd argue that none of those are technology companies. We call too many companies that use computers technology companies.

Sure they use or even develop software but it's for their own internal uses. They do not develop technology as an end product to sell. They sell a service.

Sure you can update the phone, but the phone won't keep user data unless it's been unlocked.

The only avenue of updating and keeping the user data is to unlock the phone then update. Apple has purposely made it so that there isn't a backdoor.

They know the numbers that they assigned to that line that the call is coming from. Anything not in the DID list shouldn't complete that call on that line.

While a cell phone number might be a legit callback number for that person the phone company providing the T1 doesn't know your cell number. At this point any call outgoing should send the caller id information to be able to call back on that number. Spoofing has been abused too much. Same with email address spoofing. Both have legit uses but their abuses outweigh the usefulness.

Exactly ipv4 needed address extension and simplification. People have a hard enough time understanding VLANs and subnets. Let alone trying to figure out how to calculate how much I can works.

This is one of the things that drives me nuts about IPv6 proponents. They go all crazy defensive if you criticize anything about their protocol, even when the criticism is fair. I haven't seen anything from you that isn't fair and I have seen the opposite from jd.

It's a fact that IPv6 is much more complicated than IPv4.I would have just made a new protocol that corrected IPv4's mistakes, addresses would be 64bit long and used CIDR notation. Broadcast would have been kept since it's stupid simple to use the last address, with all FF's for the MAC. DHCP would still exist and would be the main way for a dynamic addresses would be assigned Dhcpv6 has a cool feature, a router can request to get a routable subnet.

IPv6 has two main mistakes. Trying to do too much for the layer it is in the network stack, and not learning from past mistakes.

No it's not.
Don't confuse a reasonable wanting with unreasonable wanting.

Multiple phones can have the same phone number. They just go in a round robin or another configuration. Zero need to spoof the number.

There are very very few legit uses of spoofing caller id and it shouldn't be generally allowed.

Trolling is just being mean and using those reasons as excuses are very bad excuses for being mean.

I guess I am asking too much.

Trolling by definition is not useful. It may be informative but there are much better ways of getting information through.

Trolling is just being an asshole to someone else online.

SMB is always running even if you turn off filesharing it's still there \\pcname\c$ will take you to that computers c drive.

Patch please

ZFS and any fs with the Copy on write feature should introduce a hinting api to rsync. That what the fs that knows what's changed can let rsync know.

What hardware concerns does IPv6 actually address? Far as I can tell it was created without too much concern for hardware. 128 bits for example. Most cpu's are going to have to use multiple cpu cycles. Due to registers being 32/64 bit (not including simd extensions.) These aren't really a concern considering how fast our computers are and that networking gear has special processors.

IPv6 fails in a few areas that some people refuse to even acknowledge. If they wanted IPv6 to be successful they would have kept it simple. For example getting rid of broadcast in favor or multicast. Another is the complete waste of addresses, each of my interfaces gets multiple /64 and then assigns the rest of the 64bit (randomly or from the mac address) if we were going to waste that many address we should have just stuck with 64bit.

64 bit addresses would have hit all the boxes of needs that ipv6 provides. BGP routes not taking up so much memory and being simpler globally. Every device being able to reasonably have it's own globally unique address.(Not every device needs a unique address) 128 bits is stupidly large, 33 bits for example is double the size of 32 bits. For each bit we are doubling.

IPv6 fails because they didn't think to make it simple. Embedded devices need to be simple, not every manufacturer is going to pay for the best programmers. I've dealt with too many "modems/routers" that barely understood ipv4 let alone ipv6.

IPxl if implemented could work. I see it as the same hack that UTF8 uses. It faces the same exact problem the IPv6 faces, Software/hardware would have to be upgraded. IPxl could then take the good stuff such as prefix delegation. (We are keeping dhcp and arp)

Just because someone has a different opinion doesn't mean they also don't have an understanding.

It just means they disagree with you.

I don't think it's lazy, It's just that many of the good names are being squated on.

Squatters are a huge problem on the internet and should have been put a stop to in the beginning.

Bindings for nodejs doesn't mean those bindings are in the browser.

I am not sure what the purpose of binding libusb if you can run your own code on the computer. Just run native code.