I work in disconnects for businesses for a major telco, and we have a lot of auditing requirements due to SOx. I'd hate to think of what records would look like without these requirements. Sure people can still cheat, but it's also a CYA for the company that is doing the reporting.
There is still slamming now and then, but there are far fewer disconnects in error, where the telco is at fault. Usually it is the business customer not knowing which location they actually wanted to disconnect on their side, or not reading what they wanted to disconnect.
It would be nice to not have the reports. But you know if a business is not required to do it then there will be no tracking of any type done, which is where major abuses take place.
I don't mind doing the reports in addition my normal workload because I'd been able to go over others work that I am auditing and get it back on track if there is a mistake in it.
the program, working state and game data have been squeezed into the four megabytes of main memory it requires either shareware or commercial pak files, Amiga and PC paks have been successfully used total conversions and mods should work, assuming they respect the tiny memory size networking currently has been removed, but will return at a later date.
The latest article on rollable E-Ink displays sounds an awful lot like the PDA video phones used in one of the Gene Roddenberry series. They just happen to be black and white prototypes, and still need some improvement on things like voice and touch-screen input. Tag in the biometric thumb scan security, and you'd have one interesting little overpriced device.
If it happens once, it's a bug. If it happens twice, it's a feature. If it happens more than twice, it's a design philosophy.