Hacker Newsnew | past | comments | ask | show | jobs | submit | stevens37's commentslogin

I simply download longer videos with yt-dlp and watch it offline.


Yep. I do this with Brave playlists.


At the moment, Truth Social is available for U.S. users only


No. I went back to twitter. The direction is promising.


I've never heard about them but like this.


yes

openssl enc -e -aes-128-cbc -in ${1} -out ${1}.cr -iter +123456 -k <password>


You can leave your place also for any physical and mental recreation. Otherwise you can buy everything on the internet so this is mainly bad for the local shops. The gov is rather hysterical because of the recent corruption scandal


TOR browser + duckduckgo


Encrypt everything before uploading.


Tips and tricks for doing this the easiest way possible?


Rclone. It has multiple backends and you can chain them: encrypt -> cache locally for performance -> store on backend.


Deja Dup on Linux supports this. Just pick a directory to back up, sign in with your Google Account, and check a box to encrypt your stuff before uploading. Google Drive just sees encrypted chunks with file names like “duplicity.gpg”.


And don't forget to backup the decryption key using an out of band method, such as a USB disk.


Cryptomator has overall a nice clean interface, I find


slow down by 10x (gopro 240fps to 24fps)

ffmpeg -i ${1} -sn -an -c:v libx264 -r 24 -filter:v "setpts=10PTS" -crf 19 ${1}-10x.mkv

reverse video

ffmpeg -i $IFILE -s 3840x2160 -f image2 -q:v 1 -vf format=yuvj420p $tmpdir/p%8d.jpg cat $(ls -t $tmpdir/p.jpg) | ffmpeg -f image2pipe -c:v mjpeg -r 30 -i - -c:v libx264 -crf 18 -vf format=yuv420p -preset slow -f mp4 $OFILE

loop a video: loopcount=$1

ffmpeg -stream_loop $1 -i $2 -c copy $3.mkv


Once (~10-15y ago) I was thinking about a OTP based "2 component glue file sharing solution". You take a piece of data (audio,video), generate a real random one time pad then make an XOR delete the original and share the 2 random files using any media or network. Then share also the info that this and that files are the 2 component glue.


What problem does that solve?

You're doubling the transfer size. Why not just encrypt with a random passcode?

I still don't see the point though. For discoverability/longevity you need seeders. If every transfer has a different hash, then that can't happen.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: