In case you’re interested in (co-)moderating any of the communities that I created, you’re welcome to message me.

I also have the account @Novocirab@jlai.lu. Furthermore, I own the account @daswetter@feddit.org, which I hope to make a small bot out of in the future.

  • 9 Posts
  • 37 Comments
Joined 5 months ago
cake
Cake day: February 27th, 2025

help-circle

  • I didn’t know about the web interfaces of Invidious instances. Definitey looks cool, and this redicrect domain is handy to quickly find a working instance.

    Still, FreeTube has a couple of major advantages. One is that even if your go-to Invidious instance becomes unusable, your local FreeTube configuration (subscriptions, blocks, ricings, you name it) remains 100% in effect, because FreeTube just picks a different instance. Even when Google again makes all Invidious instances dysfunctional, FreeTube may still be usable by accessing YouTube directly. Also, FreeTube likely has A LOT more options—the settings page is quite sizeable. Finally, I find it increasingly nice that it’s a standalone client separate from your browser. It makes it more deliberate to start watching videos, so that I’m less likely to go on senseless watching sprees; and conversely, when I’m watching useful videos, I’m less likely to interrupt them by going to some irrelevant website.



  • Novocirab@feddit.orgtoSelfhosted@lemmy.worldGood mini PC?
    link
    fedilink
    English
    arrow-up
    7
    ·
    edit-2
    21 days ago

    What hardware do you currently use and what software do you intend to run on the new machine? And what’s your budget situation?

    In any case, I would always recommend to buy used or refurbished hardware. Even if it’s not necessary financially, it’s better for the environment.









  • Rather than running a Tor relay, running a simple Tor bridge (e.g. via the browser add-on Snowflake as suggested by @ryokimball@infosec.pub) is probably the best thing to do with one’s home hardware.

    Actual relays must suffice certain requirements, according to the Tor project:

    Requirements for Tor relays depend on the type of relay and the bandwidth they provide. ==== Bandwidth and Connections ====

    A non-exit relay should be able to handle at least 7000 concurrent connections. This can overwhelm consumer-level routers. If you run the Tor relay from a server (virtual or dedicated) in a data center you will be fine. If you run it behind a consumer-level router at home you will have to try and see if your home router can handle it or if it starts failing. Fast exit relays (>=100 Mbit/s) usually have to handle a lot more concurrent connections (>100k).

    It is recommended that a relay have at least 16 Mbit/s (Mbps) upload bandwidth and 16 Mbit/s (Mbps) download bandwidth available for Tor. More is better. The minimum requirements for a relay are 10 Mbit/s (Mbps). If you have less than 10 Mbit/s but at least 1 Mbit/s we recommend you run a [/wiki/doc/PluggableTransports/obfs4proxy bridge with obfs4 support]. If you do not know your bandwidth you can use http://beta.speedtest.net/ to measure it.

    As for exit relays aka exit nodes, the obligatory advice is of course to not run them at all unless you know exactly what you are doing both legally and technically, and probably only if you’re a foundation or something.






  • Novocirab@feddit.orgtoSelfhosted@lemmy.worldNAS Power Consumption
    link
    fedilink
    English
    arrow-up
    6
    ·
    edit-2
    1 month ago

    Some local libraries (e.g. in Heidelberg) or ecological initiatives lend devices to measure electricity consumption at the power plug. In particular, this is useful to measure other appliances as well.

    Specifically for computers, they probably have some means to tell you their own consumption, but they may not be accurate or complete and will most certainly omit any peripherals, e.g. external hard drives.







  • For a simple distraction-free control via Linux’s command line, you can install mpg123 and add the following script files to /usr/bin/ or /usr/local/bin/:

    /usr/local/bin/soma:

    #! /usr/bin/bash
    kill $(pgrep mpg123)
    mpg123 -@ http://somafm.com/nossl/$1.pls
    

    /usr/local/bin/somaoff:

    #! /usr/bin/bash
    kill $(pgrep mpg123)
    

    Make them executable for everyone by running sudo chmod a+x /usr/local/bin/soma /usr/local/bin/somaoff.

    You can now run from your console (or from KRunner on KDE, or via :sh from within helix):

    # Tune into station "Lush"
    soma lush 
    # Turn Soma off
    somaoff
    

    Works fine from a tty as well, even with bluetooth on my OpenSUSE at least.

    The specific station names to enter after soma are the ones in the URL of each station’s webpage, e.g. “folkfwd” for Folk Forward, as its URL is https://somafm.com/folkfwd/.