Hey fellow Q'ers... I am considering making a rather simple web app that helps to somewhat automate the process of decoding tweets (the decoding process can't really be fully automated in most cases, at least not in any way that I'm aware of). The app will look at Trump's tweets by default, but can be used to analyze any tweet by url. It will contain functionality including:
- list Q drops that are possibly referenced by timestamp, or if it is tweet thread, examine the deltas between tweets and see if they might lead to Q posts that are relevant
- possibly applying the +/- 1200, 2400 rule when it comes to looking up Q posts
- List capitalized letters within tweet, find possible anagrams (incl. those of common relevant abbreviations), calc gematria values (cap. letters only)
- Check tweet's overall gematria value
- use natural language processing API to determine topics written about in a tweet
- use NLP API to perform sentiment analysis and categorize tweet as positive, neutral, or negative. can also be used to compute objectivity vs subjectivity
not very difficult to do with php and I could probably do it in about half of a weekend. is this a stupid idea, or might it be useful? if anyone has any other feature suggestions, please do describe them as well.
update: there is one moron in here who keeps accusing me of being a paytriot. I want to make very clear that this is NOT a commercial venture of any sort. IF it comes to fruition, it will be 100% free, open source, and hosted on a server that I personally own (i.e. not monetized by ads or anything of the sort). Note the word "if" - that is the point of this topic, I haven't even definitively said that this is something I intend to pursue. I made this thread to gauge interest in it and hear others' opinions. This is simply what I thought would be an interesting project that maybe some people would benefit from or find useful, NOT a commercial venture of any sort, as I've stated over and over in the comments below.
view the rest of the comments →
20385146? ago
Half a weekend? Lots of decode rules and permutations to be considered. I think this might be a bigger project than you realize, though I feel you may have a better handle on it than I do. I wrote a lot of code over the years, but I left that profession years ago (retired). Just determining which CAPS are out of place, misspelled words, missing or added characters ... Mind warping amount of code to be written and debugged. Every time I read SB2 I get mind warped!
Would it be beneficial to publish a shell spec on decoding tweets that other Anons can add suggestions/methods to prior to you writing the code? That would evolve into documentation on how to decode and how to use your tool after it is released. Partitioning what can be handled by your tool and how the tool output can be further decoded using methods not included with the tool?
If you code all the "routine" decode tasks it will be a big asset to help us decode faster. Roll it out, take the feedback and add new tools as time and necessity dictates for the next revisions.
Just my thoughts FWIW. Sounds like a great idea!
20415576? ago
The NumberFag here. Yes, I will provide the framework you Code Anons need to start work. This will include exactly what data to be drawing in for analysis. I will do the analysis/decode itself. Thank you.