>>20640411

chkt and chkt again

>aggregators and archivists often use spaces to identify where buns begin and end

TYBV!

Anon notes, anon started writing an aggregator, couple years ago. As anon began developing it, anon added "edge conditions" like when there's an extra space.

Not saying every aggregator needs to update their code.

Just saying there are ways to be more flexible, even when writing digital code.

And, sometimes, being too flexible means you may start hallucinating (e.g., finding Notable where they aren't, like when attackers put a bunch of pb Notables in a list).

Anon had a good beginning, but then life got in the way.

(That sounds larger than anon meant it, kek.)

>>20640734

>Are we talking Wilshire blvd?

Wells Fargo is at 5601; can see it in beginning shot.

Huh. Keeps giving "Invalid Image….".

So, okay, putting it on Catbox. Means you get three versions.

Under 16 MB that wouldn't upload:

https://files.catbox.moe/1asqto.mp4

21 MB of same that anon just converted (via "ffmpeg -i input.mp4 -vcodec libx265 -crf 28 output.mp4"; if resulting file is too small, reduce the "28" and if too large, increase it):

https://files.catbox.moe/az4m3f.mp4

And a much larger one, 207 MB:

https://files.catbox.moe/aarhrp.mkv

>>20640508

TYB!

> >>20640420 .@realDonaldTrump: Our heartfelt prayers go out to the family of highly decorated NYPD officer Jonathan Diller… (why is there a period at the beginning of Scavino's line?)

When a tweet begins with an "@username", it only goes to that user. (This might be historical, and no longer happens.)

The period is placed at the beginning of a tweet that starts with a username, in order for everyone following that username, to be able to see the tweet.

Here's some sauce:

https://www.ethow.com/2014/03/why-some-tweets-start-with-dot.html