Facebook profile face dump Updated 2025-07-16
In 2016 Ciro made a script downloaded Facebook profile pictures.
This was possible at the time without any login by using a 2010 profile ID dump from originally announced at: blog.skullsecurity.org/2010/return-of-the-facebook-snatchers since profile picture access was not authenticated.
The profile ID dump was downloadable through a BitTorrent named fbdata.torrent of about 2.8GB, mostly compressed. Doing:
find . -type f | xargs sha256sum | sha256sum
on Ubuntu 20.04 gives:
2c9a739c9c5495e38ebab81fc67411b7c6562f139dcb8619901a3f01230efdd5
This dump widely reported e.g. on Hacker News at: news.ycombinator.com/item?id=1554558.
At some point however, Facebook finally started to require tokens to view public profile pictures, thus making such further collection impossible, e.g. as of 2021: developers.facebook.com/docs/graph-api/reference/v9.0/user/picture mentions:
Querying a User ID (UID) now requires an access token.
This is also mentioned e.g. at: stackoverflow.com/questions/11442442/get-user-profile-picture-by-id. This major privacy flaw was therefore finally addressed at some point, making it impossible to reproduce this project.
Ciro downloaded 10 thousand of those pictures, and did facial extraction with: stackoverflow.com/questions/13211745/detect-face-then-autocrop-pictures/37501314#37501314
He then created single a video by joining 10 thousand of those cropped faces which can be uploaded e.g. to YouTube. Ciro later decided it was better to make those videos private however, as sooner later he'd lose his account for it.
Companies like YouTube blocking this kind of content is the type of thing that makes companies take longer to fix such gaping privacy issues, and is a bit like security through obscurity. A video makes it clear to everyone that there is a privacy issue very effectively. But people prefer to hide and look away, and then 99% of people who know nothing about tech get their privacy busted by actual criminals/government spies and never learn about it.
But now that Facebook finally fixed it, it's fine, no need for the video anymore.
NFPA 704 Updated 2025-07-16
pH Updated 2025-07-16
Applications of Josephson Junctions Updated 2025-07-16
Solving differential equations was apparently Lie's original motivation for developing Lie groups. It is therefore likely one of the most understandable ways to approach it.
It appears that Lie's goal was to understand when can a differential equation have an explicitly written solution, much like Galois theory had done for algebraic equations. Both approaches use symmetry as the key tool.
Bought: 2018, 2021.
Seems to work OK. But you're fighting the symptom, and it will eventually come back.
Double act Updated 2025-07-16
This is crap, became slow very fast. The battery is IMPOSSIBLE to remove!!! youtu.be/kO-RwIQ_i1w?t=162 Battery was 4.163V when thing wouldn't turn on anymore. But topbattery.co.uk/product/original-battery-for-tablet-lenovo-yoga-tab-3-yt3-x50fyt3-x50m-sl20076-2/ says it is 3.6V. What?
The file:
/media/$USER/MICROBIT/DETAILS.TXT
contains:
DAPLink Firmware - see https://mbed.com/daplink
Version: 0234
Build:   Oct 12 2015 14:53:22
2022-10-14: stopped being able to connect to Ubuntu 22.04. Was trying to do a UART video demo, connected USB, disconnected, connected, disconnected several times on different filming attempts. Was working some of the time, Ubuntu did recognize it, I even saw UART output for sure, but was a bit unstable. But then at one point it just stopped getting recognized by Ubuntu 100% of the time. The board is still being powered by USB, and the previously flashed program still runs, but nothing showed on sudo dmesg -w at all, and I can't reprogram it!
A day later, managed to get tit to connect once more with a different cable, but just once!
[15310.385055] usb 1-5: new full-speed USB device number 38 using xhci_hcd
[15310.534996] usb 1-5: New USB device found, idVendor=0d28, idProduct=0204, bcdDevice=10.00
[15310.535000] usb 1-5: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[15310.535001] usb 1-5: Product: MBED CMSIS-DAP
[15310.535002] usb 1-5: Manufacturer: MBED
[15310.535003] usb 1-5: SerialNumber: 9900023436424e45001d30150000005d00000000cb8928bd
[15310.541267] usb-storage 1-5:1.0: USB Mass Storage device detected
[15310.541643] scsi host4: usb-storage 1-5:1.0
[15310.542658] hid-generic 0003:0D28:0204.000A: hiddev1,hidraw2: USB HID v1.00 Device [MBED MBED CMSIS-DAP] on usb-0000:00:14.0-5/input3
[15310.543121] cdc_acm 1-5:1.1: ttyACM0: USB ACM device
[15311.549969] scsi 4:0:0:0: Direct-Access     MBED     DAPLINK VFS      0.1  PQ: 0 ANSI: 2
[15311.550273] scsi 4:0:0:0: Attached scsi generic sg1 type 0
[15311.550825] sd 4:0:0:0: [sdb] 16512 512-byte logical blocks: (8.45 MB/8.06 MiB)
[15311.551052] sd 4:0:0:0: [sdb] Write Protect is off
[15311.551054] sd 4:0:0:0: [sdb] Mode Sense: 03 00 00 00
[15311.551204] sd 4:0:0:0: [sdb] No Caching mode page found
[15311.551207] sd 4:0:0:0: [sdb] Assuming drive cache: write through
[15311.572160] sd 4:0:0:0: [sdb] Attached SCSI removable disk
[15316.317438] usb 1-5: reset full-speed USB device number 38 using xhci_hcd
[15316.445093] usb 1-5: device descriptor read/64, error -71
[15316.681102] usb 1-5: device descriptor read/64, error -71
[15316.917102] usb 1-5: reset full-speed USB device number 38 using xhci_hcd
[15317.045028] usb 1-5: device descriptor read/64, error -71
[15317.281149] usb 1-5: device descriptor read/64, error -71
[15317.517154] usb 1-5: reset full-speed USB device number 38 using xhci_hcd
[15317.517466] usb 1-5: Device not responding to setup address.
[15317.725358] usb 1-5: Device not responding to setup address.
[15317.933042] usb 1-5: device not accepting address 38, error -71
[15318.061027] usb 1-5: reset full-speed USB device number 38 using xhci_hcd
[15318.061347] usb 1-5: Device not responding to setup address.
[15318.269270] usb 1-5: Device not responding to setup address.
[15318.477018] usb 1-5: device not accepting address 38, error -71
[15318.477153] usb 1-5: USB disconnect, device number 38
[15318.652912] usb 1-5: new full-speed USB device number 39 using xhci_hcd
[15318.785044] usb 1-5: device descriptor read/64, error -71
[15319.021068] usb 1-5: device descriptor read/64, error -71
[15319.257030] usb 1-5: new full-speed USB device number 40 using xhci_hcd
[15319.385075] usb 1-5: device descriptor read/64, error -71
[15319.621147] usb 1-5: device descriptor read/64, error -71
[15319.729170] usb usb1-port5: attempt power cycle
[15320.384941] usb 1-5: new full-speed USB device number 41 using xhci_hcd
[15320.385176] usb 1-5: Device not responding to setup address.
[15320.593188] usb 1-5: Device not responding to setup address.
[15320.801023] usb 1-5: device not accepting address 41, error -71
[15320.928909] usb 1-5: new full-speed USB device number 42 using xhci_hcd
[15320.929073] usb 1-5: Device not responding to setup address.
[15321.137244] usb 1-5: Device not responding to setup address.
[15321.344947] usb 1-5: device not accepting address 42, error -71
[15321.345173] usb usb1-port5: unable to enumerate USB device
[15321.384929] FAT-fs (sdb): unable to read boot sector to mark fs as dirty
Exact same USB and port could still mount the Raspberry Pi Pico.

There are unlisted articles, also show them or only show them.