241–250 of 278 posts
Earlier quoted context omitted.
I have never seen this before
Never seen it in the US, but it was fairly common when I was on vacation in Europe
Earlier quoted context omitted.
200 bytes for the business logic. 47MB for the UI & boilerplate around the business logic. I get that this may be the easiest way to develop and publish an application today, but it's sad that this is the direction we have taken in recent years.
Modern app bloat in one analogy: Business logic size: ~20 bytes Total app size: ~47 MB = 47,000,000 bytes Bloat factor: 47,000,000 / 20 = 2,350,000 Let’s scale this up and say the business logic is 1 pound. Then the whole app would weigh: 1 lb × 2,350,000 = 2,350,000 pounds What weighs ~2.35 million pounds? - A fully loaded Boeing 747-8: ~987,000 lbs - Another fully loaded 747-8: ~987,000 lbs - A blue whale: ~330,000…
Earlier quoted context omitted.
200 bytes for the business logic. 47MB for the UI & boilerplate around the business logic. I get that this may be the easiest way to develop and publish an application today, but it's sad that this is the direction we have taken in recent years.
Modern app bloat in one analogy: Business logic size: ~20 bytes Total app size: ~47 MB = 47,000,000 bytes Bloat factor: 47,000,000 / 20 = 2,350,000 Let’s scale this up and say the business logic is 1 pound. Then the whole app would weigh: 1 lb × 2,350,000 = 2,350,000 pounds What weighs ~2.35 million pounds? - A fully loaded Boeing 747-8: ~987,000 lbs - Another fully loaded 747-8: ~987,000 lbs - A blue whale: ~330,000…
Earlier quoted context omitted.
Yes but you need a space station OS (Unix) to enjoy the terseness of 47-200 bytes of business logic. ps: I love both space stations and Unix
The solution to this problem requires you to interact with the OS, so a solution that requires tools found in the OS itself isn't a bad one. Its so simple you can have a script triggered by a desktop shortcut and be done with it. That all said, a simple GUI API provided by the OS for simple programs like this would be nice, just to give the user better feedback on the process. Is it done? Is it doing anything? Did it…
If you really want to screw with these set your MAC address to 00:00:00:00:00:00 It’s an illegal address, but most equipment will take it because test devices occasionally come from the factory with that MAC. But higher level stuff might barf on it because it’s technically illegal.
alas, macOS refuses: $ sudo ifconfig en0 ether 00:00:00:00:00:01 ifconfig: ioctl (SIOCAIFADDR): Can't assign requested address edit: but this worked on my external NIC! Network wasn't happy though and DHCP didn't work. Ubiquiti had a funny note about this MAC: " Officially Xerox, but 0:0:0:0:0:0 is more common "
As always, ymmv.
On some equipment this may cause a broadcast storm, depending on how they implement things. Cisco equipment with some configs will send a packet to all the ports if it receives a packet and can't figure out where it's supposed to go.
Earlier quoted context omitted.
How does that work with MAC address conflicts and clashes? I naively thought every MAC address had to be unique.
They must be unique in a LAN segment. And only the lower 3 bytes in a MAC are “unique” as the upper 3 are the vendor ID and relatively fixed. In practice people put fewer than 256 devices on networks (class C), so they have less than 1/65536 possibility of complete failure. And far less because they have a mix of OUIs. But yeah, if you put a few hundred or thousand security cameras or other device from a single vendo…
MAC randomization does not have to constrain itself to the lower three bytes; you can randomize the OUI too.
What does Android MAC randomization do with the OUI?
According to this possible hallucination from Google Gemini 2.5 Flash, the OUI is partially randomized too:
- Locally Administered Bit (U/L bit): This bit (the 2nd LSB of the first octet) is forced to '1'.
- Unicast/Multicast Bit (I/G bit): The least significant bit (LSB) of the first octet is usually set to '0' to indicate a unicast address.
- Remaining OUI bits (and the entire lower three bytes): All the other bits in the MAC address, including the remaining bits of the first octet, the entire second and third octets (which are part of the OUI), and the entire last three octets, are randomized.
Me again:
So if two bits are fixed, everyone in the randomized space is randomizing 46 bits, which contains 7.03E+13 addresses.
Practically speaking, it seems that the only way you will ever see a clash arising from the above randomization strategy is if two devices are using the same very poorly seeded PRNG.
This reminded me of an old app that would scan the MAC addresses of devices already connected to a paid WiFi network. You would then just change your MAC to one that already paid for the WiFi, and then reset it once you were done.
Wouldn't that lead to interference with the original device using that MAC address? Ie both of you getting packets meant for the other etc?
Alternatively, if you don't want to run the whole Electron app, the money is this line: sudo.exec("/System/Library/PrivateFrameworks/Apple80211.framework/Versions/Current/Resources/airport en0 -z && ifconfig en0 ether `openssl rand -hex 6 | sed 's/\(..\)/\1:/g; s/.$//'`",
200 bytes for the business logic. 47MB for the UI & boilerplate around the business logic. I get that this may be the easiest way to develop and publish an application today, but it's sad that this is the direction we have taken in recent years.
Alternatively, if you don't want to run the whole Electron app, the money is this line: sudo.exec("/System/Library/PrivateFrameworks/Apple80211.framework/Versions/Current/Resources/airport en0 -z && ifconfig en0 ether `openssl rand -hex 6 | sed 's/\(..\)/\1:/g; s/.$//'`",
What would you use instead to build a macOS GUI program with comparable ease? SwiftUI? Python + Tk (using the ancient system Python)? Something like Red?