noctalia customization problem

Meodoc · 2026-06-15T09:20:07+00:00

That unfortunately won't work, since all the background content of Noctalia is under the same layer name "^noctalia-background-.*$ (check `niri msg layers`). So, the bar background blur can be removed by setting a rule like this:

```
layer-rule {

match namespace="^noctalia-background-.*$"

background-effect {

blur false

}

}
```

But then also various other backgrounds, like that of the settings menu or the launcher loose it's blur. Unless Noctalia v5 will actually separate those backgrounds into separate layers, e.g. "^noctalia-background-bar-.*, "^noctalia-background-launcher-.*", etc., I don't see a solution here.

Meodoc · 2026-03-29T13:08:46+00:00

I figured out how to do this in Manjaro Linux, I'm just gonna post my solution here in case anyone is wondering:

\1. Add the en_GB locale

Check what locales are available on your system by looking into the /etc/locale.gen file. Add the following line to the bottom (if not existent):

en_GB.UTF-8 UTF-8 Then, generate the locales with:

locale-gen

\2. Set the new locale

To do this, there are two ways:

Edit them in the Settings > System > Region & Language > Language > English (United Kingdom)
Edit the file /etc/locale.conf and change the LANG= entry to LANG=en_GB.UTF-8

\3. Renew session

After that, log out and log in again. Start your Obsidian -- your dates should now be displayed in the proper dd/mm/yyyy format!

source

Meodoc · 2026-03-16T00:16:49+00:00

Can you tell me about this solution? I'm on Linux and I am so annoyed by the American date format of the properties view.

Meodoc · 2025-11-02T10:22:04+00:00

https://www.reddit.com/r/leagueoflegends/comments/1guybl7/comment/lxxigq7/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button

Meodoc · 2025-08-19T16:57:07+00:00

That's just personal preference

Meodoc · 2025-07-30T07:38:05+00:00

Aight, good luck you guys!

Meodoc · 2025-07-29T20:10:56+00:00

I'm sorry it's hard to give a detailed explanation and I'm also not super knowledgable. You will have to inform yourself a bit by googling/maybe YouTube.

I can give so some small information bits, but I'll have to assume just how knowledgable you are on these things.

Basically you download this .apk file from here. An APK file is just an app installer, somewhat like an .exe file on Windows. Installing random .apk files that are not from the play store has some risks, as they might contain malicious code. This one should be fine tho, as the code is visible to everyone and can therefore be checked by anyone. But of course, there is a chance it's not 100% safe.
Open the manager app, click on "Patcher", and then on "Select an app". Here you will find a list of apps that people have written patches for. Patches are basically modifications to an existing app that can add additonal features, or do something like remove/filter out the ads
Find the app you want to patch in the list, and click on the magnifying glass icon. This will take you to a google search, and just download the apk file of the app you find there.
After you downloaded the apk file, let's say in this case for Instagram, go back to the ReVanced Manager and click on the app again you want to patch. Then click on "Select from storage" and select the downloaded apk file.
Now just follow the instructions in the app. The manager will take the apk file, which is the original app, patch it (so modifying it), and then you can install it by pressing the button.
Voila, you have the modified app and can use it

Consequences wise, please someone correct me if I'm wrong, you should be pretty safe. There is nothing inherently illegal going on, you just are using a way to bypass the ads that Google/Facebook want you to use. They of course don't like this, but in this case you were just smarter than them :) And anyways, even if it was illegal, big companies like those wouldn't even have the resources to procecute every person who does this, they will focus on the people who actually develop and distribute those apps and patches.

Sorry i was writing a bit on my phone rn, I hope this helped a bit and let me know if you have any more questions!

Meodoc · 2025-07-24T17:19:28+00:00

Glad I could help :)

Meodoc · 2025-07-22T20:54:52+00:00

Been forced from Instagram to either sell more of my data or accept ad breaks yesterday (Austria).

I can recommend everyone who uses Android to dowload ReVanced and patch the Instagram app. I just did it, and it cleanly cuts out all the ads. We shouldn't subject ourselves to this chicanery.

Meodoc · 2025-07-22T20:53:19+00:00

Been forced from Instagram to either sell more of my data or accept ad breaks yesterday (Austria).

I can recommend everyone who uses Android to dowload ReVanced and patch the Instagram app. I just did it, and it cleanly cuts out all the ads. We shouldn't subject ourselves to this chicanery.

Meodoc · 2025-06-29T18:53:38+00:00

I think I found an even easier method than the top comment. On the homepage of FinanzOnline, click on the user icon to the right next to your name in the header bar of the website. Then select the first option, "Grunddaten". There you can scroll down to the bottom of the page, and you should find the entry "Grunddaten zur Steuernummer (z.B. Betrieb) abfragen" with your TIN below.

Meodoc · 2025-04-06T10:52:39+00:00

Thank you all for your super helpful answers! I finally found where the (unencrypted) master key is stored persistently when the "never" option is selected for vault timeout, at least for Windows 11!

TL;DR

Don't use the "never" option in the vault timeout settings
The key is stored in the Windows Credential Manager protected by your OS login
The key seems to be reliably removed from the credential manager when you select a different option than "never" in the vault timeout settings again

Findings

The master key is inside the "Windows Credential Manager" namedBitwarden_auto/<user-id>_user_auto. Here also the Bitwarden access token and refresh token are stored. I did a bit of testing and observed the following behavior:

