I don't disagree with your idea of politely avoiding terms to avoid needlessly offending friends. My problem is that in recent years, I keep discovering some formerly benign term has been declared offensive, fencing off another part of the language. And I'm made to feel I'm a terrible person for not just knowing it. Everything seems to offend someone for one reason or another and I'm feeling less polite about it these days.
Thank you. I've been getting scared lately because terms that used to be benign are suddenly indicators of irredeemable bigotry of one sort or another. Mulatto isn't a term I generally used unless I was performing a certain Nirvana song, but I never would have thought it derogatory.
Racism is a problem and historically in America we've displayed our exceptionalism in how we've manifested it over they years. But the language is becoming a minefield of things that are suddenly unforgivable to express. And yes, in some cases it being done to weaponize the language for things like politics. But in cases like this, I think someone seems to have unilaterally declared parts of the language out-of-bounds without informing the rest of the English speakers.
Yes, using the terms on the application is odd and anachronistic. But when did they become slurs?
I don't really disagree with what you say, but I think it could be hard to retro fit into an existing service. It's well thought out and if you have it in mind, it's actually pretty useful for reasoning how how to protect the data and support the required functionality.
It's hard to say what would be most difficult since that is kind of dependent on the service in question. Me read though is that backups will be a general problem. It's not uncommon to store files for multiple users in one file system or record for multiple users in one DB. If you save more than 1 month's worth of backups, you either need to nuke all you backups any time someone requests their data be removed or you need a backup strategy that backs up non-user and per-user data separately. You need to be able to discard all the backups for a user at once. And you need the remainder of the backup to still be consistent.
Like the other problems, if you plan for it, you can probably implement a general solution, but I'm not aware of any back tools that would make this easy. And then there are offline backups. Do you have a separate tape per-user?
I would concede that Google has a better model than Apple here. Far better is possible and has been implemented in other systems.
Two things I would like to see added to Android:
- I trust this app that I am explicitly loading / updating.
- I trust apps from these specific stores (list which may or may not include Google's store)
In other words, I don't want to have to cripple all security just to use fdroid with or instead of the play store.
Not really. I'm used to multi-platform support in kernels and API and cross compilation of systems. It's a scales down system but I've seen those before and simulate them on occasion. Windows supporting more than is only remarkable because Microsoft decided to try (and no-one else has the choice in the case of Windows).
The binary translator to make windows software work on an Open Pandora is more interesting. And again, it's only interesting because the people involved don't have to source to do a proper port.
It's not that Linux was the same. It's that it would inevitably acquire any of the useful features only other UNIX had minus the annoyances that come with attempts at lock-in.
Solaris and the other UNIXes died for the same reason. They all provided roughly the same feature set in slightly incompatible ways. It made development, maintenance and administration unnecessarily difficult and error prone.
None of the vendors put sincere effort into fixing it. The GNU tools focus portability helped immensely with this. Free source tools ended up defining the only true portable standard. They gained features consistently that the others had and implemented them in ways that served the developers & user rather than an particular vendor. Eventually Linux and the FSF's tools became the best of breed UNIX without even being UNIX.
Docker is a mess because it was originally developed in a way that served the interests of Docker Inc. The single local name space of images, the poor default implement of a remote registry, the ability to only search images in dockerhub... It wasn't designed to support secure isolation. That was bolted on later and needs continual patching. There is a not-so-new love affair with BSD/MIT style licenses and "Open Core" business models. It's only bringing back the bad old days of the past.
I'm just pointing out the whole setup isn't just some crazy new idea.
Honest question. What other 3rd party records random people phone calls to businesses? I'm pretty sure the BBB doesn't. I've heard of having a third party audit for quality, but never quite like this.
Or he's not skilled enough to keep track of which audiences he must only share his public positions with and which ones he may share his private positions with.
First example, Microsoft Windows 10. Everybody knows it is snooping on users in ways that many do not approve of. It has been doing so since it's release and very little has changed. No one has come up with a reliable fix.
Second example. Cisco routers have been found to have hard coded back door accounts built into them. This has happened several times. Pretty much any one with even a modest understanding of system security knows this to be poor practice. No one outside of Cisco has any way of knowing if there are any more back door accounts in Cisco's firmware nor do they have a way to know if a new back door gets introduced.
Third example. Mozilla has in several instances added features to Firefox that snooped on users in ways that many did not approve of. People went into the source code and found it. People and system distributors made forks of Firefox that disabled or removed these features. Mozilla ended up providing ways to disable these features in every case and in many cases removed or disabled these features by default or provided an affirmative opt in.
Final example for today. Canonical added a feature to Ubuntu search interface that snooped on users in ways that many did not approve of. People went into the source code and found it. Canonical immediately documented how to opt-out and disable the feature for themselves. Forks and downstream distributions of Ubuntu removed the feature.
The lesson class is not that Open Source software is invulnerable. The lesson is that it is harder to hide and force undesirable and unsafe behavior into Open Source software compared to non-Open Source software. Open Source software is not perfect. It's merely better by distributing the possibility of finding and fixing problems to a wider group than just those who would benefit from not fixing.
You aren't thinking big picture. Consider how the Democrats view him as the ultimate in naive, inept corruption. And consider how they will automatically consider a manned trip to Mars to be fatally impossible as long as Trump is in the White House.
And then consider how Trump likes hotels. If we have a chance to get people to Mars, they might be able to convince him to forgo a second term in the hopes of building the first Martian Hotel and declare himself Martian Dictator.
To address your first paragraph, as others have pointed out, there are a number of deficiencies between what the old API could do and what web extensions can do. You sound like you should be knowledgeable enough that I shouldn't need to cite that. Also as others have mentions, some of the gaps have been lessened after the original API was drop and it was done more as concessions.
To address your other paragraph, once the original API was dropped I lost most of my extensions and most of the ones that still worked worked less well. Several of these extensions (broken and sub-functional) have forums with lists of (old) bug reports they are asking users to vote on to close the necessary gaves to be able to function again. Tabmix+ is one of the ones you mentioned later in this thread. I have several and none have improved. Blame the extension authors if it makes you feel better, but that's not going to help anything.
Finally, I still stand by my comment, which you did not address. I fully expect Mozilla to follow Google's lead here. I wouldn't be unhappy to be wrong.
Firefox had a more function API for extensions to do content blocking. They dumped it so they could use the same crippled extension API as Chrome. I can't imagine Mozilla won't follow suit again. They are used to crippling Firefox to be like Chrome.
No. If he doesn't know what made the sound, then he should just act like he didn't hear it. If any one else heard it and asked what it was, he should mock them and call them crazy.
Creative Sound Blaster ZxR and AE-5 sound card support
Does this even matter any more with pulseaudio? PA killed the usefulness of multi-open cards. PA certainly isn't low latency. What good is a better sound card when the near-mandated sound solution enforces software mixing? It would be like getting a 3D video accelerator on a system that enforces software rendering.
Well, if it was billed as a home automation tool, taking away some automation functionality seems questionable. That API may not be what they meant, but it seems they discovered a market they were accidentally serving. If they are wise they will find a way to continue to serve that market, unless those are users they want to serve. But that comes with a trade-off in lost goodwill.
...it wasn't turning off or removing anything, it was a redesign with replacement.
Yeah. That's "If you want to keep your doctor / insurance..." dishonest. There are plenty of once useful extensions for Firefox that don't work and can't work, because the APIs necessary to re-implement them have not been "replaced". I'm getting by, but I hate the web a lot more now than when I could at least make a browser behave in a tolerable fashion.
I wonder if my town can level a tax on just the grocery store and hardware store? Or can they tax the auto parts store on the East side of Main Street, but not the one on the west side? The sandwich shop, not the burger place? Can you create a tax on select individuals? Mark, but not Bill?
I suspect the answer is yes in all cases, but that you just don't write it that explicitly in the legislation.
I installed Debian on my son's Win10 Home edition to get lftp. I had to check a few more check boxes to enable it compared to a Win10 Enterprise VM I had to use at work.
I guess I'm assuming that WLS will be used for things like docker containers. Currently, interesting applications can depend on things like network (stack) APIs to accelerate data transfers and are affected by Linux-isms in things like the Nagle problem. I could see more use of userland filesystem implementations or attempts to make more use of kbus/dbus. All of these would be things that WLS will have to emulate reasonably.
Linux's userland is not standing still. Glibc has been hiding a lot of that, but recently there has been talk about the kernel providing a library to get more direct access to system calls that glibc isn't exposing sufficiently (in the eyes of some). You could be right that WLS will not see enough use to matter. On the other hand I know several developers of Linux only products that don't run Linux and go to great lengths to avoid using it (causing trouble when they integrate code that's never even been built on Linux). If MS plays their cards right, WLS could become the crutch that many cloud developers wish they had.
Slashdot Mirror
I don't disagree with your idea of politely avoiding terms to avoid needlessly offending friends. My problem is that in recent years, I keep discovering some formerly benign term has been declared offensive, fencing off another part of the language. And I'm made to feel I'm a terrible person for not just knowing it. Everything seems to offend someone for one reason or another and I'm feeling less polite about it these days.
Thank you. I've been getting scared lately because terms that used to be benign are suddenly indicators of irredeemable bigotry of one sort or another. Mulatto isn't a term I generally used unless I was performing a certain Nirvana song, but I never would have thought it derogatory.
Racism is a problem and historically in America we've displayed our exceptionalism in how we've manifested it over they years. But the language is becoming a minefield of things that are suddenly unforgivable to express. And yes, in some cases it being done to weaponize the language for things like politics. But in cases like this, I think someone seems to have unilaterally declared parts of the language out-of-bounds without informing the rest of the English speakers.
Yes, using the terms on the application is odd and anachronistic. But when did they become slurs?
And such things, if affective, will lower your social credit score.
That's why they shot first.
I don't really disagree with what you say, but I think it could be hard to retro fit into an existing service. It's well thought out and if you have it in mind, it's actually pretty useful for reasoning how how to protect the data and support the required functionality.
It's hard to say what would be most difficult since that is kind of dependent on the service in question. Me read though is that backups will be a general problem. It's not uncommon to store files for multiple users in one file system or record for multiple users in one DB. If you save more than 1 month's worth of backups, you either need to nuke all you backups any time someone requests their data be removed or you need a backup strategy that backs up non-user and per-user data separately. You need to be able to discard all the backups for a user at once. And you need the remainder of the backup to still be consistent.
Like the other problems, if you plan for it, you can probably implement a general solution, but I'm not aware of any back tools that would make this easy. And then there are offline backups. Do you have a separate tape per-user?
Honest question. Would they do it in a room full of people? Would they post it in WeChat or QQ?
I would concede that Google has a better model than Apple here. Far better is possible and has been implemented in other systems.
Two things I would like to see added to Android:
- I trust this app that I am explicitly loading / updating.
- I trust apps from these specific stores (list which may or may not include Google's store)
In other words, I don't want to have to cripple all security just to use fdroid with or instead of the play store.
Not really. I'm used to multi-platform support in kernels and API and cross compilation of systems. It's a scales down system but I've seen those before and simulate them on occasion. Windows supporting more than is only remarkable because Microsoft decided to try (and no-one else has the choice in the case of Windows).
The binary translator to make windows software work on an Open Pandora is more interesting. And again, it's only interesting because the people involved don't have to source to do a proper port.
It's not that Linux was the same. It's that it would inevitably acquire any of the useful features only other UNIX had minus the annoyances that come with attempts at lock-in.
Solaris and the other UNIXes died for the same reason. They all provided roughly the same feature set in slightly incompatible ways. It made development, maintenance and administration unnecessarily difficult and error prone.
None of the vendors put sincere effort into fixing it. The GNU tools focus portability helped immensely with this. Free source tools ended up defining the only true portable standard. They gained features consistently that the others had and implemented them in ways that served the developers & user rather than an particular vendor. Eventually Linux and the FSF's tools became the best of breed UNIX without even being UNIX.
Docker is a mess because it was originally developed in a way that served the interests of Docker Inc. The single local name space of images, the poor default implement of a remote registry, the ability to only search images in dockerhub... It wasn't designed to support secure isolation. That was bolted on later and needs continual patching. There is a not-so-new love affair with BSD/MIT style licenses and "Open Core" business models. It's only bringing back the bad old days of the past.
Right. That's what systemd is for.
Are you sure wouldn't rather see the money go into some politicial's vanity "charity" foundation?
I'm just pointing out the whole setup isn't just some crazy new idea.
Honest question. What other 3rd party records random people phone calls to businesses? I'm pretty sure the BBB doesn't. I've heard of having a third party audit for quality, but never quite like this.
Or he's not skilled enough to keep track of which audiences he must only share his public positions with and which ones he may share his private positions with.
OK. Case study students.
First example, Microsoft Windows 10. Everybody knows it is snooping on users in ways that many do not approve of. It has been doing so since it's release and very little has changed. No one has come up with a reliable fix.
Second example. Cisco routers have been found to have hard coded back door accounts built into them. This has happened several times. Pretty much any one with even a modest understanding of system security knows this to be poor practice. No one outside of Cisco has any way of knowing if there are any more back door accounts in Cisco's firmware nor do they have a way to know if a new back door gets introduced.
Third example. Mozilla has in several instances added features to Firefox that snooped on users in ways that many did not approve of. People went into the source code and found it. People and system distributors made forks of Firefox that disabled or removed these features. Mozilla ended up providing ways to disable these features in every case and in many cases removed or disabled these features by default or provided an affirmative opt in.
Final example for today. Canonical added a feature to Ubuntu search interface that snooped on users in ways that many did not approve of. People went into the source code and found it. Canonical immediately documented how to opt-out and disable the feature for themselves. Forks and downstream distributions of Ubuntu removed the feature.
The lesson class is not that Open Source software is invulnerable. The lesson is that it is harder to hide and force undesirable and unsafe behavior into Open Source software compared to non-Open Source software. Open Source software is not perfect. It's merely better by distributing the possibility of finding and fixing problems to a wider group than just those who would benefit from not fixing.
You aren't thinking big picture. Consider how the Democrats view him as the ultimate in naive, inept corruption. And consider how they will automatically consider a manned trip to Mars to be fatally impossible as long as Trump is in the White House.
And then consider how Trump likes hotels. If we have a chance to get people to Mars, they might be able to convince him to forgo a second term in the hopes of building the first Martian Hotel and declare himself Martian Dictator.
How could the Dems pass that up?
To address your first paragraph, as others have pointed out, there are a number of deficiencies between what the old API could do and what web extensions can do. You sound like you should be knowledgeable enough that I shouldn't need to cite that. Also as others have mentions, some of the gaps have been lessened after the original API was drop and it was done more as concessions.
To address your other paragraph, once the original API was dropped I lost most of my extensions and most of the ones that still worked worked less well. Several of these extensions (broken and sub-functional) have forums with lists of (old) bug reports they are asking users to vote on to close the necessary gaves to be able to function again. Tabmix+ is one of the ones you mentioned later in this thread. I have several and none have improved. Blame the extension authors if it makes you feel better, but that's not going to help anything.
Finally, I still stand by my comment, which you did not address. I fully expect Mozilla to follow Google's lead here. I wouldn't be unhappy to be wrong.
Firefox had a more function API for extensions to do content blocking. They dumped it so they could use the same crippled extension API as Chrome. I can't imagine Mozilla won't follow suit again. They are used to crippling Firefox to be like Chrome.
No. If he doesn't know what made the sound, then he should just act like he didn't hear it. If any one else heard it and asked what it was, he should mock them and call them crazy.
Creative Sound Blaster ZxR and AE-5 sound card support
Does this even matter any more with pulseaudio? PA killed the usefulness of multi-open cards. PA certainly isn't low latency. What good is a better sound card when the near-mandated sound solution enforces software mixing? It would be like getting a 3D video accelerator on a system that enforces software rendering.
Well, if it was billed as a home automation tool, taking away some automation functionality seems questionable. That API may not be what they meant, but it seems they discovered a market they were accidentally serving. If they are wise they will find a way to continue to serve that market, unless those are users they want to serve. But that comes with a trade-off in lost goodwill.
...it wasn't turning off or removing anything, it was a redesign with replacement.
Yeah. That's "If you want to keep your doctor / insurance ..." dishonest. There are plenty of once useful extensions for Firefox that don't work and can't work, because the APIs necessary to re-implement them have not been "replaced". I'm getting by, but I hate the web a lot more now than when I could at least make a browser behave in a tolerable fashion.
I wonder if my town can level a tax on just the grocery store and hardware store? Or can they tax the auto parts store on the East side of Main Street, but not the one on the west side? The sandwich shop, not the burger place? Can you create a tax on select individuals? Mark, but not Bill?
I suspect the answer is yes in all cases, but that you just don't write it that explicitly in the legislation.
I installed Debian on my son's Win10 Home edition to get lftp. I had to check a few more check boxes to enable it compared to a Win10 Enterprise VM I had to use at work.
I guess I'm assuming that WLS will be used for things like docker containers. Currently, interesting applications can depend on things like network (stack) APIs to accelerate data transfers and are affected by Linux-isms in things like the Nagle problem. I could see more use of userland filesystem implementations or attempts to make more use of kbus/dbus. All of these would be things that WLS will have to emulate reasonably.
Linux's userland is not standing still. Glibc has been hiding a lot of that, but recently there has been talk about the kernel providing a library to get more direct access to system calls that glibc isn't exposing sufficiently (in the eyes of some). You could be right that WLS will not see enough use to matter. On the other hand I know several developers of Linux only products that don't run Linux and go to great lengths to avoid using it (causing trouble when they integrate code that's never even been built on Linux). If MS plays their cards right, WLS could become the crutch that many cloud developers wish they had.