重箱の隅 retweeted
やっぱりiPhone Duoにはリモートデスクトップアプリがハマるよなあ!くそう!俺もつくってたんだよ!!!合わせて出そうと思ってたのに審査まる一週間止まってんだよ!!!(昨晩諦めて出しなおした)
こんなのです。審査通ったら出すのでお待ちください…自分で使ってても超べんりです…
casement.win
小さなシンセサイザーとして楽しそうだし、USB MIDIの信号だせるので、CodexとかClaude Codeのスイッチャーとして使えそう。ポチるか悩んでいる。マイクが付いてたら最高だったんだけど
Gamma – this.is.NOISE inc
thisisnoiseinc.com/pages/gam…
The amount of cred Google lost by abandoning Google Reader cannot be underestimated. Frankly, I'm still sore about it. After all these years, and it's still a headline.
Thanks Tailscale.
I just built one in fact, but I want to refactor it to be more performant so I'm checking out your blog post and IndyDevDan's post about Pi durable, since he just built one too.
Google Reader might be dead, but RSS is alive and well.
Build your own RSS hub with Tailscale. Read what you want, from any browser, without exposing it to the open web.
Build a thing. Escape the algorithms.
More on the blog:
buff.ly/WAVWiu5
重箱の隅 retweeted
Today we announce 1Password for Agents platform, building with companies @Muse, SpaceX Super Intelligence Grok @Bot, @AnthropicAI’s @Claudeai, @OpenAI, @TownAI, @Browserbase, @Browser_use, @heydana_ai, Instinct, @usekernel, @Perplexity_ai, @tryramp, @Tomo, and @wajo_ai, with more integrations on the way. 🎉
We've heard from so many of our customers who want to use these new personal AI agents to help them get more done, but want more control over what the agent can access with the same trust and ease of use they get when using 1Password directly.
1Password for Agents gives your agents access without giving up your passwords. When an agent reaches a sign-in form, it requests a credential from your vault. If you approve the request, 1Password directly auto-fills the credential in the destination site so the agent can’t see or take possession of the credentials.
The agent gets the task done, but it doesn’t get your passwords..
You stay in control. 1Password for Agents free and optional for personal and family accounts. Unless you opt-in to an agent connector, agents cannot touch your vault.
➡️Learn more: bit.ly/487da6J
重箱の隅 retweeted
スタートアップが事業をピボットしていくわかりやすい例
とあるスタートアップがVCから2億円調達して、すべて溶かした話。かなり赤裸々で学びが多い…
事業領域は当時急成長していたダークストア(1枚目)
・シード相場の4倍以上となる2億円を調達
・アプリリリース後は初日から注文が殺到し、エンジニアも倉庫で実働(2・3枚目)
・App Storeで4.8点を獲得するも、エリア客単価の差に打ちのめされ事業クローズを決断(4枚目)
クローズ発表当日に大手小売・大手ECなどから買収オファーが来たのに、それを蹴った話までリアルです。
その後のピボットした事業領域はぜひ記事で。
-
出典:ダークストアのスタートアップがVCから2億円調達して全て溶かした話
mesh-ai.net/blog/introductio…
重箱の隅 retweeted
Announcing Expo Desktop v1! It supports creating apps from templates, Prebuild, CNG, "run macos" / "run windows" commands, and more! 🎉
… And I made a docs website to go with it! Link below.
重箱の隅 retweeted
If your Android app relies on OkHttp (directly or via Retrofit/Ktor), you might be exposed to recent certificate authority vulnerabilities until platform roots are patched. Here's how to use a custom HostnameVerifier as a quick application-layer workaround: publicobject.com/2026/10/20/… #AndroidDev #OkHttp
重箱の隅 retweeted
【日経特報】選挙の偽情報対策、SNS事業者に収益化停止促す 総務省指針案
nikkei.com/article/DGXZQOUA2…
重箱の隅 retweeted
Seeing a lot of people freak out about Apple's new guideline 2.5.19, so quick clarification:
OTA updates are still allowed.
2.5.19 isn't a new policy. Apple's own changelog says it "clarifies long-standing policy" that used to live in 2.3.1.
What it goes after is bait and switch: apps that hide features from App Review and turn them on after approval.
Pushing an OTA update to fix a bug is totally fine.
Using it to sneak in a feature Apple never reviewed can get you kicked out.
If you were using OTAs the right way, nothing changed for you.
「O'Reillyが公式のMCPサーバーを出している」「気になる本を気軽に読めることの費用対効果は思っていたより大きい」 / “技術書を年に数冊しか買わない自分に、O'Reillyのサブスク年$150は割に合うか(ACM経由で契約してMCPまで)” htn.to/2aebHWgYww
重箱の隅 retweeted
ソフトウェアファクトリーは、多分1週間ほどあれば作れます。信頼性が高いと判断できたら本稼働。生産量は10倍になります。
同時にトークン代も、CIコストも10倍です。
もしそれで売り上げがかわらないなら、コストが10倍になっただけなので、本来の意味での生産性は1/10に下がります。
どうする?
重箱の隅 retweeted
Apple can now delete your whole developer account for a feature hidden in your binary. On Friday it became a separate rule, 2.5.19.
Apple already rejected one of my apps for this. I'd left three testing switches in the release build: screenshots-mode, slow-entitlement, UnlockedMockPurchases. Nobody could reach them from the App Store, but Apple wrote that they "appear to have been intentionally hidden".
Now I run strings on every archive before I upload.

ALT App Store Connect message from Apple on 2026-09-08 about Snowball Debt Payoff Planner: Guideline 5.6, Developer Code of Conduct. Issue description: We've identified a pattern of unusual behavior with the app that is commonly associated with fraudulent activity. Specifically, the app contains features that appear to have been intentionally hidden during the review process. Manipulative and misleading behavior is not consistent with the guideline 5.6.
SDK 58 is out 🙌
This SDK is built for iOS 27. Apps on SDK 58 will be ready for Duo on day one 📖.
The release also includes App Intents for Siri, 2x faster clean Android builds, faster Expo modules, and a CLI built for your coding agent.
Changelog: expo.dev/changelog/sdk-58
Upgrade: 𝚗𝚙𝚡 𝚎𝚡𝚙𝚘 𝚒𝚗𝚜𝚝𝚊𝚕𝚕 𝚎𝚡𝚙𝚘@^𝟻𝟾.0.0 --𝚏𝚒𝚡
Replying to @vkryukov
well you can also think of it as token efficiency. for example if your agents can’t verify their work, chances are there will be a lot of bugs and rework that needs to happen later, which also requires more tokens (and unhappy customers)
there’s also many ways to improve ttr deterministically, like with a high quality test suite, using libraries like XState (from @DavidKPiano) or @EffectTS_ to make it easier to enforce business logic invariants, etc. your codebase is a form of memory and an input to agents


























