Avatar
Technical Debt
abaa09dab1fc3fffc1409fdb28b13832cd4031704c4df6198525fa7ea466bed2
Will code 4 food.

I think the ā€œnear zero latencyā€ is still a valid UX concern.

Do you know if it’s possible to setup a webtorrent library in a way that it is forced to try fetching from HTTP the first couple of chunks and only after a short delay fire up the lookup for seeders?

I wonder if it would be a proper solution to fetch the first X chunks of a video from a blossom server, possibly at a lower quality, and then switch to something else if the user continues on that video instead of swapping again.

I mean, that should give you both low latency withoug giving up on lower distribution costs, just need to work out the complexity cost of such a solution that is.

Replying to Avatar jb55

I've seen similar services but I wonder what does it imply?

I mean, selling a managed server is great but it sounds like the biggest selling point is ā€œhey you can pay ICANN to give you a pretty name on the web and we do the restā€.

Ok, I guess my beef is with promoting central points of failure such as DNS, into a ā€œproperly decentralizedā€ protocol such as #nostr

You see, the ā€œfediverseā€ ties users into a single instance because DNS is integral to their protocol so ā€œwhateverā€ but nostr is truly permissionless, provider indepentent accounts, everything great about p2p without the bloat (ssb I’m looking at you).

Many projects do both ways, the ā€œlocalā€ flake on the repo serves as a source of bleeding edge package and ā€œblessed dev envā€ (specially useful when combined with direnv, because you just git clone, direnv allow and then get to business) while nixpkgs hosts the lastest release/stable version.

It welcomes testers without alienating everyone else.

For me most of the value from flakes came from two things:

- Coherent setup across multiple computers (including home-manager, nix-darwin and nixOS of course, be it on servers or desktop)

- Reproducible dev envs without host contamination: this one was a blessing when working with a team on proprietary stuff with a bunch of very specifc deps/setup/etc.

I guess nix ā€œaloneā€ fixed enough shit for nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s that the time investment to get into the flake train may not sound as appealing as it does for the rest of us.

Heck, I myself was a little hesitant to jump into the flakes train because of the ā€œexperimentalā€ feature flag it’s attached to.

True, but I think you need to open a LN channel for that to work.

Might be worth looking into Alby Hub and ZEUS.

Judging by the hashtag list, engagement bait/ā€œSEOā€.

nostr:npub1zm6ae3wyzpfdrjespjjmv5jtj425qlpt3fh8xzgg0ccm9rz9fqzsrwhn0a

The mistake that both the vibecoder practitioners and the neo-luddites make is thinking that the primary use of AI in #vibecode is to write lines of code.

For best results, you bounce off the model to develop the design, structure and methodology.

The lines of code that come after are an afterthought.

I have been a commercial programmer last century, and I understand the saying;

"Weeks of coding can save you hours of planning"

I'm happy to bet, that is still the ethos of "real" #programmer

#CodeMonkey

I wonder if anybody has written a guide like ā€œhow to vibe code for programmersā€.

For instance, I gave up trying to keep up with AI news, mostly seem to never get anything real done when using AI, yet, somehow, there are people here on #nostr delivering opensource libs/tools through the magic of ā€œvibe codeā€.

So I, despite being on my late 20s, feel really ancient, like am I not able to adapt anymore..?

āŽ fuck you money

āœ… self intercourse currency

I don’t know about videos but it would be nice if we converted image files into JPEG XL, because it has inherited a party trick from FLIF where you only need to i.e. download half of the file to have half of the resolution.

Should save on bandwidth and file storage, since you don’t need redundant tumbnails and alternative resolution files.

https://flif.info/animation.html

Why is it that media shared on #nostr relies on ā€œsome dude’s HTTP serverā€ instead of, IDK, distributed over IPFS, WebTorrent, MetaLink or something along those lines?

It seems that the older a post is, the less likely it is for the server hosting the linked media to still be up, so unless there’s some kind of The Internet Archive bot crawling Nostr, these are lost for good.

I haven’t looked into the Nostr protocol yet, so I’m assuming media is attatched to posts using plain links, without some metadata including the file hash, which leads to another point of concern: a rogue media server could silently change the linked media.

I would love to be proved wrong though.

Replying to Avatar corndalorian

Now I feel called out because of the state joke I posted earlier.

A functional programmer, an anarchist and a nixOS user walk into a bar.

These are all the same person and he won’t stop talking about state.

Oh god please make him stop.