pygooglenews VS LibreSignal

I have ~4k start in 2 Python libraries. Both help fetch live news articles. Links below.

These were my first libraries.

I took the approach of promoting them as any other product. You have to "sell" your code. Even if it's 100% free.

In my opinion, the most important thing is DEMO. Just make a GIF where you showcase what your software does:

* 80% of engineers won't even bother to read the description

No one will spend their precious time trying to get through your code.

[0] https://github.com/kotartemiy/newscatcher Programmatically collect normalized news from (almost) any website.

[1] https://github.com/kotartemiy/pygooglenews If Google News had a Python library

I wrote a pygooglenews package for news mining out of google news.

I'm curious where the data get fetched from. The Author mentions that Mozilla Readability and SimplePie are used.

Readability to parse the content. SimplePie to fetch the data (I assume). Dat from RSS feeds?

In case you want to make something similar, I recently wrote a blog on where you could get news data for free [1]

(self-promo) I'd recommend to take a look at my Python package to mine news data from Google News [2]. Also, in 3 days we're releasing an absolutely free News API [3] that will support ~50-100k top stories per day.

[1] https://blog.newscatcherapi.com/an-ultimate-list-of-open-sou...

[2] https://github.com/kotartemiy/pygooglenews

[3] https://newscatcherapi.com/free-news-api

I wrote a python package to scrape google news headlines at scale: https://github.com/kotartemiy/pygooglenews

Write libraries AND services, where it makes sense.

I wrote a Python library to scrape google news [0]

We also have it as a service [1]

Want to know why? Because devs who can't pay won't pay. Businesses who can pay will rather pay for a service (API in our case), and not care about maintaining it.

[0] https://github.com/kotartemiy/pygooglenews

[1] https://newscatcherapi.com/google-news-api

You can use this Python project to scrape Google News (https://github.com/kotartemiy/pygooglenews) If you look at the code you can get a feel of how to call Google News directly.

https://github.com/kotartemiy/pygooglenews https://pypi.org/project/google-play-scraper/

>what does this mean?

Moxie (Signal's founder) has thrown fits in the past over the existence of third-party clients using their servers: https://github.com/libresignal/libresignal/issues/37#issueco...

0: https://github.com/libresignal/libresignal/issues/37

I push back when anyone recommends Signal because they are fundamentally not an open network.

OWS has historically been hostile to third party implementations outside of their clients. There are multiple unofficial options but the only one I've been looking at is the bridge with matrix, though setting up a matrix server just for this is likely overkill.

I have to say that I find him fascinating too, but there are a few things that raise my suspicion, but of course do not convict him of anything:

The way he is attacking this alternative Signal client and rules out interoperability:

https://github.com/LibreSignal/LibreSignal/issues/37#issueco...

Signal was a word before he decided to turn it into a brand.

The signal server source code repo was not updated for a year. Communication intransparent.

https://www.androidpolice.com/2021/04/06/it-looks-like-signa...

I am not even against crypto integration, but I found the choice of MobileCoin odd. Instead of integrating an existing privacy coin or working with the community, he decided to integrate MOB and to be one of their "advisors":

https://techcrunch.com/2018/04/24/mobilecoin-moxie-marlinspi...

https://www.coingecko.com/en/coins/mobilecoin

Is that so surprising? Signal had always a hostile attitude to alternative clients. They have this weird disconnect of the new CEO saying they want to be available to as many people as possible and be a fully commited FOSS app, and then have no version on F-Droid (while Telegram has!) and actively fight alternative clients (see https://github.com/LibreSignal/LibreSignal/issues/37#issueco...)

Because of this hostility Signal is not a trustworthy organization at all.

LibreSignal existed before Moxie was like “no, don’t”: https://github.com/LibreSignal/LibreSignal

They have shut down third party clients, and resve the roght to continue that.

https://github.com/LibreSignal/LibreSignal/issues/37#issueco...

1) You need to audit that code, which.. everyone will have to do.

2) https://signal.org/blog/reproducible-android/

> the Signal Android codebase includes some native shared libraries that we employ for voice calls (WebRTC, etc). At the time this native code was added, there was no Gradle NDK support yet, so the shared libraries aren’t compiled with the project build.

a good answer in my opinion, but it means what you run from the play store is not reproducible and thus can never really be confirmed to be what the sources actually include. There are also binary blobs needed for interacting with Google Play.

3) Signal is openly hostile to third party client implementations: https://github.com/LibreSignal/LibreSignal/issues/37

Moxie Marlinspike on May 5th 2016:

> I'm not OK with LibreSignal using our servers, and I'm not OK with LibreSignal using the name "Signal." You're free to use our source code for whatever you would like under the terms of the license, but you're not entitled to use our name or the service that we run.

> If you think running servers is difficult and expensive (you're right), ask yourself why you feel entitled for us to run them for your product.

Moxie Marlinspike left Signal this January[2] 2022.

Whose to say whether there will be any change, but it's been interesting seeing Signal as a somewhat defended property. Although various third party clients/tools/libraries do exist already.

The claim that running servers is expensive would have been more interesting, imo, had there been any viable way to run your own. But for a long while Signal server source code wasn't being updated at all.

[1] https://github.com/LibreSignal/LibreSignal/issues/37#issueco...

[2] https://signal.org/blog/new-year-new-ceo/