Greg Wooledge <g...@wooledge.org> wrote: > On Sat, Mar 08, 2025 at 13:39:18 -0800, Charlie Gibbs wrote: > > On Sat Mar 8 13:29:36 2025 debian-u...@howorth.org.uk wrote: > > > D MacDougall <dmacd...@usc.edu> wrote: > > >> https://duckduckgo.com > > > > > > That's just a blank page except for a picture of a duck, the word > > > DuckDuckGo and a search box. No explanation of anything at any > > > length? > > > > Scroll down.
It's all one page, no scrolling. > Interesting. I see *way* more widgets than @howorth is seeing, even > without looking downward. > > Across the top, I see the corporate logo, a long entry field for the > search text, a button for chat (with a speech balloon icon next to > it), and a hamburger menu button. > > Below that, there's some text in a large font, then a very large > button offering me the opportunity to make DDG my default search > engine. > > At the bottom of the page are the words "Learn more", and a round > button with a downward-pointing arrow inside it. > > If @howorth is running some kind of ad blocker or client-side content > filter that's altering the contents of the page, it must be a *really* > aggressive one. All I'm running is noscript. Aren't you? > P.S. looking at the HTML source with Ctrl-U, it's all one line. > Seriously, who does that? Anybody used to JS minimisation. > hobbit:~$ xclip -o | wc > 0 2960 44363 > > 44 kilobytes of HTML/CSS/Javascript, all in one. stupid. line. Well, > they found a way to make me stop trying to read their page source, > that's for damned sure. That's what pretty printers are for surely?