>>/10686/
> Blogger
Based on what Google said, Blogger is endangered. If you didn't already know, there was a focused community effort to grab Blogger blogs in 2015 and 2023:
https://wiki.archiveteam.org/index.php/Blogger

Data:
. WARCs should be available here: https://archive.org/details/archiveteam_blogger
. and replays should be available in this web site: https://web.archive.org/
. I have some non-AT WARCs such as:
> /ipfs/QmdDNRVfi7SNPPfNnMg5nReyPow93Wj5aaC16vDCg88rdD/elbronymendivil.blogspot.com/warc/elbronymendivil.blogspot.com-2021-04-25-0e77bf66.cdx
> /ipfs/QmbVwuMgwUrSCTbLYYZqz3xQ93sx5Te7tpSxFW42BqjMmg/extremeponybr.blogspot.com/warc/extremeponybr.blogspot.com-2021-04-25-0e39a303.cdx
> /ipfs/QmTCWRZmJJQH1YSHUEiog7Ygwawv44ezRztMFWW8eCvXVw/bronymusiciandirectory.blogspot.com/warc/bronymusiciandirectory.blogspot.com-2021-04-01-15c6a631.cdx

 >>/10552/
 >>/10553/
 >>/10554/
That website is even worse now: CFwalled (and maybe sometimes flat-out/plainly 403'd). Cuckflare example: https://web.archive.org/web/20240714193016/https://archive.4plebs.org/tv/thread/180735311 (short thread where OP=">Your honor, I object, when my client said "slam-dunk a nigger baby into a trash can" he actually meant to raise awareness to the many underprivileged african-american youth in his neighbourhood, so that they may take back their social standing by playing basketball instead of doing crimes. \ In his own way, he's an american hero, really.")

----

Some of my tech problems:
A computer that I call "high propagation computer" (HPC) sometimes goes offline, and I think my stupid router is to blame. This isn't a big problem because my main computer (MPC) hosts/seeds the same data as HPC plus more, and MPC is often online. HPC doesn't magically come back online after it logically disconnects; I can't ssh in for one and sometimes multiple days. This sometimes fixes it: disconnecting the Ethernet cable to HPC then reconnecting it. This fixed it recently (physically disconnected for less than a minute). Multiple times over two or more days, I checked if I could ssh in: couldn't. After reconnecting the Ethernet cable that immediately fixed it (I'm pretty sure I didn't misremember that).