Open-source, encrypted file vault. | Go/Python/C, SI, BTC, XMR, Hard Tech, Finance, Inspiration. PayNym: +bc1984
Joined August 2025
- Tweets1.8K
- Following821
- Followers314
- Likes17.1K
.@ChairmanSelig: "It’s no longer science fiction to imagine your refrigerator autonomously purchasing your groceries with funds that it earns from launching a memecoin or staking ether."
My icebox will now be harvesting ETH for me so that I can replenish my maple syrup supply on an ongoing basis.
I will not be whitelisting any other smart contracts at this time. But I thank you for your interest.
Arkfile retweeted
You cannot forecast your entire life from where you stand today, the intangible things mean all possibilities remain open. Everything can change. just keep going
Arkfile retweeted
Given the problems with the Tor network, here is a new version for Sentinel.
Also a big thanks to all the contributors!
New Github repo: github.com/Sentinel-Watch-OS…
Or the old APK repository: github.com/wanderingking072/…
Bigger, better and cooler things coming SOON™, stay tuned!
I try to keep prices low. Double-wide ark. Your encrypted objects go into 2 different buckets managed by 2 different vendors. It's sort of like RAID 1 on top of S3 buckets. But only you know the nature of the animals you put onto the ark. (Where we are going, we don't need moats. Just boats.)
Arkfile retweeted
Tried running agents in parallel with worktrees/workspaces today for the first time
I'll admit it, I was falling behind a little, and this *is* a productive coding method
Do I read the code?
Absolutely. I take the time to understand it, open it in my editor, read the type definitions, and pull up the documentation. I ask the agent questions about why it made the decisions it did. The majority of my time is used understanding what the code does and why it is that way.
Are software engineers dead?
Not at all. With such powerful capabilities, I would say software engineers are thriving.
Someone with the mind of an engineer still needs to steer and define the expected outcome. How do you handle a case in which a value is null? A case when something is loading? A specific edge case?
A non-technical vibe coder who lets his swarm of agents freely implement edge case behavior is not leading, but rather being led.
Is software dead?
Nah, this claim is delusional.
Software dies when there is nobody to run it and use it. It'll always be around.
---
I've been using Deepseek v4 with opencode go because I'd rather spend money on ammo then tokens.
Everything is reinforced with strong test coverage, cross checks, manual testing, and manual review. It's working pretty well.
Arkfile retweeted
Ashigaru Desktop 1.5.1 is out.
On Oct 28 the Tor network stopped accepting older Tor versions, so 1.5.0 can’t connect. 1.5.1 bundles Tor 0.4.9.5 and fixes it.
The in-app updater needs Tor, so download manually and verify the signature:
github.com/linkinparkrulz/as…
Arkfile retweeted
Our plan is to port 6th through 10th generation Pixels to Linux 6.18 to entirely phase out requiring the older kernel branches. Having a single kernel branch across all of the supported devices will greatly simplify shipping upstream LTS revisions and hardening the kernel.
Arkfile retweeted
Storage Horoscopes (our monthly series on zodiac signs and their data habits) is back. This month: Scorpio. Full encryption, an air-gapped copy nobody's allowed to ask about, and a very short answer if you try.
Love all these little (high) energy startups and how scrappy they are! ⚡💪
@DarkHorseDRK - $DRK
@BigDigital - $BGDE
@SolunaHoldings - $SLNH
@DigipowerX - $DGXX
@vulcan_infrapwr - $VIP
Arkfile retweeted
We at @DevuanOrg said it in every possible way during the past twelve and more years: UEFI is a trap, adding complexity where its less needed. Same pattern as systemd. arstechnica.com/security/202…
Arkfile retweeted
C.S. Lewis, you must not wait for the perfect conditions
ALT There are always plenty of rivals to our work. We are always falling in love or quarreling, looking for jobs or fearing to lose them, getting ill and recovering, following public affairs. If we let ourselves, we shall always be waiting for some distraction or other to end before we can really get down to our work. The only people who achieve much are those who want knowledge so badly that they seek it while the conditions are still unfavorable. Favorable conditions never come.
Arkfile retweeted
Atenas, circa 1920 (litografía)
1920
Autor desconocido.
Buenas noches con hermosos monumentos
This is the future right here. Payable in BTC-LN and XMR. With no account required.
Many customers asking how to red-team their own codebase.
We just added the @abliteration_ai models (GLM 5.3 and DeepSeek V4.1 Flash, abliterated)
Refusals are removed from the weights, so they work through your security issues instead of declining!
ppq.ai/blog/introducing-abli…
Arkfile retweeted
i have been steadily banging the drum on domestic transformer production since 2023, and now, we have resolute grid. the last time an american company fully designed and built these was in the late 80s. so excited to see this come roaring back. incredible work!
Make TVs Dumb Again
an update on the openai/codex ban:
i was curious about my tv, found a vuln (not with codex), popped a shell, and started poking around. the intrigue of my hobby project while i had the flu wasn't something i could've predicted.
to be clear: the ban almost certainly had nothing to do with using openai -specifically- for my samsung reverse engineering work. i have no reason to believe it did.
the real issue seems deeper. i talked to friends using astra/6.1 sol for both cyber work and normal software tasks. the ones who never hit daybreak (and weren't in the blue program) said they spend a while "warming it up", getting the agent into a flowstate with substitute words and roundabout explanations that jailbreak the context. once that's done, the agent starts talking the same way and skipping tokens.
if you do serious reverse engineering without those jailbreaks, daybreak's content-hidden tripwire looks at the prompt or output in isolation and sees something indistinguishable from malware development.
i think the better fix is making the system track intent across the whole context (and through compressions) instead of punishing blunt technical language.
i believe i got banned because i just used normal terms. talking about memory, trampoline hooks, encrypted/read-protected pages, even entirely locally, looks sinister out of context. once daybreak trips, it poisons the context cache. new conversations start failing too. eventually even normal tooling work and /goals would randomly trip it. arguing your case makes it worse.
the incentives here seem strange to me. people who obfuscate from the start never seem to have problems. people who just use the actual terminology get more and more refusals.
account's still closed. pretty sure it's just from tripping daybreak too many times (even on non-cyber work).
for now i'm moving to open weight models and locking down my own compute. if these tools are part of how you work now, it's worth thinking about how to keep reliable access.
please don't harass tibo, roon or other oai people. from their public comments it sounds like they already know and agree the current setup is too strict.
sorry for the interlude, brb, back to getting the report and a repo out to fix TVs.