dpc_01234

It's easier than ever to build p2p software. E.g. You can use Pkarr as a distributed identity system, and Iroh for reliable p2p connectivity.

There's no point in messing with custom hardware, etc. We could host bunch of redundant p2p access points for everyone, and use p2p portable software for everything.

E.g. I'm building a P2P/F2F Social Media protocol that is very close to syndication platform. https://app.radicle.xyz/nodes/radicle.dpc.pw/rad:zzK566qFsZn... . I'm not saying that it's exactly the same thing as author is looking for, but the technical bits and even functionality are very close.

What's the stat of single-compiler version ABI? I mean - if the compiler guaranteed that for the same version of the compiler the ABI can work, we could potentially use dynamic linking for a lot of things (speed up iterative development) without committing to any long term stable API or going through C ABI for everything.

BBC is propaganda outlet. Don't fall for war drums, worry about your own oppressive rulling class.

Nope. It's only Signal.

Ah, the 4o, the first beer bottle for humans. https://www.npr.org/sections/krulwich/2013/06/19/193493225/t...

I more mindfully played a bit with my Element (web UI), and Element X (Android), and while there might something to it, and I suspect the e2e encrypted data model will always lead to some extra work required. Element seems a bit sluggish. However Element X on my Android seems butter smooth.

And event the slower Element seems far better than Discord that I'm forced to use, where I can't even scroll history without the whole thing stuttering.

"Slow" in what sense? Development? Because I self host a Conduit server and I don't ever notice messages being slow. It would be hard to notice anyway, as in a group chat people usually take some time to type in their responses.

The sync between large groups used to be slow because of amount of data, but Element X and "sliding windows" were rolled out to help with it.

AFAIK, the public Matrix server used to be slow because of a heavy load (I think), but on my self-hosted instance that's not a problem at all.

Signal Desktop is having its db corrupted every other time I launch it, and wants me to reconnect to the phone. The UX is OKish.

Cool! That would pair well with SelfCI's MQ daemon, preventing accidentally forgetting about merging in stuff without running the local CI.

> automatic branching and workflow stuff is optional. the core idea is great.

I'm not sure if I fully understood. But SelfCI's Merge-Queue (mq) daemon has a built-in hook system, so it's possible to do custom stuff at certain points. So probably you should be able to implement it already, or it might require couple of minor tweaks (should be easy to do on SelfCI side after some discussion).

> Do you have any other higher level architecture/overview documentation other than what is in that repo?

SelfCI is _very_ minimal by design. There isn't really all that much to document other than what is described in the README.

> Also, how do you like Radicle?

I enjoy that it's p2p, and it works for me in this respect. Personally I disagree with it attempt to duplicate other features of GitHub-like forge, instead of the original collaborate model of Linux kernel that git was built for. I think it should try to replicate something more like SourceHut, mailinglist thread, communication that includes patches, etc. But I did not really _collaborated_ much using Radicle yet, I just push and pull stuff from it and it works for that just fine.

BTW. Pre-commit hooks are the wrong way to go about this stuff.

I'm advocating for JJ to build a proper daemon that runs "checks" per change in the background. So you don't run pre-commit checks when committing. They just happen in the background, and when by the time you get to sharing your changes, you get all the things verified for you for each change/commit, effortlessly without you wasting time or needing to do anything special.

I have something a bit like that implemented in SelfCI (a minimalistic local-first Unix-philosophy-abiding CI) https://app.radicle.xyz/nodes/radicle.dpc.pw/rad%3Az2tDzYbAX... and it replaced my use of pre-commit hooks entirely. And users already told me that it does feel like commit hooks done right.

Should be 50% at least.

Oh, now ios users are an oppressed group. How cute.

I don't get it. Article titled "Common misunderstanding". OK. “There are too many meetings”. How is this a misunderstanding? "...bunch of excuses confirming there are too many meetings...". Yyy... so it's not a misunderstanding?

