It fails on more than that. Sometimes, for no apparent reason at all, the whole screen will go blank and you can't do anything until you force stop the app. Also text editing not only has a shitload of bugs, but the selection of text within an editor is also horribly designed.
But again, because the web itself is overall so fucking broken by design without browser addons, you don't have to deal with the usual shit that websites send your way.
A court does, law enforcement does not. If you are stopped by a cop or fed or other LEO and they ask you for your identity, you are under no obligation to tell them.
You are correct in that they can't just randomly stop you and ask for ID, however they can if they have probable cause to believe that you were involved in illegal activity, which even SCOTUS has upheld:
Police and prosecutors absolutely can demand the people turn over passwords
That doesn't make sense to me because a password is the "what you know" authentication factor. And what would stop somebody from saying they forgot the password?
Now a fingerprint on the other hand is "who you are" and the government does have the right to make you identify "who you are" not only to law enforcement but to the courts as well.
The third authenticaiton factor "what you have" (i.e. smart card, key fob) could be compelled to be turned over only if the government can prove that not only does it exist, but that you actually have it too.
That and have the backbone providers throttle (or better yet, outright drop) foreign originated DDoS traffic, since obviously the US can't set rules for other countries' broadband providers.
Admittedly I haven't read TFA, what has me scratching my head is how they know that this phone belonged to one of the San Bernadino killers. Perhaps they know who the phones belong to, but what makes them think the owner is one of the San Bernadino killers? Perhaps they already have other evidence and they don't actually need any backdoors?
Seems more like pork to me. The problem with cybersecurity right now mainly comes from basically anybody and everybody running old shit that is vulnerable. A classic example is Android 2.3 devices that people still carry around. And of course, large companies that have obsolete OSes still running on the public internet.
This whole IoT mess is only going to make it much worse. What's needed are rules establishing a minimum standard to raise the bar for longer term security updates. I.e. rules to the effect of requiring manufacturers to provide security updates for no less than 7 years after first product general availability to market. Also provide some kind of source escrow so that if the company folds the firmware can be released as completely open source, complete with signing keys where applicable.
Also something needs to be done about the DDoS as a service situation. The primary target should be end users who harbor compromised systems connected to a broadband ISP. For example, if they're found to be participating in a DDoS attack, whether they are a willing participant or not, they are to have their internet connection throttled to 128kbit until they have cleaned their systems.
I use Firefox on Android with adblock plus, searchonymous, and google redirects fixer installed. Clunky browser overall but it's better than dealing with the usual shit that most websites (slashdot included) have. I used the Ghostery addon before, but after seeing how much better privacy badger is (or rather, how it doesn't break websites like most privacy addons do) I just use that on desktop and hope they might make it available for Android. For now, I mostly just rely on the setting to make third party cookies be session only.
Aside from the risk of someone abusing that mechanism, the potential for it to fail like it did with NEST is too great.
Isn't that why modern devices have dual firmware images? Or at least, one firmware image is just a shim that can phone home and fix things that have gone wrong in the main firmware image, or alternatively allow somebody with a PC and a simple set of instructions to connect to it and fix it.
I would say that Microsoft could improve on desktop applications by giving them their own namespace or user space (a la Android) but instead they now call these "legacy apps" and have the unrealistic expectation that you use universal apps which do have these protections.
I say unrealistic because universal apps don't have anywhere near the capability set that you can get with "legacy apps", and there's no reason to write new desktop applications anymore because typically the best way to deliver your application to desktop users is through web apps. If a web app can't do what you need to do, then a universal app probably can't either, and indeed can probably only do less things since it has to operate very strictly within Microsoft's walled garden.
Joking aside, I'm trying to figure out why this is even necessary. Who gives a shit if somebody is sexually abusive to a chat bot? The chat bot certainly doesn't give a shit.
Is that to say all config files in Unix are consistent?
They're all consistent in that they're all just plain text. All you have to do is open it and you'll know what sed parameters you want to use to extract the value you want. For example, I wrote a script that does autodiscovery of your mythtv mysql username and password by pulling it directly from a config xml file, and I didn't even need to get a special xml parser to do it. That code looks like this:
I didn't know how to do this before I wrote that, by the way, I just looked up the syntax for awk and got it to work. I tried parsing XML in a similar manner in powershell once, and could never figure it out and just gave up.
How can you complain that PS cmdlets are both too long to type and difficult to discover? They for the most part follow a very straightforward convention of [approved verb]-[specific noun]. Like Get-childitem, add-content, export-csv, etc.
Ok here's the problem: It's never clear when you need to get content or get object or get whatever other verb they want to use. There's so much different ways of retrieving information because the way its stored is never consistent. For example, if I want information about the CPU, that's a WMI object. If I want information about running processes, that's another type of object.
But bash? Everything can be treated as an ordinary file. EVERYTHING. All system objects that you want to examine can be grabbed using THE SAME COMMANDS, thus parsing those objects feels identical and very consistent. Once you are familiar with cat, dd, grep, sort, sed, and awk, that's it, you can manipulate any object you want however you want.
But with powershell, with a new object type comes a new command to learn along with its syntax and quirks.
LOL I did that in an IT shop that was primarily Microsoft driven. I was working Tier 2 tech support (also called Desktop Support) and because I wasn't a Tier 3 tech (system engineer they were called) I had to work within the limitations of what the systems already had installed. The actual system engineers were retarded though and didn't know how to manage active directory worth shit, so I ended up finding broken shit all the time and having to build workarounds for said broken shit.
This particular script was meant as part of a system to automate provisioning employee laptops, because their existing process was rather manual, and usually took about 30 minutes. After I wrote up a bunch of powershell scripts, I turned it into a 1 minute job. This is what the tech 3 guys should have been doing, and if so they could have come up with a more elegant solution. But then again, I found that they had a very narrow understanding of Microsoft infrastructure, of which I care little for myself as I'm mainly a network guy (speak of which, I was frustrated when they had all of about zero understanding of the OSI model, which when it came down to troubleshooting a problem with NTLM authentication, they blamed it on a wifi driver when it was obviously a session layer problem, and they had no fucking clue what "session layer" even means.)
But you know, they're Tech 3 and I'm only Tech 2, so they're right of course. Fortunately I don't work there anymore.
That's fine and all until one of the US Government, the MPAA/RIAA, or whatever authority tells paypal, visa, or mastercard to stop accepting payments to their enemy of the month.
I've never bought bitcoins (mined all of the ones I have back when it was easier) I've used it to donate to BTN and WCD, which I'm sure the MPAA/RIAA don't like, in which case they can go fuck themselves. That, and cashed out on a bunch of them while the price per bitcoin was stupidly high and made a few thousand bucks.
I've done a lot of neat stuff with powershell, for example I created a powershell script that gathered information about one system (using the Get-WmiObject Win32_SystemEnclosure to retrieve i.e. a computer's brand name, serial number, bios version, etc) and opened a TCP socket to feed that information to another system across the network that had a listening server which was also written in powershell.
But yeah, it totally violates the KISS principle. It's hard as fuck to look up certain information about the system because the way it's stored and retrieved is almost never intuitive (for example, you literally have to generate an XML file and then parse said file in order to get some stuff.)
It's also very hard to figure out how to do something you might not have done before, or have done very rarely, because the command names are so long that they're difficult to remember. There are shorter aliases, but they don't have any consistent naming (for example, Get-WmiObject can be shorthanded as gwmi, whereas a command like Add-PSSnapIn is shorthanded as asnp) making them also harder to remember.
I would much rather just have bash, and do that server stuff I did with tools like netcat, which although uses a separate binary, is FAR simpler than the method I used with powershell, while also having tools like dd to be able to manipulate binary blobs, and dummy block devices like/dev/zero,/dev/random, and even the ability to directly read/write to hard disks as if they were ordinary files.
If Microsoft did that, and had a good package manager for command line tools with the ability to add third-party repositories (like aptitude does) with options to compile from source (like portage does) I might actually consider using it for servers now and then. But because it doesn't, I only use it for servers either when an application requires it (as in, no Linux version available, but this is quite rare for applications meant for servers) or for active directory (also only occasionally needed.)
I'd be more likely to pay for a service that can pre-load things for future use.
Couchpotato, Sickrage, Deluge, Plex Media Server.
You don't need usenet for these, by the way, it's all torrent driven. And if you get on private trackers (where you'll see FAST torrent downloads) then you'll want to swap deluge with rtorrent, because deluge kind of chokes when you have over two thousand torrents seeding at once.
Or alternatively, buy a seedbox that provides all of these services pre-configured and even troubleshoots it for you (several exist, such as feral hosting.) I personally don't like seedboxes though because I have 12TB of local storage and a gigabit pipe at my house, and a typical seedbox to match the my local capabilities would probably cost somewhere close to $100 a month.
That was true maybe 3 years ago, however T-Mobile's coverage is rapidly approaching what Verizon has. In fact, in terms POP (point of presence, basically how many people they cover on average,) they're currently where Verizon was about a year ago:
They're also quickly catching up. If you're still seeing people in your area that don't get coverage, it's likely they have an older phone whose radio doesn't receive the newer bands T-Mobile has been using. These newer bands are lower frequency, which means they have longer range, and T-Mobile has been deploying them to towers that cover rural areas more than anywhere else, specifically to fill in those gaps you're noticing.
Tariffs typically don't work out the way they're intended. Suppose the eu does as you say; what's to stop say Canada from purchasing from a Chinese competitor that sells for a much lower price? Meanwhile EU customers are forced to pay more, and because the cost burden on Canadian customers is lower, adjacent industries that rely on purchasing these displays can now grow more freely.
This is exactly why it's often said that tariffs cost a given economy more than they're trying to save.
I get it if those ads are part of Google's network, but they rarely are. How would Google target them (in Chrome or whatever) when they're basically just images, unless they do some kind of image parsing for literally every image that loads, in which case, bye CPU cycles.
People who say what GP says either don't have a job or haven't ever worked with actual customers before.
I am a person, and I work for a corporation. And just because I work for a corporation doesn't mean customers have the right to treat me like shit. Corporations I've worked at almost always have provisions where if a customer is obviously unruly and harassing you then you can refuse to provide service to them and you won't get any shit for it from either HR or your boss. In fact you might even get bonus points if you diffuse the situation with good tact while still not providing any services.
I think Bennet Hasselton is perhaps the best evidence that slashdot isn't as intelligent as one might think.
That is, unless, we can stop Bennet. Mod this post up if you want to stop Bennet.
In terms of features, I'd say add unicode support and probably seriff fonts when usernames are displayed. The reason why using seriffs in usernames is necessary is because there's some jackass that goes around using a name similar to other people, only substituting capital I with lowercase L, or vise versa, and copying their signature, and then making posts about mycleanpc fixing his fucked up life.
(IlIlIlI notice how these letters all look the same on slashdot font? And yet they're not the same.)
This is exactly what prompted me to abandon my old 5 digit UID account: I had two lowercase L's in my name, which made it a prime target for abuse.
Slashdot Mirror
It fails on more than that. Sometimes, for no apparent reason at all, the whole screen will go blank and you can't do anything until you force stop the app. Also text editing not only has a shitload of bugs, but the selection of text within an editor is also horribly designed.
But again, because the web itself is overall so fucking broken by design without browser addons, you don't have to deal with the usual shit that websites send your way.
A court does, law enforcement does not. If you are stopped by a cop or fed or other LEO and they ask you for your identity, you are under no obligation to tell them.
You are correct in that they can't just randomly stop you and ask for ID, however they can if they have probable cause to believe that you were involved in illegal activity, which even SCOTUS has upheld:
https://www.flexyourrights.org...
Police and prosecutors absolutely can demand the people turn over passwords
That doesn't make sense to me because a password is the "what you know" authentication factor. And what would stop somebody from saying they forgot the password?
Now a fingerprint on the other hand is "who you are" and the government does have the right to make you identify "who you are" not only to law enforcement but to the courts as well.
The third authenticaiton factor "what you have" (i.e. smart card, key fob) could be compelled to be turned over only if the government can prove that not only does it exist, but that you actually have it too.
That and have the backbone providers throttle (or better yet, outright drop) foreign originated DDoS traffic, since obviously the US can't set rules for other countries' broadband providers.
Admittedly I haven't read TFA, what has me scratching my head is how they know that this phone belonged to one of the San Bernadino killers. Perhaps they know who the phones belong to, but what makes them think the owner is one of the San Bernadino killers? Perhaps they already have other evidence and they don't actually need any backdoors?
Seems more like pork to me. The problem with cybersecurity right now mainly comes from basically anybody and everybody running old shit that is vulnerable. A classic example is Android 2.3 devices that people still carry around. And of course, large companies that have obsolete OSes still running on the public internet.
This whole IoT mess is only going to make it much worse. What's needed are rules establishing a minimum standard to raise the bar for longer term security updates. I.e. rules to the effect of requiring manufacturers to provide security updates for no less than 7 years after first product general availability to market. Also provide some kind of source escrow so that if the company folds the firmware can be released as completely open source, complete with signing keys where applicable.
Also something needs to be done about the DDoS as a service situation. The primary target should be end users who harbor compromised systems connected to a broadband ISP. For example, if they're found to be participating in a DDoS attack, whether they are a willing participant or not, they are to have their internet connection throttled to 128kbit until they have cleaned their systems.
Lucky. My floppy disks were read only, eight inches wide, and only held 80K.
I use Firefox on Android with adblock plus, searchonymous, and google redirects fixer installed. Clunky browser overall but it's better than dealing with the usual shit that most websites (slashdot included) have. I used the Ghostery addon before, but after seeing how much better privacy badger is (or rather, how it doesn't break websites like most privacy addons do) I just use that on desktop and hope they might make it available for Android. For now, I mostly just rely on the setting to make third party cookies be session only.
Aside from the risk of someone abusing that mechanism, the potential for it to fail like it did with NEST is too great.
Isn't that why modern devices have dual firmware images? Or at least, one firmware image is just a shim that can phone home and fix things that have gone wrong in the main firmware image, or alternatively allow somebody with a PC and a simple set of instructions to connect to it and fix it.
I would say that Microsoft could improve on desktop applications by giving them their own namespace or user space (a la Android) but instead they now call these "legacy apps" and have the unrealistic expectation that you use universal apps which do have these protections.
I say unrealistic because universal apps don't have anywhere near the capability set that you can get with "legacy apps", and there's no reason to write new desktop applications anymore because typically the best way to deliver your application to desktop users is through web apps. If a web app can't do what you need to do, then a universal app probably can't either, and indeed can probably only do less things since it has to operate very strictly within Microsoft's walled garden.
Sorry but this is as asinine as saying the video game Doom makes people into mass murderers.
Joking aside, I'm trying to figure out why this is even necessary. Who gives a shit if somebody is sexually abusive to a chat bot? The chat bot certainly doesn't give a shit.
Is that to say all config files in Unix are consistent?
They're all consistent in that they're all just plain text. All you have to do is open it and you'll know what sed parameters you want to use to extract the value you want. For example, I wrote a script that does autodiscovery of your mythtv mysql username and password by pulling it directly from a config xml file, and I didn't even need to get a special xml parser to do it. That code looks like this:
DBUSER="$(awk -F '[]' '/UserName/{print $3}' $CONFIGXML)"
DBPASS="$(awk -F '[]' '/Password/{print $3}' $CONFIGXML)"
I didn't know how to do this before I wrote that, by the way, I just looked up the syntax for awk and got it to work. I tried parsing XML in a similar manner in powershell once, and could never figure it out and just gave up.
How can you complain that PS cmdlets are both too long to type and difficult to discover? They for the most part follow a very straightforward convention of [approved verb]-[specific noun]. Like Get-childitem, add-content, export-csv, etc.
Ok here's the problem: It's never clear when you need to get content or get object or get whatever other verb they want to use. There's so much different ways of retrieving information because the way its stored is never consistent. For example, if I want information about the CPU, that's a WMI object. If I want information about running processes, that's another type of object.
But bash? Everything can be treated as an ordinary file. EVERYTHING. All system objects that you want to examine can be grabbed using THE SAME COMMANDS, thus parsing those objects feels identical and very consistent. Once you are familiar with cat, dd, grep, sort, sed, and awk, that's it, you can manipulate any object you want however you want.
But with powershell, with a new object type comes a new command to learn along with its syntax and quirks.
LOL I did that in an IT shop that was primarily Microsoft driven. I was working Tier 2 tech support (also called Desktop Support) and because I wasn't a Tier 3 tech (system engineer they were called) I had to work within the limitations of what the systems already had installed. The actual system engineers were retarded though and didn't know how to manage active directory worth shit, so I ended up finding broken shit all the time and having to build workarounds for said broken shit.
This particular script was meant as part of a system to automate provisioning employee laptops, because their existing process was rather manual, and usually took about 30 minutes. After I wrote up a bunch of powershell scripts, I turned it into a 1 minute job. This is what the tech 3 guys should have been doing, and if so they could have come up with a more elegant solution. But then again, I found that they had a very narrow understanding of Microsoft infrastructure, of which I care little for myself as I'm mainly a network guy (speak of which, I was frustrated when they had all of about zero understanding of the OSI model, which when it came down to troubleshooting a problem with NTLM authentication, they blamed it on a wifi driver when it was obviously a session layer problem, and they had no fucking clue what "session layer" even means.)
But you know, they're Tech 3 and I'm only Tech 2, so they're right of course. Fortunately I don't work there anymore.
That's fine and all until one of the US Government, the MPAA/RIAA, or whatever authority tells paypal, visa, or mastercard to stop accepting payments to their enemy of the month.
I've never bought bitcoins (mined all of the ones I have back when it was easier) I've used it to donate to BTN and WCD, which I'm sure the MPAA/RIAA don't like, in which case they can go fuck themselves. That, and cashed out on a bunch of them while the price per bitcoin was stupidly high and made a few thousand bucks.
I've done a lot of neat stuff with powershell, for example I created a powershell script that gathered information about one system (using the Get-WmiObject Win32_SystemEnclosure to retrieve i.e. a computer's brand name, serial number, bios version, etc) and opened a TCP socket to feed that information to another system across the network that had a listening server which was also written in powershell.
But yeah, it totally violates the KISS principle. It's hard as fuck to look up certain information about the system because the way it's stored and retrieved is almost never intuitive (for example, you literally have to generate an XML file and then parse said file in order to get some stuff.)
It's also very hard to figure out how to do something you might not have done before, or have done very rarely, because the command names are so long that they're difficult to remember. There are shorter aliases, but they don't have any consistent naming (for example, Get-WmiObject can be shorthanded as gwmi, whereas a command like Add-PSSnapIn is shorthanded as asnp) making them also harder to remember.
I would much rather just have bash, and do that server stuff I did with tools like netcat, which although uses a separate binary, is FAR simpler than the method I used with powershell, while also having tools like dd to be able to manipulate binary blobs, and dummy block devices like /dev/zero, /dev/random, and even the ability to directly read/write to hard disks as if they were ordinary files.
If Microsoft did that, and had a good package manager for command line tools with the ability to add third-party repositories (like aptitude does) with options to compile from source (like portage does) I might actually consider using it for servers now and then. But because it doesn't, I only use it for servers either when an application requires it (as in, no Linux version available, but this is quite rare for applications meant for servers) or for active directory (also only occasionally needed.)
I think "virus opens you" is applicable to any platform. Allusion to Russian jokes notwithstanding.
I'd be more likely to pay for a service that can pre-load things for future use.
Couchpotato, Sickrage, Deluge, Plex Media Server.
You don't need usenet for these, by the way, it's all torrent driven. And if you get on private trackers (where you'll see FAST torrent downloads) then you'll want to swap deluge with rtorrent, because deluge kind of chokes when you have over two thousand torrents seeding at once.
Or alternatively, buy a seedbox that provides all of these services pre-configured and even troubleshoots it for you (several exist, such as feral hosting.) I personally don't like seedboxes though because I have 12TB of local storage and a gigabit pipe at my house, and a typical seedbox to match the my local capabilities would probably cost somewhere close to $100 a month.
That was true maybe 3 years ago, however T-Mobile's coverage is rapidly approaching what Verizon has. In fact, in terms POP (point of presence, basically how many people they cover on average,) they're currently where Verizon was about a year ago:
http://finance.yahoo.com/news/...
They're also quickly catching up. If you're still seeing people in your area that don't get coverage, it's likely they have an older phone whose radio doesn't receive the newer bands T-Mobile has been using. These newer bands are lower frequency, which means they have longer range, and T-Mobile has been deploying them to towers that cover rural areas more than anywhere else, specifically to fill in those gaps you're noticing.
Tariffs typically don't work out the way they're intended. Suppose the eu does as you say; what's to stop say Canada from purchasing from a Chinese competitor that sells for a much lower price? Meanwhile EU customers are forced to pay more, and because the cost burden on Canadian customers is lower, adjacent industries that rely on purchasing these displays can now grow more freely.
This is exactly why it's often said that tariffs cost a given economy more than they're trying to save.
Negative publicity often results in some places getting more sales. Especially because it helps boost SEO ratings.
I get it if those ads are part of Google's network, but they rarely are. How would Google target them (in Chrome or whatever) when they're basically just images, unless they do some kind of image parsing for literally every image that loads, in which case, bye CPU cycles.
People who say what GP says either don't have a job or haven't ever worked with actual customers before.
I am a person, and I work for a corporation. And just because I work for a corporation doesn't mean customers have the right to treat me like shit. Corporations I've worked at almost always have provisions where if a customer is obviously unruly and harassing you then you can refuse to provide service to them and you won't get any shit for it from either HR or your boss. In fact you might even get bonus points if you diffuse the situation with good tact while still not providing any services.
I think Bennet Hasselton is perhaps the best evidence that slashdot isn't as intelligent as one might think.
That is, unless, we can stop Bennet. Mod this post up if you want to stop Bennet.
In terms of features, I'd say add unicode support and probably seriff fonts when usernames are displayed. The reason why using seriffs in usernames is necessary is because there's some jackass that goes around using a name similar to other people, only substituting capital I with lowercase L, or vise versa, and copying their signature, and then making posts about mycleanpc fixing his fucked up life.
(IlIlIlI notice how these letters all look the same on slashdot font? And yet they're not the same.)
This is exactly what prompted me to abandon my old 5 digit UID account: I had two lowercase L's in my name, which made it a prime target for abuse.