vent
You constantly shit talk other projects. You go on huge incoherent rants drowning others out. When people ask you to change something you double down or start shit talking them. When blocked you make new accounts to keep following / ranting at people which is a violation of boundries. When you enter a space you make it instantly more stressful until you finally get kicked out. This is not just me but a pattern others face as well.
Posting on vent post like this is hurtful.
vent
@serapath This sort of stuff is exactly why you keep getting kicked out of groups. Saying that people are "triggered" instead of listening to their feelings and admitting personal fault makes for a toxic interaction. You suck at communicating to a point people block you and then pretend it is their fault. Notice how basically nobody else in the ecosystem causes the issues you do and basically nobody else causes the amount of drama that you do.
Disclaimer: I often wave at #dogs when they are being taken for a walk. Not the owners.
@fleeky Neat, it's less about distributing the load and more about connecting to inference servers. :o Cool use of p2p tho
Hermes3:8b my beloved managed to actually generate a single calculator app and apply a basic update. 🤪 Sadly I have to choose between it and running 1 web app (element.io) or vscode due to only having 12 GB of ram. 😰
Tried getting https://aider.chat/ to generate a commit message using gemma2:2b and it was grossly verbose with loads of useless text.
Might be worth it to try different models to see which ones suck the least.
Something no one talks about enough:
CPU cycles aren't free.
Memory reads and writes aren't free.
That shit takes power. A miniscule amount per instance, yes, but it adds up quick if it's from an app that everyone uses constantly. All that power comes from somewhere, and right now that's mostly fossil fuels.
When people complain about software bloat, it's not just a UX problem, it's an environmental one too.
@jonny I've mostly been reading the source code of @VeilidNetwork and @n0iroh and filling in my gaps on syntax as I go. The error messages in rustc have been pretty handy (except when they're not :P )
I wish vector search as a thing would die, or return to the back seat and let traditional indexing things have the first shot.
"oh but vector search is great because it clusters similar concepts!"
Yeah you know what concepts are similar? Different names, different model numbers for things, things that are related to _but different from_ what I searched for.
If I search for "morgan", a result for "morton" is a bad result. If I search for "atari ste", a result for the atari falcon is bad.
@jonny Honestly the code is pretty yucky RN since I'm in "meet the deadlines" mode
https://github.com/RangerMauve/veilid-iroh-blobs/blob/default/src/iroh.rs#L168
It'd be cool if there was an approach of using "visual embeddings" applied to facial recognition. One could teach their personal agent a face by telling it to read the facial embedding and when encountering people the facial embeddings could be pulled from a regular vector DB instead of trying to train a new recognizer on the face. Probs easier to share data that way too.
@jeremy_list Good point I could probably wrap it in a macro to map the option and flatten it all.
@jeremy_list In this case each layer has a different meaning it's basically Didn't Time Out ( Stream still Open ( IO read didn't fail (Bytes)))
@jonny Maybe, i just have different errors I need to send for each level. I'm wrapping a read from a channel of io results in a timeout.
This week's #Rust type of the day is `Result<Option<Result<Bytes>>>`
Occult Enby that's making local-first software with peer to peer protocols, mesh networks, and the web.
Exploring what a local-first cyberspace might look like in my spare time.