blog

commit

e0fe0c0bc5aa0436141a8b654d78b0a2ee29372d

parent

13c8939f981724e554fa3cd47775b59d6e20d585

Author

Tobias Bengfort <tobias.bengfort@posteo.de>

Date

2025-12-01 19:20

tweaks and typos

Diffstat

3 files changed, 4 insertions, 6 deletions

diff --git a/_content/posts/2024-03-22-beyond-gdpr/index.md b/_content/posts/2024-03-22-beyond-gdpr/index.md

@@ -157,7 +157,7 @@ such as Google and Facebook certainly played a role. But I also blame the EU.
  157   157 With the benefit of hindsight, I hope that they can come up with a better
  158   158 communication strategy next time around.
  159   159 
  160    -1 [^2]: I understand that cookie banners are often actually required by GDPR, but
   -1   160 [^2]: I understand that cookie banners are not actually required by GDPR, but
  161   161 	by the [ePrivacy directive](https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A02002L0058-20091219).
  162   162 	But the point that the underlying principles got lost somewhere still holds.
  163   163 

diff --git a/_content/posts/2025-07-18-hdr/index.md b/_content/posts/2025-07-18-hdr/index.md

@@ -110,7 +110,7 @@ only take power away from users, it would also disregard the huge influence
  110   110 that viewing conditions have on human sight. If anything, we need more options
  111   111 for personalization, not less.
  112   112 
  113    -1 I am not entirly sure if this is really what the authors of that specification
   -1   113 I am not entirely sure if this is really what the authors of that specification
  114   114 had in mind though.
  115   115 
  116   116 ## Scene-to-Scene differences

diff --git a/_content/posts/2025-10-11-terminal-sandbox/index.md b/_content/posts/2025-10-11-terminal-sandbox/index.md

@@ -57,7 +57,7 @@ I must admit that I didn't understand `run0` when it was first announced. But
   57    57 now I really see the appeal of a privilege escalation with user interaction
   58    58 that does not depend on a configuration file in the current mount namespace.[^2]
   59    59 
   60    -1 Of course, a more low-tech option is to add just launch an unsandboxed
   -1    60 Of course, a more low-tech option is to add an option to launch an unsandboxed
   61    61 terminal.
   62    62 
   63    63 [^2]: Another, simpler implementation of this concept can be found in
@@ -86,7 +86,7 @@ I rarely use portals from inside the terminal.
   86    86 The system's input and output rely on three main protocols:
   87    87 
   88    88 -	Wayland for video, typically via the socket `$XDG_RUNTIME_DIR/wayland-0`
   89    -1 -	Pipewire for audio, typically via the sockets `$XDG_RUNTIME_DIR/pipewire-0`
   -1    89 -	Pipewire for audio, typically via the socket `$XDG_RUNTIME_DIR/pipewire-0` or `$XDG_RUNTIME_DIR/pulse/`
   90    90 -	AT-SPI for accessibility, typically via the sockets in `$XDG_RUNTIME_DIR/at-spi`
   91    91 
   92    92 Unfortunately, these protocols do not clearly separate between clients
@@ -186,7 +186,6 @@ tmpfs $XDG_RUNTIME_DIR
  186   186 
  187   187 bind $HOME
  188   188 ro-bind-try $HOME/.config
  189    -1 ro-bind-try $HOME/.dotfiles
  190   189 ro-bind-try $HOME/.local/bin
  191   190 
  192   191 share-net
@@ -201,7 +200,6 @@ setenv XDG_SESSION_TYPE
  201   200 
  202   201 ro-bind-try $XDG_RUNTIME_DIR/pipewire-0
  203   202 
  204    -1 setenv DBUS_SESSION_BUS_ADDRESS
  205   203 dbus-talk org.freedesktop.portal.Desktop
  206   204 dbus-talk org.freedesktop.portal.Documents
  207   205