"free" aka 500 requests and then we need to pay when all you really did was rehost their data.
> I got tired of rate limits and slow responses from the official vulnerability databases while building a security tool. So, I decided to build my own solution.
And now this solution introduces those issues again
This is a hosted instance of nitter, the reason why nearly all nitter instances died is because "guest" accounts got removed, so now you need tons of real twitter/x accounts instead of just generating thousands of "guest" accounts.
Well, the name of the "real" account is "zkevm.dev", and the previous account was zk-evm. Those are just letters to me, but it does seem like a clear link. Couldn't say that either is "real", though.
tldr, it mines your public social media posts and maps your degree of connection to people who post “extremist” content (guilt by association) and then ties that to any internal private dirt the FBI has on you
evades 4th amendment, warrant, FISA types of reporting because its all stuff you chose to post publicly on one of these platforms.
I sometimes wonder the firm defintion(s) of 'public social media'
If you post a blog on blogspot or similar it seems the point is to be public.
(there could be settings there to make some things non public, I don't remember or know what is current)
If you post on a network that requires login to see the posts, is that public?
(is twitter / tumbler / fbook all indexed via google / available without login?)
If you post on a social network inside a group that requires approval to join, but is free - is that public?
If you post something behind a paywall, is that public?
If someone shares a photo of you that you DMed a person using a social network..
Snapchat makes things disappear, whatsapp advertises that even they can't see your bad behavior.
Did you have a reasonable expectation of privacy in these places?
One could argue that stolen photos, texts, books, movies that are posted on a social network are now public.
And then I think about the number of people who don't understand what is public and what can be seen by others, and I feel that our apps and hardware should bear some responsibility to remind people that tapping like or making a comment may feel intimate / 1 to 1, but you may be questioned one day very publicly about why you were voting for one kind of thing while giving thumbs up and praise comments to twinks from your official account.
Then I wonder what kind of hybrid social systems will be a thing in the future - some sort of encrypted 1 to 1 and 1 to groups thing.
It's not just stories like this, but companies scraping tinder profiles and sharing the pictures and such..
People's expectation of privacy and the horrors of that not being a thing will likely cause more and more migrations into privacy proxy identity avatar agents;
which will likely lead to less data for the big companies where the data knowledge is the gold.
It doesn't really explain where the environment runs, it's not clear if I have to configure something like GCP/AWS or if GitArsenal handles all this (and how much it costs if so)
Good question, it handles all the infrastructure. GitArsenal runs on Modal's serverless platform, and we automatically provision the right machines for each repo's requirements(working on this feature btw). You don't need to configure GCP/AWS or manage any cloud resources, just point us at a GitHub repo and we handle finding the appropriate compute, spinning up environments, and running the setup
Please don't complain about tangential annoyances—e.g. article or website formats, name collisions, or back-button breakage. They're too common to be interesting.
> I got tired of rate limits and slow responses from the official vulnerability databases while building a security tool. So, I decided to build my own solution.
And now this solution introduces those issues again
"1 requests per minute"