• 0 Posts
  • 46 Comments
Joined 2 years ago
cake
Cake day: June 18th, 2023

help-circle



  • One of the things that can get annoying about searxng is that often search engines will rate limit if a lot of people are using one searxng instance. Maybe a “federated” approach would be, if results are rate limited -> send query to another trusted searx instance -> receive the results and send back to user. That way, people can stick to their favorite searxng instance without having to manually change their instance if the search engines were rate limiting.


  • One of the things that can get annoying about searxng is that often search engines will rate limit if a lot of people are using one searxng instance. Maybe a “federated” approach would be, if results are rate limited -> send query to another trusted searx instance -> receive the results and send back to user. That way, people can stick to their favorite searxng instance without having to manually change their instance if the search engines were rate limiting.







  • aldalire@lemmy.dbzer0.comtoSelfhosted@lemmy.worldStarting from zero
    link
    fedilink
    English
    arrow-up
    2
    arrow-down
    1
    ·
    1 year ago

    Recommend doing a jellyfin server with an *arr stack! Prowlarr, radarr, sonarr, plus qbittorrent. Bonus if you can integrate i2p in there so you don’t have to rely on a VPN :)

    there’s also Nextcloud AIO docker. I use it to sync my photos and escape Apple’s 5gb max free-tier backup

    Maybe add some assorted services like an invidious instance, Searxng instance?

    Welcome to the self hosting rabbit hole!


  • aldalire@lemmy.dbzer0.comtoProgrammer Humor@lemmy.ml:3{:3|:3&};:3
    link
    fedilink
    English
    arrow-up
    0
    ·
    edit-2
    1 year ago

    Replace “:” with “a” you get

    a() a a&; a

    Reformatting

    a() {

    a | a &

    };

    a

    So it creates a function, a, which what it does is it calls itself and pipes its output to itself (the a | a). The ampersand means that this will run entirely in the background. Then, to initiate things, the command calls a (in the last line)

    So, there will be exponentially be many recursive calls to a, which will eventually deplete your stack and set your pc on fire