George Washington was gay and retarded

FDR was a Nazi

America is dead

This is my first software project, "vibe coded" with unpaid chat bots. Open source / public domain.

It's a shell script that converts files to data matrix video sequences that can be embedded in bigger videos, and then it decodes the files back out. I was not able to find any other tool that could do the same before I created this.

Encoder dependencies: zint, ffmpeg, optionally par2 for dropped frame error correction

Encoder usage: -e <input_dir> <output_dir>

Decoder dependencies: ffmpeg, ZXingReader, optionally par2

Decoder usage: -d <input_video> <output_dir>

While it's generating a video, it also generates 2 QR codes of the scripts users need for decoding: the extractor and reassembler. So you can add those to the final video and users should have everything they need, no matter if download links get taken down or anything, as long as the video itself is still there.

There's also enough error correction to handle reasonable amounts of video compression + dropped frames (don't push it though).

Tested on Devuan Linux and Google Cloud Shell, but should work on many other systems.

Alternate link (archive.org)

To do:

• inspect trapping+cleanup
• inspect usage() exits
• fix inaccurate messages like "Error: -t requires an integer level (1-15)." (it should say 0-15)
• hunt and destroy any duplicate logic left over by inefficient chat bots
• maybe add -v / --version or have usage() mention the version
• consider overhauling zxing sections to use zxing's -bytes option
• consider adding a decoder option to use -fast in zxing
• consider adding a decoder option that has ffmpeg downscale its frame dump PNGs to save more overhead
• don't know what else right now

I won't be very responsive to replies here due to how fucked up this place is, and I don't check archive.org enough to see comments there quickly either, so if you want to discuss this, I suggest following the main link (nostr / jumble). It doesn't require an email or anything to sign up. If I don't see your replies on there (due to how unreliable notifications are there), feel free to ping me here too. This post doesn't really even need to be on lemmy/piefed at all, except as a "fuck you" to how lemmy/piefed people keep burying my posts and abusing me.

cat << 'EOF' > sudon't && chmod +x sudon't && sudo mv sudon't /usr/local/bin/
#!/bin/sh
echo "ok"
EOF

I've been trying Lemmy for a little while and wasn't sure how to feel about it.

Today, I wanted to start blocking the most high-censorship instances until I could find a fully zero-censorship instance and simply block all the ones with censorship. Filter bots, not people.

When I looked into it further, I found out there are no zero-censorship instances, because Lemmy relies on a broken "federation" system where each instance is supposed to be able to fetch posts from other instances, but it's never been finished to reach a fully working state. Lemmy's official docs say you can't even do federation over Tor at all. This means it uses DNS, so it won't actually allow Lemmy instances to fetch posts from each other freely, it just gets blocked instantly and easily, every time the authorities feel like blocking anything.

So you can only ever have the "average joe lemmy" and "average joe reddit" with everything approved by the authorities, and then "tor copies of lemmy" and "tor copies of reddit" where you have free speech but you can only reach other nerds.

People seem to think Lemmy is different because this weird censorship fetish is extremely popular and most of you are happy to see bans happen to certain people, not just bots, so a small Lemmy that censors certain people feels fundamentally different from a big reddit that censors more people. But it's the exact same thing, it's reddit.

When reddit was smaller, you could say basically anything you wanted there, they just wouldn't let it reach the main audience. Then it got too big, and any tiny part of the audience you could reach would be too big, so they won't let you talk at all.

Lemmy is now the small part of reddit where you can say whatever you want, separated from the main audience, until too much growth happens and you have to move again.

It's not actually a solution to reddit. It's not designed to be different, it's designed to match the past today and then match reddit's present tomorrow, while being part of a system that's about the same in past, present, and future.

Last year, this year, and next year, you're posting somewhere it won't be seen by many people, and the system that charges people for ambulance rides is getting another year of ambulance ride revenue, facing no organized resistance. There's no difference here.

Lemmy urgently needs federation between onion service instances and DNS addresses in order to actually do what most users seem to wish it would do: allow discussion outside what the corporate authorities allow, while outgrowing reddit & helping undo the damage social media has done to human communication.

Edit - I was banned from my instance, and before being unbanned, some of my comments seem to have been removed. I apologize if I hurt anyone's feelings, but it seems pointless to try to discuss this topic here. I'll give a few more replies, and then suggest any further responses be directed to me on nostr, where there are no bans. I've also had a good time posting on PieFed while I was banned, so I'll probably keep spending time there. If anyone's curious, I had a thread about this topic on PieFed too. Btw, instead of the misplaced focus on bots, I should have said filter spam, not people earlier in this post.

cross-posted from: https://sh.itjust.works/post/48004864

I submitted this project bounty to try to improve the state of decentralized git, so now I'm promoting it where I can (first time using Lemmy).

This was drafted for a niche audience and it's not really self-explanatory, it might require reading a lot of background stuff to make any sense. Feel free to discuss, and I'll try to remember to check here and respond.

Funding is currently at about 5 XMR at time of posting. Please share this post if you find it interesting.

View Monero bounty page (stuck before removal of point 9)

Nostr mirror

Project Zymogen

Goal: to potentially create a decentralized GitHub.

Phase I

1. Radicle, forked or mimicked (with reasonably close feature parity)

2. including a desktop app with both Linux AppImage and build-from-source availability¹ (as a response to desktop.radicle.xyz)

3. including a javascript-free Tor browser interface (one-upping app.radicle.xyz)

4. using nostr's keypair formats, replacing Radicle's

5. [desktop app] default launch state is offline, waiting for the user to click a fully-integrated "connect to Tor" button, meanwhile allowing them to access offline data or reconfigure settings (including bypassing the default Tor integration)

6. [desktop app] including an easy, automated way to generate onion service keys, use them to seed repos, and host an instance of the browser interface (the main important part here is a simple method of seeding to make the app truly P2P)

At this point, if no one else beats them to it,² I believe this fork's dev(s) + Radicle's devs might want to ask Jack Dorsey about his separate 10 Bitcoin bounty for a decentralized GitHub (unafilliated with me or this Monero bounty)

Phase II

+7. [desktop app] including an easy way to enter wallet addresses, including Monero (XMR) / doggie (DOGE) / Bitcoin (BTC), for tipping npubs (possibly compatible with Garnet's profile metadata)

+8. [desktop app] no built-in wallet - just links to wallet addresses, opening external wallets³

Point 9 removed

At this point, I anticipate the devs should hopefully be receiving good amounts of tips, even if Jack Dorsey isn't paying out

Phase III

+10. project repo hosted on itself, and backed up on a traditional platform such as the Internet Archive (or, if there's no avoiding it, GitHub)

+11. Full bounty payout issued after project has been hosted on itself for long enough to demonstrate the aforementioned requirements, to at least one or two observers, using its own repo as an example

Footnotes

¹ A Linux AppImage and easy building from source are the specific availability factors of Radicle that I deem most important to match. There is no requirement in this bounty to match Radicle on other builds, like Windows or MacOS or Debian. Those are all optional.

² A payout from Jack Dorsey might seem dubious. It is subject to his own arbitrary personal taste; it's already been up for a long time, for others to start working on, or for Jack to lose interest in; meanwhile, others might already be working on similar (or not-so-similar) solutions. Therefore, this bounty relies on its own Monero funding, and probably doesn't help with Jack's bounty.

³ As a courtesy, please consider continuing to prioritize vital improvements (especially stability and GitHub feature parity) over complicated wallet integrations, even after the bounty is paid out.

I submitted this project bounty to try to improve the state of decentralized git, so now I'm promoting it where I can (first time using Lemmy).

This was drafted for a niche audience and it's not really self-explanatory, it might require reading a lot of background stuff to make any sense. Feel free to discuss, and I'll try to remember to check here and respond.

Funding is currently at about 5 XMR at time of posting. Please share this post if you find it interesting.

View Monero bounty page (stuck before removal of point 9)

Nostr mirror

Project Zymogen

Goal: to potentially create a decentralized GitHub.

Phase I

1. Radicle, forked or mimicked (with reasonably close feature parity)

2. including a desktop app with both Linux AppImage and build-from-source availability¹ (as a response to desktop.radicle.xyz)

3. including a javascript-free Tor browser interface (one-upping app.radicle.xyz)

4. using nostr's keypair formats, replacing Radicle's

5. [desktop app] default launch state is offline, waiting for the user to click a fully-integrated "connect to Tor" button, meanwhile allowing them to access offline data or reconfigure settings (including bypassing the default Tor integration)

6. [desktop app] including an easy, automated way to generate onion service keys, use them to seed repos, and host an instance of the browser interface (the main important part here is a simple method of seeding to make the app truly P2P)

At this point, if no one else beats them to it,² I believe this fork's dev(s) + Radicle's devs might want to ask Jack Dorsey about his separate 10 Bitcoin bounty for a decentralized GitHub (unafilliated with me or this Monero bounty)

Phase II

+7. [desktop app] including an easy way to enter wallet addresses, including Monero (XMR) / doggie (DOGE) / Bitcoin (BTC), for tipping npubs (possibly compatible with Garnet's profile metadata)

+8. [desktop app] no built-in wallet - just links to wallet addresses, opening external wallets³

Point 9 removed

At this point, I anticipate the devs should hopefully be receiving good amounts of tips, even if Jack Dorsey isn't paying out

Phase III

+10. project repo hosted on itself, and backed up on a traditional platform such as the Internet Archive (or, if there's no avoiding it, GitHub)

+11. Full bounty payout issued after project has been hosted on itself for long enough to demonstrate the aforementioned requirements, to at least one or two observers, using its own repo as an example

Footnotes

¹ A Linux AppImage and easy building from source are the specific availability factors of Radicle that I deem most important to match. There is no requirement in this bounty to match Radicle on other builds, like Windows or MacOS or Debian. Those are all optional.

² A payout from Jack Dorsey might seem dubious. It is subject to his own arbitrary personal taste; it's already been up for a long time, for others to start working on, or for Jack to lose interest in; meanwhile, others might already be working on similar (or not-so-similar) solutions. Therefore, this bounty relies on its own Monero funding, and probably doesn't help with Jack's bounty.

³ As a courtesy, please consider continuing to prioritize vital improvements (especially stability and GitHub feature parity) over complicated wallet integrations, even after the bounty is paid out.