On Thu, 13 Feb 2025 15:52:38 -0800
David Hoff Jr <dvdhf...@gmail.com> wrote:
> I have a fresh install on Debian 12 with all updates. I am trying
> to use Links web browser to access the dailycaller.com web site but am
> being blocked. A message says to enable cookies which I have tried
> using "links -enable-cookies dailycaller.com", but to no avail. Is
> there a solution to this? I can access the web site using Lynx but
> prefer Links. On another computer I am able to access the same site
> using Links from Slint which is a fork of Slackware without any
> problems.
>
I was just able to access that website without setting any options,
including UA spoofing. Also never got a response like this, usually
it's something to do with the lack of JS. However, I'm using my own
build instead of Debian's, so if you're really stuck you might try
this. I'm not sure what could be wrong with the package, though your
hint about Slackware's is another pointer. Can you compile your own
binary? It's really simple:
http://links.twibright.com/download.php
and doesn't take long. If you're just trying out of course skip the
installation step. If it works and you're ok with that, install it
somewhere in your home folder, system-wide is probably not what you
want. Then consider a bug report, to let the maintainer know.
Funny thing is just the other day I was thinking about doing my own
one, but what happened to me is too odd even for a report. A sort of
heisenbug, freak occurrence, I have no idea what precisely happened or
how, but what I know is that I tried to open a local file (html) with
Links and made some mistake. So it didn't even start, instead I got
something about an "unknown option". Next time in Links I noticed
something really strange. My bookmarks were garbled, fairly thoroughly,
or rather "extended". It so appeared they had my bash aliases (!)
prefixed, perfectly neatly. I was so puzzled I checked my shell history
how that could've happened but there was nothing. Yet I know it must've
occurred when I tried to open said file, because my bookmarks.html in
~/.links had matching timestamp, sure enough. Outlandish, although I
ran into something roughly similar with links once before and, don't
get me wrong: it's a lovely little tool but watch out, there is not
much in the way of sanity checks. It can do utterly bizarre things at
the interface with the shell, especially when you're opening a file
that isn't (plain) html. Or indeed, somehow malformed, which also is my
best guess for what could've happened here.
