home.social

#duckduckgo — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #duckduckgo, aggregated by home.social.

  1. Well, I felt rather badly when I got a post in my stream from the official Fediverse account for dillo.

    You see, I hadn't included it in my recent HowTo, a cookbook style tutorial on Browsers in Linux, or rather, how to install a boatload of them, and all kinds of them. I even went so far to include one produced and maintained by a company that I literally loathe (and even taught their official MCSE curriculum for them starting back in the mid 90's)...

    But I left out
    dillo. I was tired, and truth be told, it really isn't easy authoring these types of technical publications - you literally need to go through each item on a VM you spin up and take it step by step to make sure that when a neophyte comes around and wants ot simply copypasta your instructions - they can do that, and it will work.

    So anyway, the devs over at the
    dillo project posted on the Fediverse and I immediately was guilt-ridden for not including them. So I went and started to edit my earlier HowTo; I came out about 5k characters over count (and I think my server's already configured for 12K chars).

    Anyway, long story short, here's one of my latest contributions to the
    #FOSS community, specifically, one that's published in the #Fediverse first and foremost. It includes almost every browser you've probably ever used, and certainly, many you probably haven't.

    I had to Quote-Post my original so it's kinda kewl with an entry point starting with
    dillo. I think that's pretty awesome, and it quotes the original (part I if you will) that starts with Vivaldi.

    I don't usually ask, but especially with respect to this HowTo/Tutorial, the more people that boost it, the further it will reach, and the more people it can benefit. Give it a gander and if you think others will find portions of it advantageous... well, feel free to boost it.

    So without further ado,
    Here's the link to the Linux Browser HowTo

    I hope you find it useful, and Enjoy!
    🤗

    #tallship #FOSS #Fediverse #Browsers #dillo #Microsoft_Edge #Firefox #Vivaldi #Brave_Browser #DuckDuckGo #Chromium #Opera #Chawan #Lagrange #Tor #Lynx #Elinks #Links #Nyxt #Epiphany #Falkon #Konqueror

  2. And now for dillo

    ## dillo browser (the honorable mention):

    Now, this tutorial wouldn't be complete without one of the most determined browser projects of all to be included. Unfortunately for the user (and by user I mean the common, everyday n00b, joeuser), very little effort has been put into a one & done download/install procedure.

    To be honest, dillo is a bit of a pain in the butt, because even though a lot of effort has been put into rescue of the intellectual property after the main author of the engine passed away and the original domain registration expired (to be picked up by a cybersquatter), rebuilding the forward facing public assets still leaves much to be desired for a simple joeuser - the folks we are all trying to ultimately serve and make things simple.

    For example, Where you would almost universally expect to see a "Download dillo" link or button, you will indeed find a link, but it leads to their cgit repo. Even junior devs cringe when they first come across cgit, even though it really is arguably far superior to GitHub style facilities like Gitea, Forgejo (Codeberg), and SourceHut.

    Although it's really only a matter of appearance, cgit was written by Jason A. Donenfeld, who also created Wireguard and Pass - the standard UNIX password manager, popular on Androids too (via F-Droid, requires installing OpenKeyChain too on Android).

    But back to #dillo! You may be wondering why I placed it so far down the list, and the reason is twofold:

    1. ) I brainfarted. Yup, I was really tired and literally forgot when initially publishing this first edition of the Browsers on Linux HowTo, and for that, especially to the dillo dev team, I apologize.
    2. ) It may seem a bit complicated - but I assure you it is not, especially when compared to the #Tor_Browser, which immediately precedes the instructions for installing dillo.

    I know that a lot of folks went through and endured the process of installing the Tor Browser, because it's such a popular utility in today's world, and since I'm figuring that you got through that okay, we can now turn our attention to dillo, without all of the hunting around on various git repo servers out there and web pages - just the bare bones simple cut and paste for you here...

    So let's get to it, shall we?

    NOTE: You should know by now that commands prefaced with ~$ are to be administered by you, the regular, unpriviliged user account; while commands prefaced with ~# mean that those commands are issued by "root". You have a choice in your terminal. The first is just to prepend the root commands with sudo, while the other option is to issue su - to root, then go into the directory the user was in and issue those commands. You may find it easier to just open a fresh tab in your terminal app so you have one user ($) shell and then in the other tab or window you have the root user's (#) shell.

    The first thing we need to do is make sure that we have resolved all dependencies (prerequisites) for compiling dillo. We do that as root (or via sudo as I just mentioned above) like so:

    ~# apt install gcc g++ git git-all autoconf automake make zlib1g-dev libfltk1.3-dev libssl-dev libc6-dev libpng-dev libjpeg-dev libwebp-dev libbrotli-dev
    

    Don't worry if some, or even most or all of those packages aren't installed, because some, many, or all of them may already be installed on your system, and invoking the install won't overwrite anything already installed.

    Next, let's git (pundit there), er... get the source for dillo, and yes, we're going to use git. A mention now that doing it this way means that in the future your updates will be relatively simple and brainless. More on that later. We'll start by creating a directory (folder) to work from, a place where you can use in the future that doesn't clutter up your home directory with needless entries; then we'll download the source code, build it locally, and install it...

    All you have to do is cut and paste each line, one by one, and wait for each step to finish before pasting the next line into your terminal.

    ~$ cd; mkdir -pv dev; cd dev
    ~$ git clone https://git.dillo-browser.org/dillo
    ~$ cd dillo
    ~$ ./autogen.sh
    ~$ mkdir build
    ~$ cd build
    ~$ ../configure --prefix=/usr/local
    ~$ make
    ~$ sudo make install
    root@mylaptop:/home/joeuser/dev/dillo/build# make install
    

    That's it! dillo has been installed!

    Now, and because we're at the very end. I want to explain the $ and # stuff so it's clear. Notice that the dillo installation steps is the only place in this HowTo that I included a sudo command. The reason is that I believe that in most cases, sudo is a bad way to administer a machine. In classic, traditional UNIX administration, you su to root (the Superuser), do what you need to with thos elevated privs and then exit out of the root shell and back to your unprivileged user account.

    So ~# is merely a shorthand in most Bash shells. typically, you're going to see something like username@hostname:/path/to/directory$ for a non-priviliged user, or for root, it will generally read as root@hostname:/path/to/directory#

    Generally speaking when you issue a command from a particular directory as a non-privileged user, followed by a command by the superuser (root), you probably want to be in that same directory. So the final command above which was make install, would have been performed by the non-privileged user ($) using the sudo utility (or, doas on some OSes) or as root - but as root, you would have wanted to be in that same directory to run the make command to install the compiled binary in /usr/local on your machine. This is what it would look like had you decided (I recommend this practice in most cases) to 'su -' to root instead of using sudo:

    joeuser@mylaptop:~/dev/dillo/build$ su - 
    root@mylaptop:~# cd /home/joeuser/dev/dillo/build
    root@mylaptop:/home/joeuser/dev/dillo/build# make install
    root@mylaptop:/home/joeuser/dev/dillo/build# exit
    joeuser@mylaptop:~/dev/dillo/build$ cd
    joeuser@mylaptop:~$ which dillo
    /usr/local/bin/dillo
    joeuser@mylaptop:~$ dillo &
    

    If you followed along with that last block of code, you'll see that we asked where our program (dillo) is, by using the which command. It told us that it's located /user/local/bin/dillo, in our default "path", so all we need to do (from anywhere) is just type in dillo & - the ampersand will release our shell so the process can run in the background. Just hit your "return" or "enter" key and you'll get your prompt back.

    Have fun running dillo!

    Well, I went into a lot of explantions that normally aren't covered, because basic navigation and what your prompts are going to look like are just assumed in most HowTo's and Tutorials, including mine. But it should be covered somewhere and this was a logical place.

    There is just one more (optional) task to complete. Adding dillo to your menu panel - I'm going to leave that task up to you, it's worth learning, and honestly, I don't want to have to cover how to do this in KDE Plasma, Xfce, GNOME, Cinnamon, Mate, etc.... you get the idea; I have no idea what desktop environment you're running but it's an excercise that is worthwhile so you can configure your menus and desktop anyway, so do give it a go :)

    There's really just one last thing folks....

    Here's just a taste of what to expect with future updates to this HowTO:

    ~# sqg -p dillo && sbopkg -i dillo.sqf

    "What?" You say? Yup! That's Slackware. Installing pretty much every single Browser in this article is as simple as doing a copypasta of that one liner with sbopkg...

    But you'll have to wait for all of that funstuff :p

    And remember: You can haz #Cheezburgerz! 🍔🍟

    I hope that helps!

    #tallship #FOSS #browsers #dillo #Microsoft_Edge #Firefox #Vivaldi #Brave_Browser #DuckDuckGo #Chromium #Opera #Chawan #Lagrange #Tor #Lynx #Elinks #Links #Nyxt #Epiphany #Falcon #Konqueror

    RE: https://public.mitra.social/objects/019f49aa-b5c6-7372-b92d-68821dcad285

  3. #Flock #Leaked Cops’ #LicensePlate Searches via #DuckDuckGo , #Bing

    Automatic license plate reader (#ALPR) company Flock exposed the reasons cops conducted searches, and sometimes the specific searched license plates, in common search engines like DuckDuckGo and Bing, according to tests by #privacy advocates and 404 Media and a statement from the company.

    404media.co/flock-leaked-cops-

  4. The Programmer’s Fulcrum: 5 June, 2026

    This post originally appeared on The Fulcrum.

    Welcome to this week’s The Programmer’s Fulcrum.

    It’s your weekly curation of the essential news in the Open Media Network and Fediverse development communities with a focus on devastating big tech via Techno Anarchism.

    The big news this week was obviously The European Commission’s European Technological Sovereignty Package. So, there’s much more […]

    https://newsletter.mobileatom.net/the-programmers-fulcrum-5-june-2026/ #Ackee #ActivityPub #AI #ATProto #Bonfire #BuildAwesome #Caddy #CSS #DuckDuckGo #elixir #fediverse #Ghost #GitHub #Holos #HTML #javascript #LAUTI #Leaflet #LibreOffice #Linux #Manade #Mastodon #Mastro #Matrix #MicroBlog #Movim #Nextcloud #OMN #Plausible #PostmarketOS #Qwant #Rails #RSS #SelfHosting #Servo #Sharkey #signal
  5. Back in the day, we had #deleteFacebook, #deleteMeta, #deleteWhatsApp, and so on.

    Some people heeded the call for a while, only to quietly return to Big Tech later on.

    Now, many have been jolted awake by our dependence on Big Tech, and another #quitday and other variations are gaining momentum.

    Personally, I started that journey years ago.

    - From Gmail to #ProtonMail and #Tuta
    - From Google to #Searx #Startpage #DuckDuckGo
    - From Chrome to #Brave #Mulvad and #LibreWolf
    - From MS Office to #LibreOffice
    - From Google Drive to #NextCloud and #Synology
    - From Facebook to #MeWe and #Mastodon
    - From Windows to #Linux
    - From WhatsApp to #Threema #Signal #Jami and #Matrix #Element
    - From Zoom to #Jitsi and #ProtonMeet
    - From Google Translate to #Deepl

    I’m sure I’m forgetting a few, but there’s a European and open-source alternative for every American Big Tech and closed-source application.

    What I’ve noticed is that many people are afraid of what they don’t know and therefore don’t dare to make the switch (completely).
    (Some people just don’t give a damn and convenience is all that matters)

    Any fear is unfounded, and if all of us switches en masse, Big Tech’s power will be quickly broken, and the development of alternatives will proceed much more smoothly and quickly.

  6. Vroeger hadden we #deleteFacebook #deleteMeta #deleteWhatsApp en noem maar op.

    Sommigen gaven daar even gehoor aan om later toch stilletjes terug te keren naar Big Tec.

    Nu werden velen even wakker geschud door onze afhankelijkheid van Amerikaanse Big Tec en komt er weer een #doeidag en andere varianten op gang.

    Persoonlijk ben ik die reis al jaren geleden begonnen.

    - Van Gmail naar #ProtonMail en #Tuta
    - Van Google naar #Searx #Startpage #DuckDuckGo
    - Van chrome naar #Brave #Mulvad en #LibreWolf
    - Van MS Office naar #LibreOffice
    - Van Google Drive naar #NextCloud en #Synology
    - Van Facebook naar #MeWe en #Mastodon
    - Van Windows naar #Linux
    - Van Whatsapp naar #Threema #Signal #Jami en #Matrix #Element
    - Van Zoom naar #Jitsi en #ProtonMeet
    - Van Google Translate naar #Deepl

    Ik vergeet er vast nog een paar, maar er is voor elke Amerikaanse en Closed Source toepassing wel een Europees en Open Source alternatief.

    Wat ik merk is dat veel mensen bang zijn voor dat wat ze niet kennen en daarom niet (geheel) durven over te stappen.
    (sommigen interesseerd het gewoon geen reet en is gemak het enige dat telt)

    Eventuele angst is ongegrond en als we met heel Europa massaal overstappen is de macht van Big Tec snel gebroken en verloopt de ontwikkeling van alternatieven veel soepeler en sneller.

  7. Seeing the posts about #Bing (and, by extension, #DuckDuckGo) blocking #Neocities makes me want to remind people about small web-focused alternatives like #Wiby (wiby.me) and #Clew (clew.se).

  8. [Перевод] Обзор поисковика Kagi за три месяца использования

    Kagi — это не просто альтернатива Google. Это попытка создать поисковик, где пользователь платит за качество, а не становится товаром. За три месяца без Google я протестировал его поисковую систему, интеграцию с ИИ и даже моральные дилеммы за кулисами. Вот честный обзор: с плюсами, минусами и размышлениями о том, стоит ли платить за поиск в 2025 году.

    habr.com/ru/articles/942300/

    #kagi #google #brave #search #поисковик #duckduckgo #bing

  9. Searching for Für Elise on Duck Duck Go gives the Wikipedia article with a nice summary as the featured result. Just below is just a regular search result pointing to the same article with a strange summary.

    > Für Elise is nearly universally featured on ringtone websites.

    Are ringtone websites still a thing?

    #Wikipedia
    #DuckDuckGo
    #Ringtones

  10. DuckDuckGo 捐了 $25K 給 The Perl and Raku Foundation

    在「DuckDuckGo Donates $25,000 to the Perl and Raku Foundation (perl.com)」這邊看到 DuckDuckGo 捐錢給 The Perl and Raku Foundation 的新聞,基金會端的新聞稿在「DuckDuckGo Donates $25,000 to The Perl and Raku Foundation」

    blog.gslin.org/archives/2024/1

    #Computer #Financial #Murmuring #Network #SearchEngine #501 #501c3 #and #duckduckgo #foundation #perl #raku #the

  11. @nullstreak @ldrngmtv Я использую разные #поисковики. По умолчанию указан #Qwant (пользователей с российскими IP-адресами посылает лесом, так что я захожу с другим IP-адресом), также есть #Peekier, #Andi, #Mojeek и другие. Есть в том числе и #DuckDuckGo aka #DDG.

    А #SearX, насколько я понимаю, не #поисковик, а лишь аггрегатор поиска, и все его результаты поиска ведут на найденные сайты не прямо, а через следящие скрипты поисковиков (в частности, #Google и #Bing). Это не так?


  12. Updated My Website a bit. Changed the Search page to wiby.me instead of duckduckgo.com and as I had to change some things Decided to write a Blog about today too lol.
    arianbhatt.github.io/blogs/col

  13. Поисковик #Brave, который я сам использовал одно время и ещё буду, заявил о персонализированных результатах.

    Для быстрого поиска он подходит, но на общие темы лучше какой-нибудь #searX. Хотя, возможно, результаты стали лучше, надо проверять. Внимание он заслуживает.

    3dnews.ru/1068699/poiskovik-br

    #3DNews #Google #DuckDuckGo #Search