nycki

joined 1 year ago
[–] nycki@lemmy.world 18 points 2 months ago (4 children)

i want to like this but I have to assume anyone still using pepe against the creator's wishes is a shitbag

[–] nycki@lemmy.world 6 points 3 months ago (5 children)

Why is this on c/Technology? Musk isn't twitter and twitter isn't tech news.

[–] nycki@lemmy.world 6 points 3 months ago

the phrase "opt-in consent" is sickening. if its not opt-in then, legally, it shouldn't be consent at all. I hate that we have to clarify.

[–] nycki@lemmy.world 25 points 3 months ago (1 children)

Why is this in c/Technology?

[–] nycki@lemmy.world 1 points 3 months ago

That's exactly what I thought would work, but it doesn't.

[–] nycki@lemmy.world 1 points 3 months ago (2 children)

I'm using a regular off-the-shelf tape recorder, it doesnt have an electronic interface, I just press play and record manually.

[–] nycki@lemmy.world 1 points 3 months ago (5 children)

I did use par2 and tar to generate redundancy, but I still need a way to locate it in the bytestream. Tar doesn't seem to reliably mark the start or end of files :/

[–] nycki@lemmy.world 2 points 3 months ago (1 children)

I tried that first! But tar complains if it can't find the file header! So I still need to do some sort of packets. Unless you know some sort of workaround?

 

I'm currently trying to set up a homebrew cassette tape storage format, but trying to use existing tech where possible. I was excited to see that minimodem already exists for converting an audio stream to a byte stream, and is even available in termux for android, so I could decode cassettes with my phone! However, I'd like some sort of higher-level tool to encode and decode "packets" or "slices" so that I can add error correction. I'm sure this sort of thing must exist for amature radio purposes.

I could write a script that cuts a file into slices, with checksums and redundancy for each slice, and then pads them with null bytes so I can isolate each frame when decoding. What I want is to find out if that's already been done. I've heard of AX.25 packets but I can't find a tool that does that with stdio.

[–] nycki@lemmy.world 14 points 5 months ago

syncthing is the easy option if you have some files you always want to have on both. if you just want to access your desktop files from your phone, I recommend Cx File Explorer for Android, it's a file browser that supports various network file share protocols including Samba and SFTP.

[–] nycki@lemmy.world 11 points 5 months ago

I dont. Its honestly not great. I'd rather that effort went to preserving and repairing the existing tools of the free and open web -- the old protocols are extensible. Imagine if we had an RSS client with a "reblog" feature!

"Federation" adds overhead and honestly creates as many problems as it solves. It's not a selling point, its a price tag.

[–] nycki@lemmy.world 49 points 7 months ago* (last edited 7 months ago) (2 children)

Starting anything from scratch is a huge risk these days. At best you'll have something like the python 2 -> 3 ~~rewrite~~ overhaul (leaving scraps of legacy code all over the place), at worst you'll have something like gnome/kde (where the community schisms rather than adopting a new standard). I would say that most of the time, there are only two ways to get a new standard to reach mass adoption.

  1. Retrofit everything. Extend old APIs where possible. Build your new layer on top of https, or javascript, or ascii, or something else that already has widespread adoption. Make a clear upgrade path for old users, but maintain compatibility for as long as possible.

  2. Buy 99% of the market and declare yourself king (cough cough chromium).

[–] nycki@lemmy.world 5 points 9 months ago

optional autocomplete is a nice-to-have, eager autocomplete is a pain in the ass. as long as it only completes when I ask it to, I don't mind.

view more: next ›