1. Nobody said anything about the cables being thinner. But due to the fact that a house has 3 phases it is suboptimal to just suck all the juice on one phase which has an upper limit (fuses before the meter) of 35A. This is different to the US where there's mostly just one phase but with a bunch more amps. So yeah, great for the US market, crap for EU market.
2. All good and great but I would still trust it more if the connections ARE separate, that way it fails safe, with having the same connectors for DC/AC you have to rely on whatever clever mechanisms and security stuff you put in which still would not fail safe but fail bad. (not sure what will happen if you suddenly pump 400V *DC* from the car into your house's wiring if the system fails (maybe due to a bad voltage sensor).
3. As mentioned somewhere else using that connector might also prevent uses like V2G/V2L etc, (maybe that might come later with some software update, but considering how crappy Tesla is with software when it comes to their current Wallbox (got the gen3 one, it's garbage although it could do so much more as it has RFID reader in it etc. Telsa just couldn't be arsed to implement it))

The main differing issue is AC charging:
NACS would not work in europe due to the fact that most homes in europe have 3 phase home installations with which means up to 12kW with only 16A via the 3-phase CCS2 connector (and could go up to 22kW if the onboard charger supports it).
NACS on the other hand can only deliver a single phase which would make it all but unusable in europe but would work in the US where there is mostly just one (or maybe two) phases in a single home
So yeah, NACS is maybe a nice connector as long as:
- you only want to charge dog slow on AC (might be not that bad in the US as there they seem to try to compensate for the lack of voltage by having a crapton of Amps allowed with required fat cables but even then I think you're done at 7.2kW).
- you only want to do DC fast charging.
- you never have any software failures with your wall charger (in CCS the AC and DC side are separate, with NACS, a software failure could connect the battery directly to AC .. :/)

For the newer shelly devices see https://github.com/tasmota/mgo... and https://devices.esphome.io/

You can use home assistant ( https://www.home-assistant.io/ ) with Shelly Plugs (or their relays) ( https://www.shelly.cloud/ ) Flash them with tasmota (minimal), then change that to esphome. https://github.com/yaourdt/mgo... https://esphome.io/ All open source, works excellent and with esphome using noise encryption (basically like wireguard) for the communication between it and home assistant it is just the best combination you can have at the moment (btw. esphome also allows you to use mqtt in case you already have some existing infrastructure using that)

Exactly.

And even if they "allow" everyone to take part, that doesn't mean they allow everyone.
For example, i wanted to join as service provider in the category chat with my priviate XMPP server.
However, T-Mobile said that they will only consider services that cater to the public. (And that answer was only after a year-long mail battle where they were either delaying or trying different excuses why my traffic should not qualify)

That means, anyone wanting to use their own chat server will have to pay up while using one of the big players (whatsapp etc) will be "free".

Now imagine having such a back-and-forth effort with ALL ISPs around the world (or even just europe...)

This has the obvious downside of Google slowly replacing the open source parts of Android with its proprietary closed-source binaries in the name of "security"

That has been an increasing problem during the last few years, see this article from 2018:

https://arstechnica.com/gadgets/2018/07/googles-iron-grip-on-android-controlling-open-source-by-any-means-necessary/

Newer Samsung phones are DROPPING any IPv6 packet (not just RAs) as soon as the screen is off. (this is in the WiFi firmware so even 3rd party roms like CyanogenMod are affected).
So anything that is connected via IPv6 will be disconnected.

See this thread (the title is about ICMPv6 but later it clarifies that newer phones drop ALL IPv6 traffic): http://developer.samsung.com/forum/board/thread/view.do?boardName=General&messageId=239890

Even if they do that to save battery, there are better ways to do this and it should be configurable.

Please help and raise a stink with Samsung over this!

APK P.S.=> AdBlock does FAR less than hosts do & FAR less efficiently - hosts by way of comparison, do MORE w/ less + Hosts start w/ the IP stack before REDUNDANT inefficient addons BEGIN to operate (as 1st resolver queried): AdBlock's 4++gb & 100% CPU usage flooring inefficiency -> https://blog.mozilla.org/nneth... + ClarityRay defeats it + it 'souled-out' & is crippled by default paid off to not do its job http://techcrunch.com/2013/07/... & ABP too http://finance.yahoo.com/news/...

Wow.

Did the timecube guy go into the ad block business or did you just hire him for marketing?

Even spam mails I get regarding viagra have a more sophisticated and yet simple language.

Wrong. You are using the wrong browser. Firefox mobile works fine with adblock plus...

That's pure BS.

You mean it is pure coincidence that all the components that get pushed into the play services app are now closed source? (keyboard, location service etc. etc.)

How would it affect updatability to keep those components open source?

There is a reason to move these apps away from the "core" android: http://arstechnica.com/gadgets/2013/10/googles-iron-grip-on-android-controlling-open-source-by-any-means-necessary/

All, except the nice bits...

http://arstechnica.com/gadgets...

Are you joking?

If I have an IPv6 only internal network (not really exotic) I shouldn't be required to set up an IPv4 nameserver and DHCP server etc.etc. just for android.

Also your examples of NETBIOS and IPX are backwards. This is more like having to use a NETBIOS server in order to use IPv4... which would be equally stupid to having to use an IPv4 server in order to use IPv6.

I wonder if Android can at least do IPv6 correctly now. At the moment you can only use IPv6 in combination with an IPv4 DNS server (which has to be assgined using DHCP (IPv4). (RDNSS value from IPv6 is not used and you can't even specify IPv6 namservers manually for WiFi, thus a pure IPv6 environment is not possible)

Yeah, appeared while I was complaining. You win this round, Mozilla!

Another release, another time when their own FTP server is the LAST place to get the release.

Last time it took around a week until the Android version (30) was available here, where previously that was the first place to find it.

What's next, changelog on twitter only?