On Fri, 20 Nov 2020 09:12:47 +0100 Antonio Ospite <a...@ao2.it> wrote:
> On Fri, 20 Nov 2020 14:47:23 +0800 > Paul Wise <p...@debian.org> wrote: > > > Package: tweeper > > Version: 1.4.2-1 > > Severity: important > > When I try to download the RSS for an Instagram account that does not > > exist, tweeper just returns an empty RSS feed and exits with success. > > > > When I try to download the RSS for a Facebook account that does not > > exist, tweeper prints a "Page not found" feed and exits with success. > > > > I assume that there are similar issues with all of supported sites. > > > > Instead it should return an error on stderr and exit with a failure, > > for each of the different websites that are supported. > > > > Thanks for the report Paul, I'll take a look during the weekend. > The issue has been fixed in the upstream master branch: https://git.ao2.it/tweeper.git/commitdiff/ad39a334af38e4a5d37e553e8ad81eac4d2cedaa https://git.ao2.it/tweeper.git/commitdiff/d5cf35e48bf2644118ede9b58f99e200e420b481 And Twitter support has been restored too after it broke because apparently Twitter is not serving the mobile UI anymore. I hope to have a new Debian package uploaded soonish. Ciao, Antonio -- Antonio Ospite https://ao2.it https://twitter.com/ao2it A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing?