Railway: we've been attacked by people trying to steal credentials like API keys! Rotate your credentials!!!
Also Railway: we've been attacked so you can't deploy your app or rotate your credentials.
https://t.co/DdJqqXialr
https://t.co/2Y07IbbyiF
🤡🤡🤡🤡🤡
If a bunch of things are broken online for you today, it's because we're experiencing the the PHPocalypse caused by a critical vulnerability. (Details here: https://t.co/fZOiBxFC1j)
Sounds like it's going to be a problem for days.
@bcardarella I think you could have probably made something that tracks a combination latency and intelligence to see it. But I don’t think it’s possible anymore.
What started as an idea between two friends in Edmonton has grown into a business with global reach.
Today, Earth Group’s products are sold across Canada while supporting millions of school meals around the world 🌎
Discover the Earth Group story https://t.co/p6qcU9V9Gv
You should use Passkeys despite the misinformation about them that's been showing up on substack. Passkeys protect you because they verify the website you are logging into is the website that issued the passkey.
If you want more information on why they are not a trap, this is a good read that rebuts the article that's been circulating online.
https://t.co/8ZLhm04iEH
@bcardarella So far today I would say it’s good for $2/$10 - but I haven’t given it enough work to judge.
I heard they benchmaxxed it. But even if they did the intro price is still good for what you get.
Until macOS 27.2 comes out, Siri will take over the shortcut <command>+<shift>+<space> to use for "ask Siri about active window".
You probably use this shortcut for something else more important... so to take it back go to Settings > Keyboard > Keyboard Shortcuts > Screenshots and uncheck "ask Siri about active window."
BUT there's a catch... if you use any of the other shortcuts listed for a screenshot, (for example <command>+<shift>+4) Apple reverts this setting and you will need to disabled it again. Every time.
This took me ages to find. And ages to figure out what was triggering it to revert. So I hope this helps you until they get it fixed.
Something I've noticed specifically with GPT 6.1 Sol - it has a tendency to overcomplicate things, especially around testing, in ways I have not seen with GPT 6 Sol (and other models).
I often run multi-day tasks using an agent graph and since adopting Sol 6.1 I've seen a pattern emerge where it's so intent on proving it's correct it will write test suites that take days to run and then attempt to run them multiple times as it works through to the solution. Effectively making it so that a task becomes impossible to complete.
I've seen this several times now and the only fix has been to walk back the run and start from scratch.
GPT 6 Sol didn't do this. It's new with GPT 6.1 Sol. Just something to keep an eye out for.
So I prefer cohost for its ability to format text (aka. code snippets) I see that a lot of you have ended up on mastodon.
I’m https://t.co/UW49PqERtx
if that’s your jam. :)