Chrome crashes with "FD ownership violation" and exit_code=133 #permissions #googlechrome

https://askubuntu.com/q/1567041/612

Denied write right to files that should be accessable #permissions #samba #php

https://askubuntu.com/q/1567040/612

PCSX2 BIOS Not Detecting on Ubuntu After Installation #permissions

https://askubuntu.com/q/1566725/612

• 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.

• 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.

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 👍

Title: P2: Doas instead of sudo [2025-05-04 Sun]

♲ #dailyreport #linux #administration #permissions #secops #sudo #doas #network #bash #proc

Title: P1: Doas instead of sudo [2025-05-04 Sun]

permit setenv { WAYLAND_DISPLAY XDG_RUNTIME_DIR } nopass g
as ff
doas -u ff firefox
-----------------------------------------------------
With help of AI I have written a simple bash scrippt that
output average network bandwidth by reading directly
from /proc/net/dev

I think 70 lines is better than some special app with
writing output parser for it. #dailyreport #linux #administration #permissions #secops #sudo #doas #network #bash #proc

Title: P0: Doas instead of sudo [2025-05-04 Sun]

#sudo #doas #network #bash #proc
Sudo command is overburden, I switched to Doas tool from
FreeBSD project that lighter by weight. I don't use SU
command, because it require PAM framework, that I don't
use.

Before:
larry ALL=(ff) NOPASSWD: ALL
sudo --preserve-env=WAYLAND_DISPLAY,XDG_RUNTIME_DIR -u ff
firefox

After: #sudo #doas #network #bash #proc #dailyreport #linux #administration #permissions #secops #sudo #doas #network #bash #proc

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