Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[RFC] a1fbox: add new TELEFONNUMMER_NET callinfo helper #3

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

mvo5
Copy link
Contributor

@mvo5 mvo5 commented Feb 17, 2021

A bit of an rfc/question - I recently ran accross telefonnumme.net and it had data on a spam call that the others did not have. So I was wondering if you would consider adding it as an additional callinfo thing? PR is a bit of an RFC, there seems to be no API so it's "parsing" html but it all looks super unstructured. So I went with a super simple approach to just pick out the "bad" ones. But of course ideas welcome. Feel free to close if it feels to hackish/unstable without an API.

@bufemc
Copy link
Owner

bufemc commented Mar 6, 2021

I have seen in my browser history I also used it once for:
https://telefonnummer.net/rufnummer/994404135029

What I really would like to parse is what comes after: "dass es sich um folgenden Typ handelt:"
(here: Ping Call). At least for the name we could pick the most voted (if you scroll down it's on the top).
Here it is Ping-Call.. somewhere else it could be something very good describing like "Versicherungsvertreter" or "Lottokuendigungsmasche" etc.

Today it was commented 1086 times, this would go into comment count.
One other problem is how to set the spam score here. I only see one could use the thumbs (up, down, neutral) for that.

It seems this service is quite the opposite to the tellows scoring: 1 means "unseriös", 5 neutral, and 10 is "seriös":

 <div class="buttons"> <button type="submit" name="serioesitaet" value="1" class="btn btn-fab bg-unserioes"><i class="material-icons">thumb_down</i></button> <h5>Unseriös</h5> </div> </div> <div class="col-xs-4 text-center"> <div class="buttons"> <button type="submit" name="serioesitaet" value="5" class="btn btn-fab bg-neutral"><i class="material-icons">thumb_down</i></button> <h5>Neutral</h5> </div> </div> <div class="col-xs-4 text-left"> <div class="buttons"> <button type="submit" name="serioesitaet" value="10" class="btn btn-fab bg-serioes"><i class="material-icons">thumb_up</i></button> <h5>Seriös</h5> </div> </div> </div> </form> 

To stick to the tellows scoring system I would e.g. invert it, the values could be 9 (very bad), 5 (neutral) and 1 for known and serious.

It seems the HTML is a little bit awkward, the piece to parse would be IMHO:

<div class="well zusammenfassung row">  <h3 class="typ "><span class="thinner">Einschätzung:</span> <strong class="btn-tooltip" data-toggle="tooltip" data-placement="right" title="" data-container="body" data-original-title="Von Usern am häufigsten gemeldete Einschätzung.">Ping Call</strong></h3><div class="text-center col-xs-4"> <span class="zusammenfassung-serioesitaet btn btn-raised btn-fab bg-unserioes btn-tooltip" data-toggle="tooltip" data-placement="bottom" title="" data-container="body" data-original-title="Durchschnittlich gemeldete Seriosität der Rufnummer"><i class="material-icons">thumb_down</i></span> <span class="subline">Ø Seriosität</span> </div> <div class="text-center col-xs-4"> <span class="zusammenfassung-meldungen btn btn-raised btn-fab btn-primary over-thousand">1.086</span> <span class="subline">Meldungen</span> </div> <div class="text-center col-xs-4"> <span class="flag-icon flag-icon-az flag-icon-squared"></span> <span class="subline">Aserbaidschan</span> </div> </div>

Could we add more parsing? Then we could integrate it also in the cascade of number checking => get_cascade_score

@bufemc
Copy link
Owner

bufemc commented Apr 2, 2021

Hi @mvo5 - any thoughts on this? Sorry it took me so long first.. today I'd have a free day ,)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants