Sex acts mentioned

Sensitive content

in reply to WestphalDenn

... ein aufblitzendes Messer im trüben Schein einer rostigen Straßenbeleuchtung könnte man sonst als Warnblinkleuchte vor der Gefahr eines Angriffes deuten ...

Das Lesen des Tatherganges im Urteil – schon vom 20.6.2024 – erzeugte bei mir ein Geschmäckle nach versuchten "Ehrenmord" und dass die Anstifter und wahren Täter unbehelligt bleiben!

Hier das originale Urteil des BGH:
juris.bundesgerichtshof.de/cgi…

@WestphalDenn

in reply to Civio

¿A qué se debe que aún no podamos acceder a los datos de todo el país?

Según el organismo competente del @mitecogob consolidar los datos es un "proceso complejo y largo".

El Tribunal de Cuentas lo achaca a la mala coordinación entre comunidades autónomas y Ministerio.

El resultado es que encontrarás datos de 2017 y 2018 para 28 provincias, los fuegos de 2019 en 20 regiones más, los incendios de 2020 en 11 territorios y los de 2021 en Badajoz, Córdoba, Granada y Soria.

in reply to Crypto News

Is there any chance we can encourage you to trend #NVIDIA when that's the company you mean, please? I know what their NASDAQ handle is, but #NVDA is much more widely known as the name of the screen reader we make and the #NVDA hashtag is very widely used for the screen reader. It will save both our communities polluting each other's feeds. If you'd like to find out more about the screen reader, our website is nvaccess.org/ - Thank you!

ODF wholesome encryption is the default password (symmetric) encryption mode in LibreOffice 24.8.

Supports AES-256-GCM and Argon2id.

LibreOffice 24.2/24.8 is required to open the encrypted files.

Disable: Tools > Options > Load/Save > General > ODF Format Version > 1.3 (drop down menu) > Apply > OK

AES: en.wikipedia.org/wiki/Advanced…
GCM: en.wikipedia.org/wiki/Galois/C…
Argon2: en.wikipedia.org/wiki/Argon2

Website: libreoffice.org
Mastodon: @libreoffice

#LibreOffice #Encryption #InfoSec #Privacy #E2EE

Just discovered that @protonprivacy have produced an excellent 60 page guide to IT Security for small business (and individuals!). It covers all sorts of software and network configuration. Not just about Proton products.

It's well worth a read even if you think you are upto speed as I guarantee you'll pick up a few nuggets.

proton.me/business/security-gu…

This entry was edited (1 year ago)

This gorgeous saffron spice tea popped into my mind today so I have made myself a pot. I first had it in a Kashmiri shop in South India. They serve this tea as you wander around. It was so so good so I asked what it was. Simply saffron, cardamom, cinnamon and cloves.

For a full Kashmiri experience you can add Karshmiri green tea leaves, organic dried rose petals and slivered almonds.

For a pot:
4 cloves, or more if they are small. Sometimes I use up to 10!
4 cardamom pods
2cm piece cinnamon
1 pinch strands of saffron

method
Crush the spices roughly in a mortar – no need to grind them at all, just to break them up a little. Place in a teapot, pour hot water over and allow to seep for 5 minutes. This will allow the saffron time to develop colour, and the flavour from the spices to emerge. Strain into a special teacup and sip slowly.

Aaaah! How relaxed you feel.

#food #FromTheArchives #WhatIAmCooking #WhatIAmEating #Vegetarian

in reply to mask-wearing, socially distant entity

1/2 This video is probably a good example of one which, aside from the "The TRUTH about the ADHD Superpower" heading, really doesn't need a screen reader to read the text. The text is captions of what is being said in the video - that is a great thing for those who are deaf or otherwise benefit from captions. For a screen reader user listening to text, in this particular case, they are generally better off listening to the dialog being spoken direclty
in reply to NV Access

2/3 NVDA CAN read the captions - press NVDA+r to have NVDA use OCR on the text. Note that NVDA has a setting to periodically refresh OCR. It's not perfect, but could be used in a situation like this (if that text WASN'T already being spoken for instance). By far the best option is for the video to ensure needed information is conveyed both visually and audibly to suit all audiences.
in reply to mask-wearing, socially distant entity

You're welcome :) In this particular case, a screen reader user can ignore that text - there are other videos where similar such text may be useful, and it may also depend on the platform the video is on as to how accessible that is - On some platforms you don't need to use OCR at all, just move NVDA's focus to the text as you start the video, and it will keep reading out new text as it changes.

Have a great weekend!

Our In-Process blog is out. Today we have a reminder of NVDA 2024.3, info on NVDA 2024.4 and our Beta / RC program, details of the upcoming SPEVI conference 2025 and a walkthrough of creating a portable copy and the highly anticipated change to the process which now creates a folder for you.

Read now at: nvaccess.org/post/in-process-5…

#NVDA #NVDAsr #ScreenReader #FOSS #Portability #Portable #Bea #PreRelease #News #Blog #Newsletter

I wrote this blog post in 2019 with the confidence that the WordPress starter theme I built would stand the test of time, no matter how many things changed in the WordPress core.

I'm happy to say that after upgrading to the latest WP version, including PHP, everything works as smoothly as it did on day one.

Blowing my own horn here, but this is a great testament to how a modular and lean source code can be resilient and reliable without needing constant maintenance.

alecaddd.com/embracing-wordpre…

So... any zlib/deflate experts here?

I have a weird issue: an APK (i.e. ZIP file) with deflate-compressed data which I cannot recreate using python + zlib, even with code that tries every possible combination of parameters (with the obvious exception of providing a predefined compression dictionary) instead of just varying the compression level.

One file's compressed data can be reproduced using strategy Z_FILTERED, but for all the other files I've tried the script doesn't return any matches (it works fine with the APK we built ourselves, which should have had identical compressed data as the build is supposed to be deterministic).

Anyone have any idea what's going on here?

Test code: gist.github.com/obfusk/d9d1223…

Original issue: github.com/enteraname74/SoulSe…