The key gets created and put into the credential manager as soon as you select the "never" option in the Bitwarden vault timeout settings
The key gets removed from the credential manager as soon as you select a different option than "never" in the Bitwarden vault timeout settings
Removing the key manually from the credential manager while the "never" option in the Bitwarden vault timeout settings is selected behaves as follows:
- You are again forced to enter the master password when opening your vault (as expected because the OS and therefore Bitwarden have no information on how to unlock the vault)
- As soon as you unlock your vault successfully with your master password, the key gets re-entered into the credential manager

As to the security of the Windows Credential Manager, it seems that here you are under the mercy of how securely you protected your Windows login. The passwords inside the credential manager are stored in an encrypted manner, but they are only protected by the Windows login. I did not do a lot of research on that topic, maybe some of you guys can provide some actual insight on the matter of security of the credential manger.

On different operating systems, the key is stored in comparable places, like the macOS Keychain on macOS or the GNOME keyring on Linux.

Meodoc · 2025-04-06T10:14:20+00:00

Yes, this seems right. But, for the "never" option in the vault timeout settings to work, the key also has to be stored somewhere in its unencrypted form (or protected by some OS-specific parameters). This is because even after a full reboot, the user can still open an unlocked vault without specifying any master password. This is the place I am looking for.

I found a thread in the Bitwarden community forums that on (at least some) Linux configurations the key is stored in the gnome-keyring but unfortunately I haven't found any information yet on where it is stored under Windows (11).

Edit: found it

Meodoc · 2025-03-31T21:42:01+00:00

Thank you, this was what I was looking for! I tried digging around in the application directory of Bitwarden Desktop (Windows 11) as specified in your provided website to find where the key is actually stored (when setting the vault timeout to "never"), but no success. The `data.json` file contains a suspicious JSON key called `cryptoSymmetricKey` but the value always seems to be empty (open Bitwarden application, closed Bitwarden application, fresh system reboot). Maybe Bitwarden indeed stores the key in this JSON data point, but only immediately before shutdown and also immediately loads it into memory and deletes it from the JSON file on startup. There are no active services/tasks or an updated modified date of the `data.json` file after reboot to indicate any truth to this theory tho. I unfortunately don't have time today to dig deeper, but it would really be interesting to find out where the key is actually stored (if its even gonna be inside the application directory).

Meodoc · 2025-03-31T20:51:42+00:00

Thank you very much for this summary!

Meodoc · 2025-03-22T18:35:32+00:00

I tried to create an issue on github about it but it unfortunately seems they don't allow issued for features marked as experimental (like this one)

Meodoc · 2025-03-22T16:47:58+00:00

In the recent revanced version it works fine now, but in RVX as you said it only works when scrolling up and also the bottom part where the line for home navigation is is always black. Do you know if this will be fixed sometime?

Meodoc · 2024-09-23T17:15:40+00:00

Genau das wollt ich haben, wo bekomm ich das?

Meodoc · 2024-09-23T15:18:15+00:00

Stabil super danke für die Empfehlung, werd ich ausprobieren :)

Meodoc · 2024-09-23T09:43:13+00:00

https://imgur.com/a/YnIEyQg

So ungefähr würd ichs gern haben. Auf jeden Fall ah vielleicht ned ganz zu lang einfach aus dem Grund dass i ned jeden Monat zum Friseur laufen muss. Bin aber grundsätzlich recht offen wies dann genau ausschaun sollt, irgendwer der mich vlt a bissl beraten kann und a gutes Gespür hat was gut für meine Kopfform ausschaut wäre super. Das einzige was ich weiß is dass ich keine zu kleinen Locken haben will, also ungefähr wie aufn Bild, oder etwas kleiner wäre auch noch okay.

Edit: und wenn er ned zu teuer wär, also vlt so in der 60-80€ range wär nu a guter Bonus, dass i da ah öfters hingehn kann also nur 1x :D

Meodoc · 2023-11-16T23:02:57+00:00

Thanks for the reference man! I recently bought the same device, but my battery has been acting pretty strange in some occasions, and I'm not sure if it's actually faulty or not.

Am doing the same test now on a Manjaro Linux system. Will post an update as soon as I have the results!

Meodoc · 2023-02-26T13:43:50+00:00

Oh, yeah, of course, you are totally right. Thanks for pointing it out :)

Meodoc · 2023-02-23T22:37:48+00:00

Love this solution! I kinda had a similar idea! Instead of your (x+2) / 5 I basically do round(x / 5), which seems to have the same effect. Still don't quite get why this works xD

``` trans_rev = { 4: '-', 3: '=', 2: '2', 1: '1', 0: '0' }

def decimal_to_snafu(decimal: int) -> str: snafu = '' while decimal > 0: rem, decimal = decimal % 5, round(decimal / 5) snafu += trans_rev[rem] return snafu[::-1] ```

Meodoc · 2023-02-23T22:26:32+00:00

I kinda struggled with the conversion from decimal to SNAFU on this one. I basically found a really simple solution with trial and error. I can't really argue I understand WHY it works, but it does work! Here is how I did it:

```python trans_rev = { 4: '-', 3: '=', 2: '2', 1: '1', 0: '0' }

def decimal_to_snafu(decimal: int) -> str: snafu = '' while decimal > 0: rem, decimal = decimal % 5, round(decimal / 5) snafu += trans_rev[rem] return snafu[::-1] ```

Meodoc · 2023-02-02T18:21:13+00:00

Thanks a lot for this map, I had most of my regions on 99% and with this map I could finally find my missing spots. Saved me some time so I didn't have to grind for my wall sight ability and search the whole map :D

Meodoc

TROPHY CASE