#permissions — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #permissions, aggregated by home.social.
-
Chrome crashes with "FD ownership violation" and exit_code=133 #permissions #googlechrome
-
Chrome crashes with "FD ownership violation" and exit_code=133 #permissions #googlechrome
-
Chrome crashes with "FD ownership violation" and exit_code=133 #permissions #googlechrome
-
Chrome crashes with "FD ownership violation" and exit_code=133 #permissions #googlechrome
-
Chrome crashes with "FD ownership violation" and exit_code=133 #permissions #googlechrome
-
PCSX2 BIOS Not Detecting on Ubuntu After Installation #permissions
-
CW: Uncomfortable truth about the Fediverse that'll totally scare Mastodon users; CW: long (over 2,400 characters), Fediverse meta, Fediverse-beyond-Mastodon meta, quote-post meta, character limit meta
When you see it, you'll shit brix: The Hubzilla timeline.
The "it" that you're supposed to see is:- The Fediverse did, in fact, not start with Mastodon.
There was something in the Fediverse before Mastodon: Mistpark was there almost 6 years before Mastodon, Hubzilla was there 10 months before Mastodon.
Mastodon came into an already existing Fediverse with servers and users and content and a culture.
The Fediverse has never been only Mastodon. And it will never be. - The Fediverse had quote-posts almost 6 years before Mastodon.
(Accurate implication: The non-Mastodon Fediverse can quote-post any public Mastodon toot with no problems, and it has always been able to do so, for as long as Mastodon has been around.) - The Fediverse had groups almost 6 years before Mastodon which still doesn't even support groups.
- The Fediverse had better lists than Mastodon lists almost 6 years before Mastodon.
- The Fediverse had reply control almost 6 years before Mastodon where people are still waiting for some kind of reply control.
- The Fediverse had permissions almost 6 years before Mastodon where the concept of permissions is completely unknown.
- The Fediverse had no character limit to worry about almost 6 years before Mastodon came along with only 500 characters.
The Fediverse had 16,777,215 characters almost 6 years before Mastodon had 500 characters. - The Fediverse had full rich-text formatting almost 6 years before Mastodon.
The Fediverse could generate bold type, italics, underline,code blocks, bullet-point lists etc. without any Unicode trickery. Almost 6 years before Mastodon was there. And more than 12 years before Mastodon could even only display that stuff.
Although it should be blatantly obvious: This here is not a Mastodon toot. This post comes from Hubzilla directly to your Mastodon apps.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #Mistpark #Friendica #Hubzilla #FediverseCulture #QuotePost #QuotePosts #QuoteTweet #QuoteTweets #QuoteToot #QuoteToots #QuoteBoost #QuoteBoosts #QuotedShares #Groups #FediGroups #FediverseGroups #Lists #ReplyControl #Permissions #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #500Characters #TextFormatting #RichText #NotOnlyMastodon #FediverseIsNotMastodon #MastodonIsNotTheFediverse - The Fediverse did, in fact, not start with Mastodon.
-
CW: Uncomfortable truth about the Fediverse that'll totally scare Mastodon users; CW: long (over 2,400 characters), Fediverse meta, Fediverse-beyond-Mastodon meta, quote-post meta, character limit meta
When you see it, you'll shit brix: The Hubzilla timeline.
The "it" that you're supposed to see is:- The Fediverse did, in fact, not start with Mastodon.
There was something in the Fediverse before Mastodon: Mistpark was there almost 6 years before Mastodon, Hubzilla was there 10 months before Mastodon.
Mastodon came into an already existing Fediverse with servers and users and content and a culture.
The Fediverse has never been only Mastodon. And it will never be. - The Fediverse had quote-posts almost 6 years before Mastodon.
(Accurate implication: The non-Mastodon Fediverse can quote-post any public Mastodon toot with no problems, and it has always been able to do so, for as long as Mastodon has been around.) - The Fediverse had groups almost 6 years before Mastodon which still doesn't even support groups.
- The Fediverse had better lists than Mastodon lists almost 6 years before Mastodon.
- The Fediverse had reply control almost 6 years before Mastodon where people are still waiting for some kind of reply control.
- The Fediverse had permissions almost 6 years before Mastodon where the concept of permissions is completely unknown.
- The Fediverse had no character limit to worry about almost 6 years before Mastodon came along with only 500 characters.
The Fediverse had 16,777,215 characters almost 6 years before Mastodon had 500 characters. - The Fediverse had full rich-text formatting almost 6 years before Mastodon.
The Fediverse could generate bold type, italics, underline,code blocks, bullet-point lists etc. without any Unicode trickery. Almost 6 years before Mastodon was there. And more than 12 years before Mastodon could even only display that stuff.
Although it should be blatantly obvious: This here is not a Mastodon toot. This post comes from Hubzilla directly to your Mastodon apps.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #Mistpark #Friendica #Hubzilla #FediverseCulture #QuotePost #QuotePosts #QuoteTweet #QuoteTweets #QuoteToot #QuoteToots #QuoteBoost #QuoteBoosts #QuotedShares #Groups #FediGroups #FediverseGroups #Lists #ReplyControl #Permissions #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #500Characters #TextFormatting #RichText #NotOnlyMastodon #FediverseIsNotMastodon #MastodonIsNotTheFediverse - The Fediverse did, in fact, not start with Mastodon.
-
CW: Uncomfortable truth about the Fediverse that'll totally scare Mastodon users; CW: long (over 2,400 characters), Fediverse meta, Fediverse-beyond-Mastodon meta, quote-post meta, character limit meta
When you see it, you'll shit brix: The Hubzilla timeline.
The "it" that you're supposed to see is:- The Fediverse did, in fact, not start with Mastodon.
There was something in the Fediverse before Mastodon: Mistpark was there almost 6 years before Mastodon, Hubzilla was there 10 months before Mastodon.
Mastodon came into an already existing Fediverse with servers and users and content and a culture.
The Fediverse has never been only Mastodon. And it will never be. - The Fediverse had quote-posts almost 6 years before Mastodon.
(Accurate implication: The non-Mastodon Fediverse can quote-post any public Mastodon toot with no problems, and it has always been able to do so, for as long as Mastodon has been around.) - The Fediverse had groups almost 6 years before Mastodon which still doesn't even support groups.
- The Fediverse had better lists than Mastodon lists almost 6 years before Mastodon.
- The Fediverse had reply control almost 6 years before Mastodon where people are still waiting for some kind of reply control.
- The Fediverse had permissions almost 6 years before Mastodon where the concept of permissions is completely unknown.
- The Fediverse had no character limit to worry about almost 6 years before Mastodon came along with only 500 characters.
The Fediverse had 16,777,215 characters almost 6 years before Mastodon had 500 characters. - The Fediverse had full rich-text formatting almost 6 years before Mastodon.
The Fediverse could generate bold type, italics, underline,code blocks, bullet-point lists etc. without any Unicode trickery. Almost 6 years before Mastodon was there. And more than 12 years before Mastodon could even only display that stuff.
Although it should be blatantly obvious: This here is not a Mastodon toot. This post comes from Hubzilla directly to your Mastodon apps.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #Mistpark #Friendica #Hubzilla #FediverseCulture #QuotePost #QuotePosts #QuoteTweet #QuoteTweets #QuoteToot #QuoteToots #QuoteBoost #QuoteBoosts #QuotedShares #Groups #FediGroups #FediverseGroups #Lists #ReplyControl #Permissions #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #500Characters #TextFormatting #RichText #NotOnlyMastodon #FediverseIsNotMastodon #MastodonIsNotTheFediverse - The Fediverse did, in fact, not start with Mastodon.
-
CW: Uncomfortable truth about the Fediverse that'll totally scare Mastodon users; CW: long (over 2,400 characters), Fediverse meta, Fediverse-beyond-Mastodon meta, quote-post meta, character limit meta
When you see it, you'll shit brix: The Hubzilla timeline.
The "it" that you're supposed to see is:- The Fediverse did, in fact, not start with Mastodon.
There was something in the Fediverse before Mastodon: Mistpark was there almost 6 years before Mastodon, Hubzilla was there 10 months before Mastodon.
Mastodon came into an already existing Fediverse with servers and users and content and a culture.
The Fediverse has never been only Mastodon. And it will never be. - The Fediverse had quote-posts almost 6 years before Mastodon.
(Accurate implication: The non-Mastodon Fediverse can quote-post any public Mastodon toot with no problems, and it has always been able to do so, for as long as Mastodon has been around.) - The Fediverse had groups almost 6 years before Mastodon which still doesn't even support groups.
- The Fediverse had better lists than Mastodon lists almost 6 years before Mastodon.
- The Fediverse had reply control almost 6 years before Mastodon where people are still waiting for some kind of reply control.
- The Fediverse had permissions almost 6 years before Mastodon where the concept of permissions is completely unknown.
- The Fediverse had no character limit to worry about almost 6 years before Mastodon came along with only 500 characters.
The Fediverse had 16,777,215 characters almost 6 years before Mastodon had 500 characters. - The Fediverse had full rich-text formatting almost 6 years before Mastodon.
The Fediverse could generate bold type, italics, underline,code blocks, bullet-point lists etc. without any Unicode trickery. Almost 6 years before Mastodon was there. And more than 12 years before Mastodon could even only display that stuff.
Although it should be blatantly obvious: This here is not a Mastodon toot. This post comes from Hubzilla directly to your Mastodon apps.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #Mistpark #Friendica #Hubzilla #FediverseCulture #QuotePost #QuotePosts #QuoteTweet #QuoteTweets #QuoteToot #QuoteToots #QuoteBoost #QuoteBoosts #QuotedShares #Groups #FediGroups #FediverseGroups #Lists #ReplyControl #Permissions #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #500Characters #TextFormatting #RichText #NotOnlyMastodon #FediverseIsNotMastodon #MastodonIsNotTheFediverse - The Fediverse did, in fact, not start with Mastodon.
-
CW: Uncomfortable truth about the Fediverse that'll totally scare Mastodon users; CW: long (over 2,400 characters), Fediverse meta, Fediverse-beyond-Mastodon meta, quote-post meta, character limit meta
When you see it, you'll shit brix: The Hubzilla timeline.
The "it" that you're supposed to see is:- The Fediverse did, in fact, not start with Mastodon.
There was something in the Fediverse before Mastodon: Mistpark was there almost 6 years before Mastodon, Hubzilla was there 10 months before Mastodon.
Mastodon came into an already existing Fediverse with servers and users and content and a culture.
The Fediverse has never been only Mastodon. And it will never be. - The Fediverse had quote-posts almost 6 years before Mastodon.
(Accurate implication: The non-Mastodon Fediverse can quote-post any public Mastodon toot with no problems, and it has always been able to do so, for as long as Mastodon has been around.) - The Fediverse had groups almost 6 years before Mastodon which still doesn't even support groups.
- The Fediverse had better lists than Mastodon lists almost 6 years before Mastodon.
- The Fediverse had reply control almost 6 years before Mastodon where people are still waiting for some kind of reply control.
- The Fediverse had permissions almost 6 years before Mastodon where the concept of permissions is completely unknown.
- The Fediverse had no character limit to worry about almost 6 years before Mastodon came along with only 500 characters.
The Fediverse had 16,777,215 characters almost 6 years before Mastodon had 500 characters. - The Fediverse had full rich-text formatting almost 6 years before Mastodon.
The Fediverse could generate bold type, italics, underline,code blocks, bullet-point lists etc. without any Unicode trickery. Almost 6 years before Mastodon was there. And more than 12 years before Mastodon could even only display that stuff.
Although it should be blatantly obvious: This here is not a Mastodon toot. This post comes from Hubzilla directly to your Mastodon apps.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #Mistpark #Friendica #Hubzilla #FediverseCulture #QuotePost #QuotePosts #QuoteTweet #QuoteTweets #QuoteToot #QuoteToots #QuoteBoost #QuoteBoosts #QuotedShares #Groups #FediGroups #FediverseGroups #Lists #ReplyControl #Permissions #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #500Characters #TextFormatting #RichText #NotOnlyMastodon #FediverseIsNotMastodon #MastodonIsNotTheFediverse - The Fediverse did, in fact, not start with Mastodon.
-
CW: Uncomfortable truth about the Fediverse that'll totally scare Mastodon users; CW: long (over 2,400 characters), Fediverse meta, Fediverse-beyond-Mastodon meta, quote-post meta, character limit meta
When you see it, you'll shit brix: The Hubzilla timeline.
The "it" that you're supposed to see is:- The Fediverse did, in fact, not start with Mastodon.
There was something in the Fediverse before Mastodon: Mistpark was there almost 6 years before Mastodon, Hubzilla was there 10 months before Mastodon.
Mastodon came into an already existing Fediverse with servers and users and content and a culture.
The Fediverse has never been only Mastodon. And it will never be. - The Fediverse had quote-posts almost 6 years before Mastodon.
(Accurate implication: The non-Mastodon Fediverse can quote-post any public Mastodon toot with no problems, and it has always been able to do so, for as long as Mastodon has been around.) - The Fediverse had groups almost 6 years before Mastodon which still doesn't even support groups.
- The Fediverse had better lists than Mastodon lists almost 6 years before Mastodon.
- The Fediverse had reply control almost 6 years before Mastodon where people are still waiting for some kind of reply control.
- The Fediverse had permissions almost 6 years before Mastodon where the concept of permissions is completely unknown.
- The Fediverse had no character limit to worry about almost 6 years before Mastodon came along with only 500 characters.
The Fediverse had 16,777,215 characters almost 6 years before Mastodon had 500 characters. - The Fediverse had full rich-text formatting almost 6 years before Mastodon.
The Fediverse could generate bold type, italics, underline,code blocks, bullet-point lists etc. without any Unicode trickery. Almost 6 years before Mastodon was there. And more than 12 years before Mastodon could even only display that stuff.
Although it should be blatantly obvious: This here is not a Mastodon toot. This post comes from Hubzilla directly to your Mastodon apps.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #Mistpark #Friendica #Hubzilla #FediverseCulture #QuotePost #QuotePosts #QuoteTweet #QuoteTweets #QuoteToot #QuoteToots #QuoteBoost #QuoteBoosts #QuotedShares #Groups #FediGroups #FediverseGroups #Lists #ReplyControl #Permissions #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #500Characters #TextFormatting #RichText #NotOnlyMastodon #FediverseIsNotMastodon #MastodonIsNotTheFediverse - The Fediverse did, in fact, not start with Mastodon.
-
Quand tu veux télécharger une #application d'accès à des chronos (#mylaps ; comptage sur des courses de voitures RC) et que tu te rends compte que l'App a été conçue pour #siphonner tout ce qu'elle pouvait comme données.
Rien dans le descriptif de l'application ne laisse penser qu'elle a besoin de toutes ces #permissions pour fonctionner normalement.
On va s'en passer je crois... 😅
Merci à #exodus #privacy pour le travail d'analyse de toutes ces app 👍
-
Quand tu veux télécharger une #application d'accès à des chronos (#mylaps ; comptage sur des courses de voitures RC) et que tu te rends compte que l'App a été conçue pour #siphonner tout ce qu'elle pouvait comme données.
Rien dans le descriptif de l'application ne laisse penser qu'elle a besoin de toutes ces #permissions pour fonctionner normalement.
On va s'en passer je crois... 😅
Merci à #exodus #privacy pour le travail d'analyse de toutes ces app 👍
-
Quand tu veux télécharger une #application d'accès à des chronos (#mylaps ; comptage sur des courses de voitures RC) et que tu te rends compte que l'App a été conçue pour #siphonner tout ce qu'elle pouvait comme données.
Rien dans le descriptif de l'application ne laisse penser qu'elle a besoin de toutes ces #permissions pour fonctionner normalement.
On va s'en passer je crois... 😅
Merci à #exodus #privacy pour le travail d'analyse de toutes ces app 👍
-
Weird as it sounds, I think we need an actual law, like some kind of bill of rights, that says you can't notify me on my phone without offering me highly fine-tuned control of each kind of message.
Notifications intrude into my life. Sometimes my phone is on waiting for emergencies or other high-priority issues while I sleep. If a friend wakes me, I can have them dialed up or down in priority.
But Android is designed so Audible won't let me have control of my audiobooks in the lock screen without notifications turned on, yet once I've done that, Audible has no compunction against advertising new book releases in the middle of the night via notifications. I should be able to get cash compensation in court for that.
And my USB-C cable, once I plug it into my Android phone insists on randomly popping up an utterly inscrutible notification saying "you need to log in if you want to see notifications", or some such, and then when I do there is no notification to see. It was just random.
And Android Auto likes to give me two completely pointless notifications, one when I plug my phone into the car and one saying Android Auto is available. The first one I don't need a notification about because I just plugged in my phone. But more importantly, the second one is a lie. Android Auto MIGHT be available and it confirms nothing. The handshake may have been done wrong, so all it tells me is the thing I know already, which is that Android Auto is on the phone. But I might have to pull the plug and replug it to be properly connected. So the notification is worse than pointless and just floods my screen with stuff I don't care about that appears to need immediate attention. And then Android asks, as soon as I disconnect it, how my experience was. I always say "Bad" because part of my experience is getting asked that pesky message that I do not want and would happily say "never do this".
These all seem like technical problems, but they are not. They are reminders that we no longer control our lives, that companies can, at a whim, intrude into our lives with pointless rituals that whittle away our existence. I'm not being metaphorical when I say we need laws on this. I absolutely mean that if we don't write strong law on this, it will only get worse. Or we need to enforce the 4th Amendment on a theory, like Larry Lessig has effectively said in the past, that programmatic code is effectively a kind of government that binds us and our choices in life as surely as legal code does.
But what DO we get laws about? Having to login to use an operating system so they can track us better, know who we are and where we are at every moment. We need laws against such laws.
#marketing #notifications #android #ui #ux #settings #design #QualityOfLife #computers #LockScreen #permissions #law #legal #lawsuits #ClassAction #rights #HumanRights #BillOfRights #identity #intrusion #interruption #4thAmendment #government #code
-
Weird as it sounds, I think we need an actual law, like some kind of bill of rights, that says you can't notify me on my phone without offering me highly fine-tuned control of each kind of message.
Notifications intrude into my life. Sometimes my phone is on waiting for emergencies or other high-priority issues while I sleep. If a friend wakes me, I can have them dialed up or down in priority.
But Android is designed so Audible won't let me have control of my audiobooks in the lock screen without notifications turned on, yet once I've done that, Audible has no compunction against advertising new book releases in the middle of the night via notifications. I should be able to get cash compensation in court for that.
And my USB-C cable, once I plug it into my Android phone insists on randomly popping up an utterly inscrutible notification saying "you need to log in if you want to see notifications", or some such, and then when I do there is no notification to see. It was just random.
And Android Auto likes to give me two completely pointless notifications, one when I plug my phone into the car and one saying Android Auto is available. The first one I don't need a notification about because I just plugged in my phone. But more importantly, the second one is a lie. Android Auto MIGHT be available and it confirms nothing. The handshake may have been done wrong, so all it tells me is the thing I know already, which is that Android Auto is on the phone. But I might have to pull the plug and replug it to be properly connected. So the notification is worse than pointless and just floods my screen with stuff I don't care about that appears to need immediate attention. And then Android asks, as soon as I disconnect it, how my experience was. I always say "Bad" because part of my experience is getting asked that pesky message that I do not want and would happily say "never do this".
These all seem like technical problems, but they are not. They are reminders that we no longer control our lives, that companies can, at a whim, intrude into our lives with pointless rituals that whittle away our existence. I'm not being metaphorical when I say we need laws on this. I absolutely mean that if we don't write strong law on this, it will only get worse. Or we need to enforce the 4th Amendment on a theory, like Larry Lessig has effectively said in the past, that programmatic code is effectively a kind of government that binds us and our choices in life as surely as legal code does.
But what DO we get laws about? Having to login to use an operating system so they can track us better, know who we are and where we are at every moment. We need laws against such laws.
#marketing #notifications #android #ui #ux #settings #design #QualityOfLife #computers #LockScreen #permissions #law #legal #lawsuits #ClassAction #rights #HumanRights #BillOfRights #identity #intrusion #interruption #4thAmendment #government #code
-
Weird as it sounds, I think we need an actual law, like some kind of bill of rights, that says you can't notify me on my phone without offering me highly fine-tuned control of each kind of message.
Notifications intrude into my life. Sometimes my phone is on waiting for emergencies or other high-priority issues while I sleep. If a friend wakes me, I can have them dialed up or down in priority.
But Android is designed so Audible won't let me have control of my audiobooks in the lock screen without notifications turned on, yet once I've done that, Audible has no compunction against advertising new book releases in the middle of the night via notifications. I should be able to get cash compensation in court for that.
And my USB-C cable, once I plug it into my Android phone insists on randomly popping up an utterly inscrutible notification saying "you need to log in if you want to see notifications", or some such, and then when I do there is no notification to see. It was just random.
And Android Auto likes to give me two completely pointless notifications, one when I plug my phone into the car and one saying Android Auto is available. The first one I don't need a notification about because I just plugged in my phone. But more importantly, the second one is a lie. Android Auto MIGHT be available and it confirms nothing. The handshake may have been done wrong, so all it tells me is the thing I know already, which is that Android Auto is on the phone. But I might have to pull the plug and replug it to be properly connected. So the notification is worse than pointless and just floods my screen with stuff I don't care about that appears to need immediate attention. And then Android asks, as soon as I disconnect it, how my experience was. I always say "Bad" because part of my experience is getting asked that pesky message that I do not want and would happily say "never do this".
These all seem like technical problems, but they are not. They are reminders that we no longer control our lives, that companies can, at a whim, intrude into our lives with pointless rituals that whittle away our existence. I'm not being metaphorical when I say we need laws on this. I absolutely mean that if we don't write strong law on this, it will only get worse. Or we need to enforce the 4th Amendment on a theory, like Larry Lessig has effectively said in the past, that programmatic code is effectively a kind of government that binds us and our choices in life as surely as legal code does.
But what DO we get laws about? Having to login to use an operating system so they can track us better, know who we are and where we are at every moment. We need laws against such laws.
#marketing #notifications #android #ui #ux #settings #design #QualityOfLife #computers #LockScreen #permissions #law #legal #lawsuits #ClassAction #rights #HumanRights #BillOfRights #identity #intrusion #interruption #4thAmendment #government #code
-
Weird as it sounds, I think we need an actual law, like some kind of bill of rights, that says you can't notify me on my phone without offering me highly fine-tuned control of each kind of message.
Notifications intrude into my life. Sometimes my phone is on waiting for emergencies or other high-priority issues while I sleep. If a friend wakes me, I can have them dialed up or down in priority.
But Android is designed so Audible won't let me have control of my audiobooks in the lock screen without notifications turned on, yet once I've done that, Audible has no compunction against advertising new book releases in the middle of the night via notifications. I should be able to get cash compensation in court for that.
And my USB-C cable, once I plug it into my Android phone insists on randomly popping up an utterly inscrutible notification saying "you need to log in if you want to see notifications", or some such, and then when I do there is no notification to see. It was just random.
And Android Auto likes to give me two completely pointless notifications, one when I plug my phone into the car and one saying Android Auto is available. The first one I don't need a notification about because I just plugged in my phone. But more importantly, the second one is a lie. Android Auto MIGHT be available and it confirms nothing. The handshake may have been done wrong, so all it tells me is the thing I know already, which is that Android Auto is on the phone. But I might have to pull the plug and replug it to be properly connected. So the notification is worse than pointless and just floods my screen with stuff I don't care about that appears to need immediate attention. And then Android asks, as soon as I disconnect it, how my experience was. I always say "Bad" because part of my experience is getting asked that pesky message that I do not want and would happily say "never do this".
These all seem like technical problems, but they are not. They are reminders that we no longer control our lives, that companies can, at a whim, intrude into our lives with pointless rituals that whittle away our existence. I'm not being metaphorical when I say we need laws on this. I absolutely mean that if we don't write strong law on this, it will only get worse. Or we need to enforce the 4th Amendment on a theory, like Larry Lessig has effectively said in the past, that programmatic code is effectively a kind of government that binds us and our choices in life as surely as legal code does.
But what DO we get laws about? Having to login to use an operating system so they can track us better, know who we are and where we are at every moment. We need laws against such laws.
#marketing #notifications #android #ui #ux #settings #design #QualityOfLife #computers #LockScreen #permissions #law #legal #lawsuits #ClassAction #rights #HumanRights #BillOfRights #identity #intrusion #interruption #4thAmendment #government #code
-
Weird as it sounds, I think we need an actual law, like some kind of bill of rights, that says you can't notify me on my phone without offering me highly fine-tuned control of each kind of message.
Notifications intrude into my life. Sometimes my phone is on waiting for emergencies or other high-priority issues while I sleep. If a friend wakes me, I can have them dialed up or down in priority.
But Android is designed so Audible won't let me have control of my audiobooks in the lock screen without notifications turned on, yet once I've done that, Audible has no compunction against advertising new book releases in the middle of the night via notifications. I should be able to get cash compensation in court for that.
And my USB-C cable, once I plug it into my Android phone insists on randomly popping up an utterly inscrutible notification saying "you need to log in if you want to see notifications", or some such, and then when I do there is no notification to see. It was just random.
And Android Auto likes to give me two completely pointless notifications, one when I plug my phone into the car and one saying Android Auto is available. The first one I don't need a notification about because I just plugged in my phone. But more importantly, the second one is a lie. Android Auto MIGHT be available and it confirms nothing. The handshake may have been done wrong, so all it tells me is the thing I know already, which is that Android Auto is on the phone. But I might have to pull the plug and replug it to be properly connected. So the notification is worse than pointless and just floods my screen with stuff I don't care about that appears to need immediate attention. And then Android asks, as soon as I disconnect it, how my experience was. I always say "Bad" because part of my experience is getting asked that pesky message that I do not want and would happily say "never do this".
These all seem like technical problems, but they are not. They are reminders that we no longer control our lives, that companies can, at a whim, intrude into our lives with pointless rituals that whittle away our existence. I'm not being metaphorical when I say we need laws on this. I absolutely mean that if we don't write strong law on this, it will only get worse. Or we need to enforce the 4th Amendment on a theory, like Larry Lessig has effectively said in the past, that programmatic code is effectively a kind of government that binds us and our choices in life as surely as legal code does.
But what DO we get laws about? Having to login to use an operating system so they can track us better, know who we are and where we are at every moment. We need laws against such laws.
#marketing #notifications #android #ui #ux #settings #design #QualityOfLife #computers #LockScreen #permissions #law #legal #lawsuits #ClassAction #rights #HumanRights #BillOfRights #identity #intrusion #interruption #4thAmendment #government #code
-
Inconsistent access of local WIndows drive #permissions #2404 #files
-
Inconsistent access of local WIndows drive #permissions #2404 #files
-
Permission denied (public key) error i forgot to save the key when i created the Instance #server #permissions #2204 #oracle
-
Not letting me move or copy file to desktop #permissions #files
-
Not letting me move or copy file to desktop #permissions #files
-
But wait, there's more: Even if a Hubzilla channel, upon confirming your follow request, "follows" you back, it doesn't necessarily actually follow you back, as in, let your toots and boosts in.
Chances are that the Hubzilla channel uses its permissions system to keep your toots and boosts out. Replies are allowed. DMs are allowed. But anything that isn't either is kept out.
#FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Hubzilla #Permissions #Contacts -
HP OMEN 16 fan control not working on Ubuntu (ec_sys permission issue) #drivers #permissions #fan #temperature
-
How do I mount my 8TB hard as my Videos folder with rw permissions? #permissions #mount #harddrive
-
How do I mount my 8TB hard as my Videos folder with rw permissions? #permissions #mount #harddrive
-
How do I mount my 8TB hard as my Videos folder with rw permissions? #permissions #mount #harddrive
-
How do I mount my 8TB hard as my Videos folder with rw permissions? #permissions #mount #harddrive
-
How do I mount my 8TB hard as my Videos folder with rw permissions? #permissions #mount #harddrive
-
Node.js Brotli UAF, by @maitai:
https://blig.one/2026/03/29/nodejs-brotli-uaf.html
#nodejs #permissions #brotli #compression #security #claude #ai
-
Change ownership of a volume #permissions #volumecontrol #ownership
-
Simplified Permission Management for Unity #Permissionmanagement #Unity #Android #Ios #Mobile #Permissions #Api #Editortools #AssetStore
https://u3dn.com/packages/simplified-permission-management-for-unity-257289
-
Simplified Permission Management for Unity #Permissionmanagement #Unity #Android #Ios #Mobile #Permissions #Api #Editortools #AssetStore
https://u3dn.com/packages/simplified-permission-management-for-unity-257289
-
Simplified Permission Management for Unity #Permissionmanagement #Unity #Android #Ios #Mobile #Permissions #Api #Editortools #AssetStore
https://u3dn.com/packages/simplified-permission-management-for-unity-257289
-
Simplified Permission Management for Unity #Permissionmanagement #Unity #Android #Ios #Mobile #Permissions #Api #Editortools #AssetStore
https://u3dn.com/packages/simplified-permission-management-for-unity-257289
-
I think there should be app store guidelines that prohibit apps from having permissions prompts that make it unclear which permissions are required, for what, and that the control about the permissions is exclusively done via system prompts and settings.
In particular, this would prohibit:
* Asking for permissions randomly or preemptively. Only ask for permissions on initial setup and after explicit user request of a feature that requires or uses the permission.
* Showing an app-controlled permissions popup with an option to reject that will trigger a further system popup if the app popup is accepted.Here is a shitty example from Spotify.
The layout makes it look like this screen is asking me to give Spotify the permission. It isn't. It looks like tapping continue, the only obvious choice, will grant the permission. It won't.
The popup appears even though no functionality related to Bluetooth devices was requested.
It is not made clear what will happen when the permission is rejected. "Why do you need this?" implies that the user does in fact need the permission. They don't.
The statement that "You're in control" is not helpful. It directly contradicts "Why do I need this?". It also suggests that the only way to deny the permission is to disable it in system settings. You can just deny the permission in the system prompt. -
I think there should be app store guidelines that prohibit apps from having permissions prompts that make it unclear which permissions are required, for what, and that the control about the permissions is exclusively done via system prompts and settings.
In particular, this would prohibit:
* Asking for permissions randomly or preemptively. Only ask for permissions on initial setup and after explicit user request of a feature that requires or uses the permission.
* Showing an app-controlled permissions popup with an option to reject that will trigger a further system popup if the app popup is accepted.Here is a shitty example from Spotify.
The layout makes it look like this screen is asking me to give Spotify the permission. It isn't. It looks like tapping continue, the only obvious choice, will grant the permission. It won't.
The popup appears even though no functionality related to Bluetooth devices was requested.
It is not made clear what will happen when the permission is rejected. "Why do you need this?" implies that the user does in fact need the permission. They don't.
The statement that "You're in control" is not helpful. It directly contradicts "Why do I need this?". It also suggests that the only way to deny the permission is to disable it in system settings. You can just deny the permission in the system prompt. -
I think there should be app store guidelines that prohibit apps from having permissions prompts that make it unclear which permissions are required, for what, and that the control about the permissions is exclusively done via system prompts and settings.
In particular, this would prohibit:
* Asking for permissions randomly or preemptively. Only ask for permissions on initial setup and after explicit user request of a feature that requires or uses the permission.
* Showing an app-controlled permissions popup with an option to reject that will trigger a further system popup if the app popup is accepted.Here is a shitty example from Spotify.
The layout makes it look like this screen is asking me to give Spotify the permission. It isn't. It looks like tapping continue, the only obvious choice, will grant the permission. It won't.
The popup appears even though no functionality related to Bluetooth devices was requested.
It is not made clear what will happen when the permission is rejected. "Why do you need this?" implies that the user does in fact need the permission. They don't.
The statement that "You're in control" is not helpful. It directly contradicts "Why do I need this?". It also suggests that the only way to deny the permission is to disable it in system settings. You can just deny the permission in the system prompt. -
I think there should be app store guidelines that prohibit apps from having permissions prompts that make it unclear which permissions are required, for what, and that the control about the permissions is exclusively done via system prompts and settings.
In particular, this would prohibit:
* Asking for permissions randomly or preemptively. Only ask for permissions on initial setup and after explicit user request of a feature that requires or uses the permission.
* Showing an app-controlled permissions popup with an option to reject that will trigger a further system popup if the app popup is accepted.Here is a shitty example from Spotify.
The layout makes it look like this screen is asking me to give Spotify the permission. It isn't. It looks like tapping continue, the only obvious choice, will grant the permission. It won't.
The popup appears even though no functionality related to Bluetooth devices was requested.
It is not made clear what will happen when the permission is rejected. "Why do you need this?" implies that the user does in fact need the permission. They don't.
The statement that "You're in control" is not helpful. It directly contradicts "Why do I need this?". It also suggests that the only way to deny the permission is to disable it in system settings. You can just deny the permission in the system prompt. -
I think there should be app store guidelines that prohibit apps from having permissions prompts that make it unclear which permissions are required, for what, and that the control about the permissions is exclusively done via system prompts and settings.
In particular, this would prohibit:
* Asking for permissions randomly or preemptively. Only ask for permissions on initial setup and after explicit user request of a feature that requires or uses the permission.
* Showing an app-controlled permissions popup with an option to reject that will trigger a further system popup if the app popup is accepted.Here is a shitty example from Spotify.
The layout makes it look like this screen is asking me to give Spotify the permission. It isn't. It looks like tapping continue, the only obvious choice, will grant the permission. It won't.
The popup appears even though no functionality related to Bluetooth devices was requested.
It is not made clear what will happen when the permission is rejected. "Why do you need this?" implies that the user does in fact need the permission. They don't.
The statement that "You're in control" is not helpful. It directly contradicts "Why do I need this?". It also suggests that the only way to deny the permission is to disable it in system settings. You can just deny the permission in the system prompt. -
🎩 GitHub's latest #magic trick: a context-aware babysitter for #Claude #Code. Now you can pretend to be in control of #permissions while your code takes a #coffee #break ☕. Spoiler: #AI is the real boss here, folks! 😂
https://github.com/manuelschipper/nah/ #GitHub #HackerNews #ngated -
A context-aware permission guard for Claude Code
https://github.com/manuelschipper/nah/
#HackerNews #contextaware #permissions #ClaudeCode #security #GitHub #open-source
-
A context-aware permission guard for Claude Code
https://github.com/manuelschipper/nah/
#HackerNews #contextaware #permissions #ClaudeCode #security #GitHub #open-source