The US government entered a debt spiral a while ago (https://fred.stlouisfed.org/series/A091RC1Q027SBEA), and needs lower interest rates to service its tremendous debt while trying to inflate it away by printing money. That's all it comes down to. For decades fiscal conservatives were warning about it and were laughed at. Now that we're are the end game the inevitable shitshow will become apparent. You can hate Trump (rightly so), but as much as he did contribute to the problem directly, the problem is larger and systemic, and anyone else in office would have the exact same problem now.

Well, it's not like it never happened to me to "burn tokens" with some lifetime issue. :D But yeah, if you're working in Rust on something with sharp edges, LLM will get get hurt. I just don't tend to have these in my projects.

Even more basic failure mode. I told it to convert/copy a bit (1k LOC) of blocking code into a new module and convert to async. It just couldn't do a proper 1:1 logical _copy_. But when I manually `cp <src> <dst>` the file and then told it to convert that to async and fix issues, it did it 100% correct. Because fundamentally it's just non-deterministic pattern generator.

Might be obviously, but there is definitely a lot of biases in the data here. It's unavoidable. E.g. many bugs will not be detected, but they will be removed when the code is rewritten. So code that is refactored more often will have lower age of fixed bugs. Components/subsystems that are heavily used will detect bugs faster. Some subsystems by their very nature can tolerate bugs more, while some by necessity will need to be more correct (like bpf).

> We have an in-house, Rust-based proxy server. Claude is unable to contribute to it meaningfully outside

I have a great time using Claude Code in Rust projects, so I know it's not about the language exactly.

My working model is is that since LLM are basically inference/correlation based, the more you deviate from the mainstream corpus of training data, the more confused LLM gets. Because LLM doesn't "understand" anything. But if it was trained on a lot of things kind of like the problem, it can match the patterns just fine, and it can generalize over a lot layers, including programming languages.

Also I've noticed that it can get confused about stupid stuff. E.g. I had two different things named kind of the same in two parts of the codebase, and it would constantly stumble on conflating them. Changing the name in the codebase immediately improved it.

So yeah, we've got another potentially powerful tool that requires understanding how it works under the hood to be useful. Kind of like git.

It's not about memory/CPU/IO, but latency vs throughput. Most software is slow because it ignores the latency. If you program serially waiting for _whatever_ it is going to be slow. If you scatter your data around memory, or read from disk in small chunks, or make tons of tiny queries to the DB serially your software will be 99.9% waiting idle for something to finish. That's it. If you can organize your data linearly in memory and/or work on batches of it at the time and/or parallelize stuff and/or batch your IO, it is going to be fast.

Totalitarians on one side convince their side, that it's totally fine and desirable to ignore the law and let millions of illegal immigrants in. Then then totalitarians on the other side convince their side it is necessary to ignore the law and introduce wide sweeping surveillance to undo it. Congratulations, both sides cooperated while hating each other because they are easy to play dummies.

Error log level should be renamed. It's just a terrible name that confuses usage.

Did your Roombas also yelled in the middle of the night "PLEASE CHARGE ROOMBA!!!" every few minutes with no way to disable that behavior?

I now have 2x $150 iLifes and couldn't be happier. They're also imperfect, but they are affordable and simple.

Right buffer is a relative obvious and simple idea. For some reason the Java-OOP crowd keeps thinking that LMAX deserves a nobel price for being neither first nor last to use it.

> have to go out of my way

Yeah, that's exactly the annoying part. Can't mention ring buffer ever without someone bring up LMAX. "But do you know, that some Java developers somewhere once wrote something that didn't completely ruin the hardware performance?! It's stunning and amazing."

This does not seem to be a license, only a plea.

For all these "Please charge Rumba!!!" in the middle of the night, good riddance.

Dandelion is used to improve privacy of broadcasting (cryptocurrency transactions) and comparing it to Tor is confusing. Tor is trying to hide who is talking with who, Dandylion hide who is the originator of a message that everyone will receive.

I'm a happy NextDNS user. I'm not sure what kind of support you need that wouldn't be solved by asking AI and/or some community online. They have wonderful integrations, instructions, documentation and features. Blocking ads is not even primary reason I use them - the parental control and safety features are the main reason for me.

Is _everything_ working? Last time I put Linux on a x86_64 Air Book I was given for free, everything was working _except_ resume from suspend would crash and reboot the system, and from the reading on it, it seems it is a know issue due to T4 security chip or something. Made me believe that if older chips doesn't yet work, the newer ones probably have more caveats. Or am I wrong?

Generally I'm reluctant investing in Linux on a hardware from company more or less hostile to it, but I also don't have any need for ARM laptop, and I'm happy with my Framework.

Programming with Rust and deployment and mgmt with Nix is so much better to how things used to be. Did I mention how much better my Helix works than how Neovim used to? Revision control with JJ, conflict resolution with mergiraf. My personal computers are more powerful than ever before and can get amazing stuff done super fast.

Everything is better and keeps getting better if you make good decision instead of following the lowest common denominator tech.