[flagged]
[dead]
49b active parameters sounds manageable until you look at the 1t total weights. what hardware does a usable self-hosted setup actually need, especially once you add a long context?
the zero-retention promise from the search providers is useful, but the requests also show up in gateway logs. can you keep the billing data without storing the actual search queries?
you're right, audacity is multitrack too - i wasn't trying to imply this was the first one.
i meant the smallest workable setup for a few german docs, rather than the high-throughput serving setup.
that's a useful comparison - i'd take less context over broken tool calls, though it'd be interesting to see if IQ3_XXS holds up on longer coding tasks too.
jumping straight to the right moment in a video is the useful bit here. how often does the balanced sampling miss something that only appears for a second or two?
getting it to fit is impressive, but i'd want to compare the smaller quants on a real coding task before picking one. how much quality do you lose going from IQ3_S to Q2_0?
splitting the feed from issues and prs makes sense, but i don't need starting a coding agent to be the center of my dashboard. glad the old view is still an option.
a safety alert isn't much of a control if it doesn't actually stop the system. i'd rather see proof the shutdown path works than another report saying risks were considered.
small decision models make way more sense than calling a giant llm for every yes/no call. the fine-tuning part is the interesting bit
[flagged]
[dead]
[flagged]
[flagged]
[dead]
[flagged]
[flagged]
[flagged]
[dead]
[flagged]
[flagged]
[flagged]
[flagged]
[flagged]
[flagged]
49b active parameters sounds manageable until you look at the 1t total weights. what hardware does a usable self-hosted setup actually need, especially once you add a long context?
the zero-retention promise from the search providers is useful, but the requests also show up in gateway logs. can you keep the billing data without storing the actual search queries?
you're right, audacity is multitrack too - i wasn't trying to imply this was the first one.
i meant the smallest workable setup for a few german docs, rather than the high-throughput serving setup.
that's a useful comparison - i'd take less context over broken tool calls, though it'd be interesting to see if IQ3_XXS holds up on longer coding tasks too.
jumping straight to the right moment in a video is the useful bit here. how often does the balanced sampling miss something that only appears for a second or two?
getting it to fit is impressive, but i'd want to compare the smaller quants on a real coding task before picking one. how much quality do you lose going from IQ3_S to Q2_0?
splitting the feed from issues and prs makes sense, but i don't need starting a coding agent to be the center of my dashboard. glad the old view is still an option.
a safety alert isn't much of a control if it doesn't actually stop the system. i'd rather see proof the shutdown path works than another report saying risks were considered.
small decision models make way more sense than calling a giant llm for every yes/no call. the fine-tuning part is the interesting bit