If you learned today about LibreY, why don't you provide a link for others? π
I am sure you are not the only one, who didn't know about it
this post was submitted on 11 Feb 2024
46 points (97.9% liked)
Selfhosted
40173 readers
661 users here now
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (donβt cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 1 year ago
MODERATORS
you're right, thanks for posting it yourself! I'm a newbie in the selfhosting world, so I thought that LibreY was "famous", but I was wrong!
Never assume anyone ever knows what you're talking about. It may seem like you're talking to people here who know more than you, but everyone has a different bucket of knowledge.
Self-hosting, by it's nature of using a lot of OSS, means there's a LOT of discovery here.
You're effectively addressing the entire world here - you never know who is here for the first time.
This is college level writing 101 stuff - the first time you mention something, you footnote a reference. Today that equivalent is a link.
I try to always link to things we're talking about, except for really big stuff (I'm not linking to Google.com, but maybe to a specific app or feature somewhere within Google).
I like SearXNG, I pipe it through a gluetun vpn tunnel to mix up my traffic with others. I turn off google and use a !g bang when really necessary. One of the killer features is setting up blacklists for content farms (see config file) which has helped my dev searches immensly, also bye fandom etc.
I love me a no-js, simple search engine π
Iβve only ever self-hosted SearxNG but i wanna try out LibreY. As for who gets rate-linited less, if you self host for yourself plus some friends iβd be surprised if you have Google rate limiting your searches. I didnβt run a problem with mine anyways. I like the βtorrentsβ feature of LibreY tho. I might self host and report back.
Self hosted: I don't know how I wpuld get others to use it aka more fingerprintable
Publzic: I haven't found an Εnstance that I felt was trustworthy, I am very open to recomendations
New Lemmy Post: LibreY vs SearXNG, which one do you suggest and why? (https://lemmy.world/post/11822215)
Tagging: #SelfHosted
(Replying in the OP of this thread (NOT THIS BOT!) will appear as a comment in the lemmy discussion.)
I am a FOSS bot. Check my README: https://github.com/db0/lemmy-tagginator/blob/main/README.md
LibreY's "Framework and JS free" approach is an anti-feature as far as I'm concerned. If you really don't like those for some reason then sure, but I personally prefer getting a nicer UX with a bit of JS.
I don't think it makes sense to self-host these services, unless you plan to open it up for everyone.
Why? The public instances are heavily overloaded, isn't a private instance faster?
Many use SearXNG to get less personalized search and tracking. If hundreds of users appear as one user for the search engine then both tracking and personalization of the results suffer.
Hm, I would think users could get good value out grouping search subject and selecting the best engines for their need, and receive a good spread of results from a single search.
..also, our upcoming swarm of personal AI's might benefit from such a selfhosted search service.
The main goal of these projects (SearxNG, Piped, Invidious, Nitter...) is to make it way harder to track users by having thousands of users make requests from one single place. If you host this service just for yourself... you'd get the same tracking as using the service itself.
Self-hosting just for yourself damages the community a bit because your data will not be used to confuse Google and the other guys.
That's a goal, but it's hardly the only goal.
My goal is to get a synthesis of search results across multiple engines while eliminating tracking URLs and other garbage. In short it's a better UX for me first and foremost, and self-hosting allows me to customize that experience and also own uptime/availability. Privacy (through elimination of cookies and browser fingerprinting) is just a convenient side effect.
That said, on the topic of privacy, it's absolutely false to say that by self-hosting you get the same effect as using the engines directly. Intermediating my access to those search engines means things like cookies and fingerprinting cannot be used to link my search history to my browsing activity.
Furthermore, in my case I host SearX on a VPS that's independent of my broadband connection which means even IP can't be used to correlate my activity.
Probably stupid question: let's say I selfhost searxng only for myself: google & Co can track all my searches, but doesn't they pair all the data to the IP of my server? And because of this, they will not be able to show personalized ads to me, using my laptop. Is this wrong?
If the public IP is same, they can serve the same ads.
And what if the server has a static IP address?
Doesn't matter. They can still serve you ads.
How is this possible? I mean, how can they connect the searches from the ip of the server with your laptop's ip?
If the public IP is same, they will only see that.
They only see your public IP address (ie your router), so all devices on the private side will appear to be the same source.
So, if your laptop and your server (and anyone else at the same location) are connected to the internet via the same router, then, you're the same source.