• 6 Posts
  • 23 Comments
Joined 1 year ago
cake
Cake day: June 22nd, 2023

help-circle

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




  • The conversion is not an issue, there are already multiple tools for that, including a browser plugin with auto refresh.

    However the tight integration with the editor, in this case neovim, is missing. At the bare minimum it should show the changed area curently being edited, ideally scroll with the editor scrolling like with common markdown extensions. Currently it just shows a static site that refreshs.










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




  • 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




  • 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:*

    1. I tested locally via ssh from the pi the connection via curl http://mylocalip:8081/ and it works, i get the html back
    2. 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.
    3. 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.


  • Quick Update:

    I’ve been evaluating the best options and decided to wait a few months, until more devices are out and the ones i am looking at become cheaper.

    I have decided for a proof of concept or intermediate solution by using the raspberry pi with openmediavault and 2x 2TB SSDs connected via USB, as well as SnapRaid to sync them. This should suffice for storage and test in shortterm. However i ran into an issue with the connection to OMV here:
    OMV not reachable

    My options for later:

    1. The Beelink S12 Pro with 16 GB of RAM and 512GB storage. Unfortunately this will be a limited option, as most sources state that 16Gb is the max for this model. (some say 32GB). However it is cheap, a good start and in the long run i could buy more powered by solar to create a highly available mini cluster via k3s.

    2. Morefine M9, slightly more expensive, but with a 1TB SSD and can be upgraded to 32GB for sure. Unfortunately it’s not directly available in my country, but i’ve found a reseller, who seems to have it under a new brand name.

    3. Passively Cooled Firewall appliance with no ssd or ram, also N100 or N305. Has good reviews on the common yputube channels, in the end more expensive, but better ports and 4x 2,5GbE. It sounds interesting, but its only sold via a chinese trading company on amazon.

    4. An older i3 1120g4 or something similar, which would allow me to use 64GB of RAM. Unfortunately i found literally no devices with it being sold at all.

    Generally i’d prefer 64GB and 6 to 8 Cores, but in the low power area that is tough to find. The N305 has 8 cores, but max 32GB RAM, the i3 allows 64GB but nothing is being sold, as for the N100 is cheap, but only 4 cores (might be sufficient, if i later extend to a mini cluster powered powered by solar), but also limited to 32GB.

    In general, nothing really ideal, so i hope that later this year either more devices drop in price or become available (like anything with the N300 would be interesting too).

    What do you guys think of these choices for a mini beginner budget low power homelab ? (the description becomes longer over time…)