Hi everyone.
I've just discovered whoogle through the many quotes from @SGS.
I've been testing it for a few days on Android, via www.whoogle.click
Perhaps this is the reason for this unexpected behaviour or perhaps I have misunderstood the principle of whoogle.
Take a look at the screenshot...
This is the first time it's happened and when you refresh the page it disappears, then reappears on another refresh.
What do you think?
(off topic: Thank DeepL)
yep, I thought so.
It confirms what I suspected.
This online version seems to take a few liberties with Whoogle's original philosophy.
I'll see if there's a port for Android.
Thank you for sharing your expérience.
I have to guess this is related to the specific instance. My Whoogle instance does not show sponsored links on a mobile device.
There doesn't seem to be a clean port for Android.
However, I have found an online version that seems to respect the original whoogle philosophy.
about sdf.org (aka freeshell.org):
In case anyone is interested in being able to use whoogle independently of the hardware/software used ^^
Good day to all
sorry simultaneous answers
It is not mandatory on first page . some times on last page , other times , between two pages ...
It is uncommon to host a web server on a mobile device. A more typical setup would be to set up the Whoogle instance on a normal computer and connect to that from your mobile device.
If you have an "always on" machine, it's pretty easy to set up a web server. If it is just Whoogle on there, a low-resource machine like a Raspberry Pi or an old laptop you don't use anymore is fine. One simple way I have done it is to set up a DDNS domain (I don't have a static IP address from my ISP), which is free from duckdns.org or similar. Then deploy a web server like Nginx or Apache and get an SSL cert through Let's Encrypt, using Certbot to obtain and renew certificates.
Here is a Docker Compose project you can grab that takes care of that whole stack for you: GitHub - evgeniy-khist/letsencrypt-docker-compose: Set up Nginx and Let’s Encrypt with Docker Compose in less than 3 minutes with a Docker Compose project, which automatically obtains and renews free Let's Encrypt SSL/TLS certificates and sets up HTTPS in Nginx for multiple domain names and a simple CLI configuration management tool.
Whoogle also can be very easily set up in Docker, so you can get everything on one Docker Compose yml and bring it up with barely any effort. Then you can set up your website as the default search engine in your browser, etc.
If you don't want to set up a publicly accessible website, another very easy-to-set-up option is to use Tailscale and set up your Whoogle server somewhere on your Tailnet. Navigate to the Tailscale IP address in your web browser when you want to bring up Whoogle, and that's it.
Either one of those options is totally free, except for the hardware you will need to host it on, but another easy non-free option would be to set up a $5/month Linode or something like that and set up your Whoogle server on there.
The public instances are convenient because you don't need to bother setting anything up, but it really is nice having your own because it's super fast and you never get rate limited.
My lifestyle is uncommon.
My always-on hardware is my rooted rugged smartphone with access point + vpn tethering, sftp+https server, adway with thirteen source lists and termux. All my devices (4) use it to connect the internet (so my smartphone provides a clean internet access). I had vpn with port forwarding (so good that my name domain point to it and replace ddns service) , but this feature will be stopped the next month (f***ing Mullvad) . So I will change vpn provider.
All this to say that it would been great to had whoogle capability to my project of nomad full featured versatile standalone server in pocket.
And incidentally, for calls and SMS. But it's rare... 
I will search if it's possible to compile whoogle into termux environment. Android stay a {Linux,Unix}-like OS.
To be continued... =)
Tailscale is a really nice way to have it all connected without relying on a DDNS or port forwarding.
I am going to have a look at it straight away.
I have just done Ă quick test.
First disadvantage: my public is ip my real ip. It is not modified.
The second: I can't get my domain name to point to my vpn easily.
There are others, but to be brief, Tailscale is Wonderful for historical function of vpn with much benefits (if I have good understood), and I keeping it in mind. I am going to need it coming soon. Thank You for this.
So it's easier for me to adopt vpn service (for privacy and more) with port forwarding feature (to bypass CGNAT of gsm). It requires only 2 steps: set public ip at my registrer (DNS type A) and set port forwarding in vpn config.
If I have understood everything correctly.
With Tailscale, you do not use your public IP--even for devices directly connected to the WAN. Tailscale sets up its own subnet in the 100.xxx.xxx.xxx address range (a private or non-routable IP range). If you want to access a device on your tailnet you use the Tailscale IP.
Run tailscale status from the command line to see the IP addresses Tailscale has given your devices, or just look at them in the admin panel when you log in at tailscale.com. Or if you download the Android client, that will show what Tailscale IP each connected device has as well.
And that's just one of it's use cases. You can use another device as exit node (speak: act as full VPN), force the same DNS server on all devices (eg. for adblocking), use the Cloudflare tunnel like "funnel" service and all that strictly regulated on zero trust principles via ACLs. Needless to say, I became a big fan it lately 
Oh, and sharing devices with other friends using Tailscale is also easily possible.
@BluishHumility and @dr460nf1r3
I did it. and it is just one part of problem .
Useless to try to sell me Tailscale. I will adopt it but for another usage.
For my specific use , it is not adapted. I will keep my 2 steps roadmap. ^^
I remind You my project:
Citation
"...... my project of nomad full featured versatile standalone server in pocket......."
And it already done. I need simply to change my vpn provider because mine stop port forwarding feature next month. That is not the problem.
My goal, now, ( and it's @SGS fault ), it is to intégrate if possible whoogle feature at my Android web server.
{joke mode on}
Ça vous dirait pas d'apprendre le français ? J'en chie avec l'anglais !
{joke mode off}
Mais c'est cool, ça me permet de réapprendre l'anglais. Et je découvre plein de choses grâce à la communauté Garuda. 
Merci pour ça aussi.
^^
installing whoogle on Android with termux is super easy. 
Thanks termux and PyPI (pip). ^^
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.
