• 4 Posts
  • 329 Comments
Joined 1 year ago
cake
Cake day: April 27th, 2024

help-circle

  • I don’t like that it’s not open source, and there are opt-in AI features, but I can highly, highly recommend Kagi from a pure search result standpoint, and one of the only alternatives with their own search index.

    (Give it a try, they’ve apparently just opened up their search for users without an account to try it out.)

    Almost all the slop websites aren’t even shown (or put in a “Listicles” section where they can be accessed, but are not intrusive and do not look like proper results, and you can prioritize/deprioritize sites (for example, I have gituib/reddit/stackoverflow to always show on top, quora and pinterest to never show at all).

    Oh, and they have a fediverse “lens” which actually manages to reliably search Lemmy.

    This doesn’t really address the future of crawling, just the “Google has gone to shit” part 😄






  • Actual answer for 3:

    • put jellyfin behind a proper reverse proxy. Ideally on a separate host / hardware firewall, but nginx on the same host works fine as well.
    • create subdomain, let’s say sub.yourdomain.com
    • forward traffic, for that subdomain ONLY, to jellyfin in your reverse proxy config
    • tell your relatives to put sub.yourdomain.com into their jellyfin app

    All the fear-mongering about exposing jellyfin to the internet I have seen on here boils down to either

    • “port forwarding is a bad idea!!”, which yes, don’t do that. The above is not that. Or
    • “people / bots who know your IP can get jellyfin to work as a 1-bit oracle, telling you if a specific media file exists on your disk” which is a) not an indication for something illegal, and b) prevented by the described reverse proxy setup insofar as the bot needs to know the exact subdomain (and any worthwhile domain-provider will not let bots walk your DNS zone).

    (Not saying YOU say that; just preempting the usual folklore typically commented whenever someone suggests hosting jellyfin publicly accessible)




  • Neovim, because I wanted something that would not just disappear.

    I never really got along with VSCode, opting for Atom instead. Microsoft bought GitHub, which owned Atom, and promptly discontinued it.

    Nvim has such an active community (and no “owner”) that I’m certain that this won’t happen again. At the same time, the plugin system is so flexible that I’m also certain that I will never miss out on any shiny new features.

    Over the years, my config has matured, and is mine. The thought of going back to an editor, any editor, less flexible in its configuration than nvim is just… an absolute “no”.

    It’s a steep learning curve, but well worth it.