HelloHotel

Yup, real hardware to logical to virtual to logical again, its big unnessary steps.

Without the vm its real hardware to logical With a container, its real hardware to logical to another logical (way easier)

If one enjoys the twisted pain inflicted on children, then inflicting pain that makes most adults want to use eye-bleach by showing off their plunders is to them well executed revenge on the people they dont like.

I wouldve recommended catbox.moe but I have FUD about it now. I assume they are have themselves together, but I cant know for shure.

CSAM sourcing?

Where do these people get that much CSAM. somebody once said that to the best of their understanding, it was new CSAM images each time, meaning not many repeats. My collection of reddit memes costs me ~15-30GB, all of sbubby costs ~5GB. where is it pooled from?

The most fried part of my brain says “One of the big companies trying to absorb the fediverse is doing this to undermine their competition,” but I have zero evidence

Most companies that build CSAM detectors, by nature of their work, have a lot of it. likely thousands of photos and videos were willingly handed over to put into some vault to fight against it’s existance. If its a large corperation attacking is, it nesisarly means a leak from a CSAM vault wether it was intentional (an authorized attack) or not (opsec mistakes or insiders). Or it means there was no vault (negligence) or it wasnt tranfered securely (opsec mistakes).

it’s just the only motive I can even think of beyond it being a rogue crank.

Its not hard to build a bot that scrapes a webpage of its images, they can easly aggrogate that much content over decades.

Good, its an API that can fit diffrent tools even if one is promoted. Upgrading means switching out a binary file. Posix modularization FTW.

Sounds like a useful back-pocket fallback/emergency tool. A thing for when your primary is failing or need more help.

Its a bug in sombodies markdown parsing.

Your URL was somehow HTML escaped.

Correct

…?width=640&height=480

Incorrect

…?width=640&height=480

Some software somwhere has a bug in it and it broke your link, im sorry if i failed to communicate that

Im generally on the side of reposting for archival and continuation. however, the “throw it out there” half-assed ness and lack of transparency of these services make it a no deal. If I were to remake one (and ive thoght about it) a simple “upload and done” approach is discusting. These bots (clarified: probably should create their own instance for the task) need communal love and care to be anything but “a fire hose of content”. I propose the following:

1. Allow the community to control most aspects of the bot behavor.
2. Do not upload/add to queue unless initated by a lemmy user
3. Allow users to vote on post deletion, add resistance or disable if there are many non bot comments.
4. Allow users to vote on the bot’s upload speed and what gets priority (up/down vote this comment)
5. Pin an admin post to act like a “settings menu” for the project
6. Pin an unintrucive admin comment in every post to vote on actions for the post
7. Use as little boilerplate as possable. Hide in spoiler what you cant avoid.
8. Use one bot account for uploads, one blocked user blocks the whole service.
9. Put human and machine readable metadata of the original and repost in a spoiler.
10. Use 8 or so well labeled “sorting bot accounts” to aproimate upvotes of the source relative to its negboring ccomments. Should be no more sway than ±8 votes. Bot votes Should be disclosed in the metadata.
11. Call the bot somthing like “reddit archive” put source’s username in the post/comment body
12. Allow off instance admins to moderate bot posts
13. Prefix all communities with somthing like "auto: " for transparency
14. Allow partial reuploads and omition of threads for admin/data cleanup purposes.

I generally agree, ill add that to the post.

Edit: oh, it was written but poorly explained that it should be its own instance.

Allow off instance admins to moderate bot posts