Been working on improvements to GLM 5.3 Flash on TensorFold Zig...
...but DeepSeek-V4.1-Flash-1017 keeps bringing me back.
It's so fast, and good.
Check out my recipe fork, which hopefully gets into @MiaAI_lab's main soon, with KV sharding and more.
...but DeepSeek-V4.1-Flash-1017 keeps bringing me back.
It's so fast, and good.
Check out my recipe fork, which hopefully gets into @MiaAI_lab's main soon, with KV sharding and more.
@yume_arasaki @ivanfioravanti Give it a try! Temp of 0 vs 0.7 does have a factor and @MiaAI_lab's Sparkdash changed defaults
github.com/wojo/DeepSeek-…
3
0
9
1,108
@MiaAI_lab Oh man, it got merged on the 24th. I've been busy. Rock on @MiaAI_lab 🤘
0
0
2
43
wojo retweeted
Starting today, eligible ChatGPT Pro and Business subscribers can claim up to $500 per month in API credits to build apps and agents.
627
804
9,176
2,064,838
wojo retweeted
Tailscale replied on Reddit:
Hi folks, Mike Shaver here, VP of Engineering at Tailscale.
We've seen the concerns about Tailscale SSH and wanted to share what we know so far.
If you want to jump to the most important part, based on our current assessment, we're not recommending that everyone disable Tailscale SSH.
We've now received the researcher's report and are reviewing it. Our engineering and security teams had already been investigating independently, with help from external security specialists. That work has identified issues we're working to fix. We're still validating the full scope, including which configurations are affected.
A bit of technical context:
Tailscale SSH uses your tailnet's access policies to control who can connect to which machines. Most of the issues we've identified so far concern what happens after someone has been authorized to connect, particularly how Unix privileges and SSH forwarding are handled. In some cases, a session may be able to do more than the configured local user should be allowed to do.
While it’s a serious concern, it isn't the same as an unauthenticated attacker being able to connect to arbitrary machines, but the potential impact depends on how SSH access is configured. We're still investigating, so we don't want to make blanket claims about what's affected or not.
Again, based on our current assessment, we're not recommending that everyone disable Tailscale SSH.
In the meantime, there are a few precautions you can take:
•Review your SSH access policies. Make sure only the people and devices that need access have it.
•Review SSH forwarding permissions and remove access you don't need.
•Consider enabling SSH check mode for an additional authentication step. This won't fix privilege escalation issues, but it does add another barrier to gaining access.
•Enable automatic updates where supported so you can pick up fixes when they're released.
For particularly sensitive systems, consider temporarily tightening your Tailscale SSH access policies while we investigate, so that only the specific users and devices that need access can connect.
We're working on fixes and testing them carefully. We'll publish a security advisory explaining the confirmed findings, affected configurations, recommended actions and available patches. We'll also follow up with a more detailed technical write-up.
If we find anything that changes our assessment or requires immediate customer action, we'll communicate that.
We know it's been a rough week for security teams, and we understand why people are concerned. We'd rather give you the technical context we have than speculate about things we haven't confirmed yet.
We'll share more as we verify the details. If you have any questions about how this relates to your particular environment, please get in touch with our team tailscale.com/contact/suppor…
Hi folks, Mike Shaver here, VP of Engineering at Tailscale.
We've seen the concerns about Tailscale SSH and wanted to share what we know so far.
If you want to jump to the most important part, based on our current assessment, we're not recommending that everyone disable Tailscale SSH.
We've now received the researcher's report and are reviewing it. Our engineering and security teams had already been investigating independently, with help from external security specialists. That work has identified issues we're working to fix. We're still validating the full scope, including which configurations are affected.
A bit of technical context:
Tailscale SSH uses your tailnet's access policies to control who can connect to which machines. Most of the issues we've identified so far concern what happens after someone has been authorized to connect, particularly how Unix privileges and SSH forwarding are handled. In some cases, a session may be able to do more than the configured local user should be allowed to do.
While it’s a serious concern, it isn't the same as an unauthenticated attacker being able to connect to arbitrary machines, but the potential impact depends on how SSH access is configured. We're still investigating, so we don't want to make blanket claims about what's affected or not.
Again, based on our current assessment, we're not recommending that everyone disable Tailscale SSH.
In the meantime, there are a few precautions you can take:
•Review your SSH access policies. Make sure only the people and devices that need access have it.
•Review SSH forwarding permissions and remove access you don't need.
•Consider enabling SSH check mode for an additional authentication step. This won't fix privilege escalation issues, but it does add another barrier to gaining access.
•Enable automatic updates where supported so you can pick up fixes when they're released.
For particularly sensitive systems, consider temporarily tightening your Tailscale SSH access policies while we investigate, so that only the specific users and devices that need access can connect.
We're working on fixes and testing them carefully. We'll publish a security advisory explaining the confirmed findings, affected configurations, recommended actions and available patches. We'll also follow up with a more detailed technical write-up.
If we find anything that changes our assessment or requires immediate customer action, we'll communicate that.
We know it's been a rough week for security teams, and we understand why people are concerned. We'd rather give you the technical context we have than speculate about things we haven't confirmed yet.
We'll share more as we verify the details. If you have any questions about how this relates to your particular environment, please get in touch with our team tailscale.com/contact/suppor…
15
65
657
178,348
Assume all your devices on your network will be compromised.
Either by a bad actor, or an entity like Samsung. Wait... what's the difference?
INVEST IN LOCAL OPSEC
Either by a bad actor, or an entity like Samsung. Wait... what's the difference?
INVEST IN LOCAL OPSEC
i own a relatively new (2025) samsung tv.
i kept getting weirdly targeted ads.
i tried reversing the firmware but it was aes encrypted and no keys unless tear it apart and do uart/jtag magic.
zero days it is. root shell on new samsung TVs!
discovered PRIVACY HORROR. write up?
0
0
0
94
wojo retweeted
The r/OpenSource subreddit has officially banned anything using AI. In any way. Violators will be permanently banned.
Which means… r/OpenSource will ban anyone submitting anything that, in any way, involves… the Linux kernel.
reddit.com/r/opensource/c…
Which means… r/OpenSource will ban anyone submitting anything that, in any way, involves… the Linux kernel.
reddit.com/r/opensource/c…
472
271
5,641
627,422
In addition to using Tailnet Lock, analyze your Tailscale ACLs and keep minimum access principles even for your internal network!
I also recommend going deeper and separating your IoT devices on VLANs. Your agent can help you out. There are no excuses anymore!
I also recommend going deeper and separating your IoT devices on VLANs. Your agent can help you out. There are no excuses anymore!
Hey fellow Tailscale loving friends, with all the security shenanigans going on here’s a prompt I recommend for making sure the weakest link on your talilnet can’t wreck everything else over ssh or otherwise.
Give your agent this and let it walk you thru locking down your ACL:
x
6
12
271
23,631
You COULD run Headscale, too, but will you do a better job at hosting than Tailscale + security of Tailnet Lock?
Doubt it.
More info on Tailnet Lock: tailscale.com/docs/features/…
Doubt it.
More info on Tailnet Lock: tailscale.com/docs/features/…
1
0
40
14,498
5.2M by reclaiming the video RAM. Added to my main for now as default off, but flip it on if you don't have a need for video!
github.com/wojo/DeepSeek-…
github.com/wojo/DeepSeek-…
1
0
1
595
wojo retweeted
if this PHP vulnerability allows remote code execution, doesn't that mean we can use the vulnerability to auto-patch all vulnerable servers?
386
1,748
21,877
1,366,671
Ported my KV sharding, NVMe spill v2 and other improvements to DeepSeek-V4.1 Flash 1017 recipe by @MiaAI_lab running @ashxhart's TensorFold on Zig.
2x DGX Sparks reach 2.1M tokens of KV (two full 1M contexts!), block-based NVMe spill that handles forks and rewinds, and a 237k chat resumes from disk in 1.7s vs 2m!
2x DGX Sparks reach 2.1M tokens of KV (two full 1M contexts!), block-based NVMe spill that handles forks and rewinds, and a 237k chat resumes from disk in 1.7s vs 2m!
7
4
47
4,428
Nerfing kernel work. Now refusing to load local ablit models. This is the trend of "safeguards" from the frontier.
What makes the few at the top think they know what's best for us?
I'm trying to protect and safeguard my assets from others that don't respect these imposed safeguards!
If it's not illegal, back off and let us build.
What makes the few at the top think they know what's best for us?
I'm trying to protect and safeguard my assets from others that don't respect these imposed safeguards!
If it's not illegal, back off and let us build.
A few days ago opus would load and unload abliterated models no problem, from yesterday it started to refuse everything, it won’t even look at it now
1
0
3
382