That sounds like an interesting idea, I’ll test that out, thanks!

I thought about this solution, as it is the “cleanest”, however I need on total 4 firefox derivatives. Unfortunately, when looking deeply into the options, i haven’t found 4 that are similarly trustworthy, well maintained etc. Also i have my firefox config fully figured out, it works and is as private as i want them, without some maintainer forcing their opinion on my use cases. Plain firefox is the easiest to configure, as it’s like a blank start. However i might be wrong here and am open to suggestions :D

Unfortunately that is not what I am looking for. I am already using named profiles. Like i stated in my original post as well as my answers below, this only works from Inside Firefox, however from the operating system pov it is still treated as the same application. Which means:

a) When i share the work profile, i also share all other profiles, as they are all Firefox b) When I quick access firefox via spotlight, i end up at the nearest, random profile / instance of firefox. c) There is no way to differentiate the profiles on an application level. d) I can not assign the instances to different desktops, as they are all Firefox.

It looks very interesting!

But I don’t see the unique selling point of it compared to alacritty and kitty, besides web-enabled. Is there anything that it does better than these 2?

That looks promising, especially since my current status bar is also just a collection of shell scripts, so that might be easier to switch

Thanks! That looks exactly like what I was looking for. I hope it works as promising as it looks :)

Thanks, that was a very interesting read!

I forgot one essential tool, where I need a recommendation for: spotlight. I use it to switch quickly between applications or to folders. Keyboard shortcut, first letter of the application name and enter… I know there are solutions, but I only heard from Ubuntu, which I don’t want. Anything simple and fast you can recommend?

Thank you everyone for all your suggestions! I’ll quickly try to summarize them for myself. So what you suggest is:

Operating Systems:

• NixOs
• Debian 12
• ElementaryOS
• mint
• PopOs
• EndevourOS
• Fedora
• arch
• Opensuse
• Novara

Tiling Window Manager:

Recomended to use something based on wayland.

• hyprland (can be configured from file, good compatibility with nix)
• sway (proposed with Debian, multiple suggestions, config via file as well, good for custom keybindings, already options for sway in nixos)
• i3
• bspwm
• KDE Plasma
• dwm / dwl

Status Bar:

• swaybar (in case of using sway)
• waybar (when using wayland)
• eww
• ags
• KDE neon

Package Managers:

• flatpack
• brew (is this already stable enough?)
• Nix (obvious choice if nix os chosen)
• snap
• (pacman if arch)
• integrated one

Packages:

• together with wayland alacritty or kitty
• foot
• Yakuake
• suckless

At the moment I am trying to avoid anything where RedHat is involved. Not because of the recent controversy, but simply IBM is known to kill their software solutions on a whim. (although i still use ansible), so Fedora is unfortunately out (again, no judging on how great it is). I’ve been quite interested in EndevourOS, so that might be fun to try out. Debian for the desktop probably not right now. I’m running it on servers for stability, but for a desktop environment, i prefer having more recent packages (e.g. neovim). The “sales pitch” for Mint sounded pretty interesting as well. However i’ll give NixOs a try first, simply because it was mentioned very often, same with sway.

Based on this i’ll try out these combinations first:

1. NixOs with sway and eww
2. NixOs with hyprland and waybar
3. NixOs with dwl and ?

If this does not satisfy, i’ll look into endevourOS and mint, but that might require some Ansible I assume.

Thank you very much!

It might have. I’ve tried nixos on a mini PC meant as a home server, so most configuration is done via SSH and users don’t change (much), I might have accidently activate it while trying nixos out.

Making users unable to login is a bit of an odd (side?) Effect, but maybe I’m not understanding the purpose of this option correctly. I’ll stay away from it for now :D

I don’t know how the code is currently working, but I like this feature idea and would suggest to start very simple and proceed from there.

For example you could: a) Make a list of communities that are siblings with their id and instance b) add a toggle to view sister community posts yes /no c) query all communities, list the last x posts from each with time constraints, e.g. not older than 1 day or hour depending on the community post frequency d) list them sorted by time of x , depending on what was chosen

The biggest issue I see with this simple approach, besides others, is that different communities are different in terms of activity / post frequency. So ideally the better, but more effort, way would be to let each community instance communicate their posts themselves via a query with activity metric parameters. Basically the amount of returned posts would depend on common parameters set by the most active instance.

It’s not yet thought out, but just getting an mvp started and test the waters would probably be better than having it perfect right away while working on it for months

The issue was much more straightforward than i thought. It seems sometimes thinking of too complex issues will hinder finding the easiest cause - the local forewall on the pi was blocking it / had no explcite allow.

To check i did: sudo ufw status verbose

There was only port 22

I added the new port as Allow Port 8081: sudo ufw allow 8081

And it works now! Thanks for all the tipps that pointed me in the right direction!

Thanks for the hints, this definitely helped, however it did not solve the issue.

What i did:

1. I changed via omv-firstaid the omv port from 80 to 8081.
2. I confirmed with ss -ltn that this change was successful and i see the listening port 80 vanished, while this now popped up:

State Recv-Q Send-Q Local Address:Port Peer Address:Port

LISTEN 0 511 0.0.0.0:8081 0.0.0.0:*

3. I tested locally via ssh from the pi the connection via curl http://mylocalip:8081/ and it works, i get the html back
4. I tested from my laptop (connected to my router via WiFi, where the raspberry is meshed into via the repeater in between) and i still get the timeout.
5. I tried tunneling again via ssh ssh -L 8081:localhost:8081 pi@raspberrypi.local and i did not get any errors this time. However when i open the local url in the browser i get a connection reset and my terminal shows me channel 3: open failed: administratively prohibited: open failed. However this just says that TcPForwarding is disabled, which is fine, so that tunneling issue should not be the main problem, i assume.

The jbod idea sounds good to explore further, as it tha home server and storage would be separated. However it would add an additional device to the power bill.

However i don’t need the full amount of all disks at all times. If i’d want to unplug via shell script, i’d need to plug it manually in person back in for storing things. I actually do not need it running all the time, as the home server ssd can cache most of what i need recently in access. The jbod is then more an archive.

i’m mainly looking for a way to power down the inexpensive hdd’s. I could use the raspberry pi as the jbod controller, but it does not properly support wake on lan, so thats also not an option