parler-grab
serverless-image-handler
| parler-grab | serverless-image-handler | |
|---|---|---|
| 11 | 4 | |
| 228 | 1,260 | |
| -0.9% | 0.4% | |
| 5.1 | 4.2 | |
| over 3 years ago | about 1 month ago | |
| Lua | TypeScript | |
| The Unlicense | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
parler-grab
- Note to active US servicemembers: UCMJ Article 94
- The Hacker Who Archived Parler Explains How She Did It (and What Comes Next)
- Parler’s amateur coding could come back to haunt Capitol Hill rioters — some 80 Terrabytes of posts, many already deleted, preserved for posterity.
-
Parler’s amateur coding could come back to haunt Capitol Hill rioters
As linked in article, scraping code here:
https://github.com/ArchiveTeam/parler-grab/blob/master/parle...
-
70TB of Parler users’ messages, videos, and posts leaked by security researchers
https://github.com/ArchiveTeam/parler-grab
The details in the post are generally false - nowhere in this grabber (which is what was used to download the 70TB (or 56tb based on the tracker[0]) are admin credentials used to bypass ACLs. There were no ACLs on the video and picture files, so anyone could wget them without issue.
0: https://tracker.archiveteam.org/parler/
- All Parler user data is being downloaded as we speak!
-
Parler Databases Disclosed
https://github.com/ArchiveTeam/parler-grab
-
A job for you: Archiving Parler posts from 6/1
I'm running the Docker container now. Is there any point in running multiple containers concurrently (I'm not super familiar with Docker), or also running the manual https://github.com/ArchiveTeam/parler-grab scripts? I'm getting a lot of these:
serverless-image-handler
-
How to perform on fly image resize from CloudFront if it does not exist in the S3 origin ?
AWS Suggests this if you want to do regular lambda + CF cache and they say it is production quality: https://github.com/aws-solutions/serverless-image-handler
- My theory on why so many people are bad at coding.
-
AWS for Photos
I use imgix to resize images on the fly, which I recommend, but given the large amount of images you have it may not be cost effective. You could look into running your own: https://github.com/aws-solutions/serverless-image-handler
-
The Hacker Who Archived Parler Explains How She Did It (and What Comes Next)
It looks like there’s a ‘standard service’ for video media: https://aws.amazon.com/elastictranscoder/ but actually for jpg you might need to do something a bit more bespoke. You could deploy a ‘serverless’ lambda function to do this conversion and write the S3 urls to a database after: https://github.com/awslabs/serverless-image-handler. Looks like it uses SharpJS: https://sharp.pixelplumbing.com/. In the past I’ve used ImageMagick on compute instances: https://imagemagick.org/script/index.php
What are some alternatives?
warrior-dockerfile - A Dockerfile for the ArchiveTeam Warrior
base65536 - Unicode's answer to Base64
lowercase-keys - Lowercase the keys of an object
image-optimization - Simple, performant and cost efficient solution for optimizing images using Amazon CloudFront, Amazon S3 and AWS Lambda
lambda-edge-resizing-images-custom-origin - Sample code for resizing Images with Lambda@Edge using the Custom Origin. You can deploy using AWS CDK.
graceful-fs - fs with incremental backoff on EMFILE