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.

Sign up for GitHub

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

Jump to bottom

Persönliche Einstellungen für die Blockliste im Anrufbeantworter berücksichtigen #91

Open
haumacher opened this issue Nov 3, 2024 · 0 comments
Open

Persönliche Einstellungen für die Blockliste im Anrufbeantworter berücksichtigen #91

haumacher opened this issue Nov 3, 2024 · 0 comments

Comments

@haumacher
Copy link
Owner

Der Anrufbeantworter hat keine Beschränkung bezüglich der Blocklist-Größe. Aber die Mindestanzahl von Votes für eine Nummer, ab der diese als SPAM betrachtet wird, sollte berücksichtigt werden - genauso wie die Einstellung, ob Nummern über Wildcards gesperrt werden sollen.
haumacher added a commit that referenced this issue Nov 30, 2024
@haumacher
Issue #91: Keep track of blocks of phone number reported as SPAM.
fb319ea 
When a user wants to detect ranges of phone numbers that obviously
belong to the same SPAM source, there must be an easy way to decide
whether a certain number belongs to such block. To accomplish this, two
additional database tables are maintained with aggregation information.
SPAMREPORTS_10 and SPAMREPORTS_100 with aggregate information of blocks
of size 10 and blocks of size 100 respectively.
haumacher added a commit that referenced this issue Nov 30, 2024
@haumacher
Issue #91: Refactored schema of SPAM number storage.
c734341 
Consolidated number information from SPAMREPORTS, OLDREPORTS, RATINGS,
RATINGHISTORY, SEARCHES, and SEARCHHISTORY into NUMBERS and
NUMBERS_HISTORY. All relevant info for a phone number is now available
from a single database row. This makes the decision which numbers are
"most active" more easy.
haumacher added a commit that referenced this issue Nov 30, 2024
@haumacher
Issue #91: Adjusted pages to changed API.
37fd471
haumacher added a commit that referenced this issue Nov 30, 2024
@haumacher
Issue #91: Clarified table names.
b5b74c6
haumacher added a commit that referenced this issue Nov 30, 2024
@haumacher
Issue #91: Use validity ranges for history storage.
8cd015f 
This makes access to historic information much more easy.
haumacher added a commit that referenced this issue Nov 30, 2024
@haumacher
Issue #91: Updated sitemap.jsp after number API change.
4cf4f0e
haumacher added a commit that referenced this issue Nov 30, 2024
@haumacher
Issue #91: Prevent constraint violation.
7cfd3c5
haumacher added a commit that referenced this issue Nov 30, 2024
@haumacher
Issue #91: Added auto-migration.
5c8ac1f
haumacher added a commit that referenced this issue Nov 30, 2024
@haumacher
Issue #91: Fixed wrong column name.
d004fd2
haumacher added a commit that referenced this issue Nov 30, 2024
@haumacher
Issue #91: Fixed wrong column name (2).
aa2f535
haumacher added a commit that referenced this issue Nov 30, 2024
@haumacher
Issue #91: Only active numbers in statistics.
dd0cbac
haumacher added a commit that referenced this issue Nov 30, 2024
@haumacher
Issue #91: Optimized the top-searches query.
8edadee
haumacher added a commit that referenced this issue Nov 30, 2024
@haumacher
Issue #91: Added DB index for top searches query.
0460f9e
haumacher added a commit that referenced this issue Nov 30, 2024
@haumacher
Issue #91: Limit top searches to two days, even if checkpointing fails.
48fb42f
haumacher added a commit that referenced this issue Nov 30, 2024
@haumacher
Issue #91: Cleanup: Variable naming.
524bfcb
haumacher added a commit that referenced this issue Nov 30, 2024
@haumacher
Issue #91: Adjusted table header to changes report semantics.
0367176
haumacher added a commit that referenced this issue Dec 1, 2024
@haumacher
Issue #91: Fixed rating computation.
ffc8ae6
haumacher added a commit that referenced this issue Dec 1, 2024
@haumacher
Issue #91: Extracted schema setup to separate method.
81a28da
haumacher added a commit that referenced this issue Dec 1, 2024
@haumacher
Issue #91: Fixed revision creation.
cd2f534 
* Added logging if creation fails.
* Use generated keys lookup for newly created revision number.
* Adjusted migration setting the sequence correctly starting with the
next revision instead of restarting with 1.
haumacher added a commit that referenced this issue Dec 2, 2024
@haumacher
Issue #91: Integrated META_UPDATE also into NUMBERS table.
9db3cbe
haumacher added a commit that referenced this issue Dec 2, 2024
@haumacher
Issue #91: No history checkpoint during startup.
f9ab5ec
haumacher added a commit that referenced this issue Dec 2, 2024
@haumacher
Issue #91: Fixed history migration.
df7b1d5 
Since the history is not complete (only 365 days are stored) the
historic information must be reconstructed from current numbers, not
aggregated from first stored revision.
haumacher added a commit that referenced this issue Dec 2, 2024
@haumacher
Issue #91: Display most searched numbers.
5aec377
haumacher added a commit that referenced this issue Dec 2, 2024
@haumacher
Issue #91: Fixed display of related numbers in blocks of 10.
aa09a45
haumacher added a commit that referenced this issue Dec 2, 2024
@haumacher
Issue #91: Ensure that numbers of mass spammers do not time out.
9ac72f5 
A number that is found to be part of a number block is only archived, if
all numbers of the block are archived. This is achieved by updating a
"last-ping" column of all numbers in the block for each search or vote
against a number in the block.
haumacher added a commit that referenced this issue Dec 2, 2024
@haumacher
Issue #91: If a number has no comments, show comments of related ones.
b91467a
haumacher added a commit that referenced this issue Dec 2, 2024
@haumacher
Issue #91: Provide rating from block of related numbers.
513591e
haumacher added a commit that referenced this issue Dec 2, 2024
@haumacher
Issue #91: Optimized page load of status page.
9a6e1bd 
Looking up top current searches must not involve history lookup.
haumacher added a commit that referenced this issue Dec 2, 2024
@haumacher
Issue #91: Reorganized number info page.
ee32168
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@haumacher