Post

Interop 2027 prep is now. Want to help? 1. Go to developer-signals.rviscomi.workers.dev 2. Sign-in using GitHub 3. Find features you need 4. Click the comment icon, add your use case 5. Submit There aren't many ways to tell browsers what you need and why you need them. That's a very effective one.

11/9/26, 7:23 am11 reposts23 likes

Andrew Hudson

@andrewhudson.dev

12 Sept

unable to log-in. Tried in Chrome and Firefox (both with with the Ghostery extension). No warning messages, no "failed login" or similar messages, just not able to upvote or leave comment etc.

Rick Viscomi

@rviscomi.dev

12 Sept

Hmm you can try the direct login URL: developer-signals.rviscomi.workers.dev/api/auth/git... Let me know if it works or if there are any network errors in DevTools

Andrew Hudson

@andrewhudson.dev

13 Sept

Chrome: console message: GET developer-signals.rviscomi.workers.dev/js/component... net::ERR_BLOCKED_BY_CLIENT

Andrew Hudson

@andrewhudson.dev

13 Sept

Firefox: Cookie “_gh_sess” has been rejected because it is in a cross-site context and its “SameSite” is “Lax” or “Strict”. also same message for “_octo” and “logged_in” cookies.