syllogistic

5 ms·

1.
by syllogistic 3mo ago
Apologies I should have been more precise. What I meant was it doesn't work on the browser support in the way webrtc works on the browser . The point of webrtc on the browser is to establish a peer to peer connection.
2.
by syllogistic 3mo ago
It's backwards! Unlike webrtc, iroh doesn't work inside a browser. It's for the case where you have two native apps that need to talk to each other p2p. For browser / webapps you want webrtc.
3.
by syllogistic 3mo ago
> when will iroh support webrtc... This would give you a native iroh node that also speaks webrtc but I find that what folks want is for browsers to participate as peers. I build p2claw, p2p for self-hosted web apps, and ended up doing b
4.
by syllogistic 3mo ago
PR for the webrtc-rs half is up! https://github.com/webrtc-rs/webrtc/pull/807
5.
by syllogistic 3mo ago
Good to know, thanks! Though maybe I’ll keep my old limits for old browser compatibility.
6.
by syllogistic 3mo ago
Yes! that's the "other reconstruct" I mention on the post. maxMessageSize at least appears in SDP and getStats. We ended up patching both at our client to be safe [800 bytes and 16kb respectively].
7.
by syllogistic 3mo ago
Would agree it's uncommon in general traffic. Rare conditions [webrtc-rs, 1280 class tunnel / tailscale, and ipv6 pair] but deadly when they are met since every connection silently fails. That's what made it worth chasing dow
8.
by syllogistic 3mo ago
Author here, thank you, that means a lot coming from you. Pion was the prior art I pointed the webrtc-rs maintainers at. And pion/sctp#12 is super relevant. A known, proposed fix years before we hit it. "The hardcoding we all sett
9.
by syllogistic 3mo ago
Author here, Agreed. The port-number point is the most plausible rationale I've heard, more convincing than the RFC line in their source comment. The historical fix for "can't classify fragments" was virtual reassembly o
10.
by syllogistic 3mo ago
Author here. This started as a blank page on one device and ended two weeks later at the intersection of two bugs: webrtc-rs hardcodes INITIAL_MTU=1228 [never updated, no path probing, retransmits at the same size forever], and Tailscale&#x
11.
The iPad was on Tailscale: a WebRTC debugging story(p2claw.com)
72 points by syllogistic 3mo ago|36 comments
12.
by syllogistic 3mo ago
How do these results compare with the engram based approach from deepseek?
13.
by syllogistic 3mo ago
Is he headline strictly about subsidized subscriptions? Anthropic announced their first profitable quarter.
14.
by syllogistic 3mo ago
> Just use WINE Did you just tell me to go fuck myself ?
15.
by syllogistic 4mo ago
At the very least this sort of thing [building] can be cathartic. I hope it helped you in your situation and that the process itself made it worth it, even if it doesn't become a thing. I hope it does!
16.
by syllogistic 4mo ago
Had AI help me write a blog post last week. Most of the process was deleting verbosity. I guess it solves the blank page problem but once you get going the noise is worse than doing it yourself.
17.
by syllogistic 4mo ago
Reminds me of my dad's experience with google nest hub a few months ago. He called it the best product google's ever made until an over the air update killed the video call feature he used to talk to his grand kids. Brutal.
18.
by syllogistic 4mo ago
I've gone back and forth too. Your point about the missed learning/re-enforcement opportunity is real, and the temptation to gloss over things is too. That said, I'm starting to think differently about what I consider worth l
19.
Use MSP from chat completions with any model(reddit.com)
1 points by syllogistic 1y ago|1 comments
20.
by syllogistic 1y ago
The LLM SDK *is* the MCP Client
21.
by syllogistic 1y ago
good take overall, though the last point is forgiven as a subtle dig at lafayette
22.
by syllogistic 2y ago
It's in the first sentence of the article too :)
23.
by syllogistic 2y ago
He's not though because cohere stuck the already embedded dataset on huggingface https://huggingface.co/datasets/Cohere/wikipedia-22-12-en-em...
24.
OpenAI Assistant 1 week later: drop-in compatible svc and an OSS implementation(twitter.com)
5 points by syllogistic 3y ago|1 comments
25.
by syllogistic 3y ago
That didn't take very long, is OpenAI's Assistant API the new standard for LLM apps and RAG?
26.
by syllogistic 3y ago
Huh, yeah it repros. Java is faster 159s vs 203s for the 256 tokens on my intel i9 12 gen