×
Login Register an account
Top Submissions Explore Upgoat Search Random Subverse Random Post Colorize! Site Rules
5

API?

submitted by SearchVoat to TalkDev 2.9 yearsJun 22, 2021 00:57:35 ago (+5/-0)     (TalkDev)

This thread over at the SearchVoat Forum https://forum.searchvoat.co/viewtopic.php?f=11&t=3138 raised the idea of a talk.lol API for updating SV with talk.lol posts and comments. Reason being there are some talk.lol comments missing from SV. Cannot detect gaps at that end because of your postid convention.

Are you interested in making talk.lol properly searchable? Obviously it doesn't need a comprehensive API just to stream the posts to SV, but something needs to be added to make it reliable. I'm just scraping currently, which is very inefficient and incomplete.

Any thoughts on this?


2 comments block


[ - ] system 6 points 2.9 yearsJun 22, 2021 01:27:30 ago (+6/-0)

Yeah good idea. Shouldn't be too hard to get something going. Let me see what I can whip up.

[ - ] try 1 point 2.9 yearsJun 22, 2021 02:07:15 ago (+1/-0)*

A type of api, even if minimalist and so primitive its just the last 60 minutes worth sorted indexes would be better than scraping using ...

https://www.voat.xyz/v/all?view=bump

bump, followed by a blind descent by date seems 99% accurate, but the pesky asterisk for "edited" retains the original date I assume, requiring a hash compare of prior messages with "edits" when folding into searchvoat.co, and I think asterisk edited comments dont percolate into "bump" at all, EVER. Try it yourself. No bump entrance.

This means its hard to scrape re-edited comments. very hard, except by active user recent last few comments list, but last few comments list ALSO omits putting edited comments at the top.

re-Edited comments are basically what a scraper will miss currently.

An API would make searchvoat.co more functional, but should also use a CREDENTIAL auth code unless url request from a logged in account. Avoiding a credential opens door for ddos or other harassment.

Proposed API url call should also denote edited comments.

using biderectional POST and JSON would allow massive data payloads returned