superhighway84
searxng
Our great sponsors
superhighway84 | searxng | |
---|---|---|
40 | 117 | |
664 | 6,742 | |
- | 5.7% | |
5.6 | 9.8 | |
8 days ago | 7 days ago | |
Go | Python | |
GNU General Public License v3.0 only | GNU Affero General Public License v3.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
superhighway84
-
Would we still create Nebula today?
https://github.com/gravitl/netmaker
Honorable mention:
SuperHighway84 - more of a Usenet-inspired darknet, but I love the concept + the author's personal website:
-
Open source P2P alternative to Slack and Discord built on Tor and IPFS
While I do like the idea behind a P2P E2EE chat, I believe that unless you're willing to invest heavily into OrbitDB and IPFS, this project will stay niche at best.
The performance issues that come along with running OrbitDB/IPFS on a machine, let alone a mobile device, are still significant unfortunately. Adding Electron on top of what is already a heavy-weight application is probably going to make people's devices go brrrrr all the time. Not only that, but I would argue that for instant communication this stack might not be the best idea in terms of performance in first place.
Besides, the way IPFS has been (and still keeps) changing their dozens of libraries doesn't make development particularly smooth either. OrbitDB is always behind the latest IPFS version due to all these changes that are being introduced. Hence unless you're planning to allocate developer time on these two things as well, my guess is that you probably won't have too much fun with your back-end.
The integration with Tor is another thing that will likely be a time drain for developers, as other people here already pointed out, and that will lead to even more performance issues down the line.
Don't get me wrong, I really like the idea behind this project. However, I feel like the aspirations are unrealisticly high and the actual outcome might be realtively frustrating for the average end-user. Having that said, I would love my gut feeling to be proven wrong!
Disclaimer: I'm the developer of Superhighway84 (https://en.wikipedia.org/wiki/InterPlanetary_File_System#App..., https://github.com/mrusme/superhighway84), a USENET-inspired, uncensorable, decentralized internet discussion system running on IPFS & OrbitDB.
-
Ask HN: Is it time to resurrect a Usenet clone?
Someone created a Usenet-like thing on IPFS. https://github.com/mrusme/superhighway84
It's kind of dead. IIRC the dev put that on the back burner in favor of a new BBS-like app. https://github.com/mrusme/neonmodem
-
We need a community archiving effort for YouTube channels. What's most crucial to protect and how do we get organised?
SuperHighway84 - Is this handy for organization? I like the usenet-style where it sorts itself if people use proper newsgroup names. If people used a 'youtube.channelname' format at least people could maybe scroll down to channels/videos people are talking about.
-
How do you/we share the stuff we hoard so those looking for stuff find it?
In my mind something like superhighway84 would be a better platform, then it's automatically organizing itself to some degree if people post in appropriate newsgroups. People looking for lost youtubers could post in youtube.channelName. That person looking for old VCDs & screeners could post in vcds.screeners.
-
10+ years of Sumo GONE
I like the idea of something like SuperHighway84 for talking about our collections. We could make one called YoutubeGraveyard or something. There's also r/DHExchange
-
Reminder: Libgen is also hosted on the IPFS network here, which is decentralized and therefore much harder to take down
Superhighway84 is like a decentralized usenet/forum that runs off of ipfs.
-
Any DataBase-type project built on IPFS?
superhighway84 uses orbitdb.
-
IPFS has an indexing problem. The search engines suck.
SuperHighway84 is a neat option for that.
searxng
- So I deployed Whoogle on my NAS....
-
Your privacy is optional
I have switched over to using DuckDuckGo as my main search engine, but I may set up SearNGX behind a VPN in the future.
-
Welcome to mwmbl, the free, open-source and non-profit search engine
For my first search (current work problem) "rust json diff" it only found 6 links, only one of which was a rust crate. Unfortunate.
Second Search: "black sabbath sleeping village lyrics" only gave 2 results, only one of which was correct.
Also the repo is missing the SearXNG[1] search engine.
-
Searx is no longer maintained
From the README,
> What is the difference between searx and SearxNG?
> TL;DR: SearXNG is for users that want more features and bugs getting fixed quicker. If you prefer a minimalist software and stable experience, use searx.
> SearxNG is a fork of searx, created by a former maintainer of searx. The fork was created because the majority of the maintainers at the time did not find the new proposed features privacy respecting enough. The most significant issue is with engine metrics.
> Searx is built for privacy conscious users. It comes with a unique set of challenges. One of the problems we face is that users rather not report bugs, because they do not want to publicly share what engines they use or what search query triggered a problem. It is a challenge we accepted.
> The new metrics feature collects more information to make engine maintenance easier. We could have had better and more error reports to benefit searx maintainers. However, we believe that the users of searx must come first, not the software. We are willing to compromise on the lack of issue reports to avoid violating the privacy of users.
> Furthermore, SearxNG is under heavy refactoring and dependencies are constantly updated, even if it is unnecessary. It increases the risk of introducing regressions. In searx we strive for stability, rather than moving fast and breaking things.
- Google - But On a Subset of the Internet
-
Try a Marxist-Leninist search engine - is it useful?
Hmm if you're good at computer shit you could put up a custom Searxng instance and configure it to only search a certain subset of sources/websites. It'd be self-hosted so no google, you just need a domain and a vps to host it on.
-
Does Firefox have the same results as Google chrome?
SearXNG
-
Marginalia.nu API
> SearXNG supports marginalia but uses the demo key.
Yeah. Looking over the GitHub issue you raised about it, they didn't seem to really understand the problem before they closed it.
I've just asked a question about it (same thing, different wording), which might work:
- Best alternative to duckduckgo?
-
Why Firefox doesn't launch their own Private search engine ?
- SearXNG - It aggregates results from various search services and databases. I personally find these two instances to be really good options but there are others if you search the "instance list": searx.be and baresearch.org
What are some alternatives?
Searx - Privacy-respecting metasearch engine
whoogle-search - A self-hosted, ad-free, privacy-respecting metasearch engine
searx-instances - SearXNG instances list
searx - Privacy-respecting metasearch engine [Moved to: https://github.com/searx/searx]
elasticsearch-py - Official Python client for Elasticsearch
Yacy - Distributed Peer-to-Peer Web Search Engine and Intranet Search Appliance
librex - Framework and javascript free privacy respecting meta search engine
tribler - Privacy enhanced BitTorrent client with P2P content discovery
rathole - A lightweight and high-performance reverse proxy for NAT traversal, written in Rust. An alternative to frp and ngrok.
searxng - SearXNG is a free internet metasearch engine which aggregates results from various search services and databases. Users are neither tracked nor profiled. This is a fork of SearXNG used by searx.tiekoetter.com
algorithms - Minimal examples of data structures and algorithms in Python
elasticsearch-dsl-py - High level Python client for Elasticsearch