lynx-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Lynx-dev] a twitter user? is a posible solution, is help with ff.ne


From: Jude DaShiell
Subject: Re: [Lynx-dev] a twitter user? is a posible solution, is help with ff.net.
Date: Tue, 9 Feb 2021 16:43:04 -0500

browssh certainly rates a reward for stupid design! What possible rationalle could there be for the package? If you run in a text environment you don't try to emulate a graphical environment, there's real graphical environments that do it lots better.


On Tue, 9 Feb 2021, Karen Lewellen wrote:

My successful source regarding fictionpress recommended posting the faulty captchas over and over again. Given users of the m.fanfiction.net platform do not get the ads either, I am not persuaded such is the issue. Especially since prior to now lynx worked just fine, with rather a few contributors who experience various print challenges.
Kare



On Tue, 9 Feb 2021, Thorsten Glaser wrote:

 Karen Lewellen dixit:

 Which is why my focus was on ffn.net fictionpress on twitter instead.

 The FictionPress twitter account has yet to react *at all* to anything
 I wrote in the last? two months or so. They seem to ignore this.

 Perhaps they realise lynx users don?t see their advertisements.

 did they mean edbrowse instead?

 No, browsh, of which brow.sh is the website. It?s some sort of pseudo
 text mode interface to Firefox. I haven?t tried it myself, but from
 the screenshots they post on the website it?s not a good fit for a11y.
 It tries to emulate the GUI look-and-feel.

 bye,
 //mirabilos
 --
 Solange man keine schmutzigen Tricks macht, und ich meine *wirklich*
 schmutzige Tricks, wie bei einer doppelt verketteten Liste beide
 Pointer XORen und in nur einem Word speichern, funktioniert Boehm ganz
 hervorragend.          -- Andreas Bogk ?ber boehm-gc in d.a.s.r


_______________________________________________
Lynx-dev mailing list
Lynx-dev@nongnu.org
https://lists.nongnu.org/mailman/listinfo/lynx-dev





reply via email to

[Prev in Thread] Current Thread [Next in Thread]