Thaw Update: 2.0.0 Incoming, macOS 27 Support, & Built-In Privacy #854
Pinned
diazdesandi
announced in
Announcements
Replies: 3 comments 19 replies
|
@diazdesandi BTW, will you guys publish a few 2.0.0 RC builds before the final release, so we can test all the fixes together instead of using individual debug builds? |
11 replies
|
Is it just me or is there still several problems with the Thaw bar needing to respring all the apps which locks my cursor and is a huge annoyance. I do have the option to Prompt me each time Thaw wants to reload all my programs, but to do so takes a lot of time and resources |
5 replies
|
Can you describe more about your setup? Is this one monitor? Multiple? Is
it happening when you unplug and replug? Randomly? Anything like that tends
to help.
…On Mon, Aug 10, 2026 at 8:11 AM Andrew Chepurny ***@***.***> wrote:
Its gotten demonstrably worse in rc-2.1 (49). Seems to be aggravated when
I have to switch monitor arrangements/layouts.
I was able to reproduce the behavior and log it to debug logs... I would
file an Issue but I'm honestly not 100% sure how to even describe the
problem let alone the EXACT step to reproduce it.
thaw_2026-08-10_11-08-29.log
<https://github.com/user-attachments/files/30904219/thaw_2026-08-10_11-08-29.log>
—
Reply to this email directly, view it on GitHub
<#854?email_source=notifications&email_token=AB7VZC5YWO4HJNBZ3GOB7ED5JHQ2DA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNZZGY2DOMZVUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSWGM33PORSXEX3DNRUWG2Y#discussioncomment-17964735>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB7VZC2UWXXV22CGYGJCEO35JHQ2DAVCNFSNUABJKJSXA33TNF2G64TZHMYTCNBVGM3TIOBRHA5UI2LTMN2XG43JN5XDWMJQGUZDGOBWGCQXMAQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
We’ve been dealing with several things in parallel:
Integrations: Raycast and Droppy
thaw://automation surface.thaw://already works with Alfred today; what’s left is a packaged, installable workflow.Outside the app (and worth knowing)
We’ve been hardening the project around contributors, releases, and trust, not just features:
Signed-off-byunder the Developer Certificate of Origin. This isn’t a CLA; it’s an attestation that you can contribute the change under GPL-3.0 (including AI-assisted work you’re responsible for).docs/: architecture, assurance case, release process, URI schemes, hidden flags, roadmap.OpenSSF: what the scores mean
OpenSSF gives two related but different signals:
Together: Best Practices is “are we doing the right things on paper and in process?”; Scorecard is “does the repo look healthy to automated scrutiny?” We’re investing in both because Thaw asks for powerful permissions. Users should be able to verify what they’re installing and how the project is maintained. We’re also going to keep expanding into third-party open source certifications. Most apps don’t pursue them, and menu bar managers basically don’t at all. SLSA is our next objective.
Idea: “What Thaw sees”
For 2.1.0 we’re considering a verification mode where users can see the untreated screen capture Thaw is working from: literally “what Thaw sees” so far. Goal: make capture inspectable, not more opaque. You grant the permission, you should also be able to confirm the scope of what the app observes.
Feedback and questions welcome on any of the above. The goal is transparency and contribution.
All reactions