roboyoshi

I tried a bunch of "open" tools last week, but turns out they are a paid tool in disguise most of the time. I eventually paid for CleanShotX for my work and have peace of mind because it just works. OBS is IMO much more stable and aimed at live streaming anyway.

Do you have a skill for that or do you (or anyone else here) just prompt with "try to find security issues"?

It's rather broad right now. I started reverse engineering a mac app and it started reading some binary data and then quickly told me to switch to Opus 4.8 to continue, because the guardrails kicked in.

Always a joy to read those and the fact that the emulator keeps on improving. You can run it on SteamDeck nicely and play Gamecube games better than Switch 2. It's a shame nintendo has only released about 5 games thus far.. Great work Dolphin Devs! I still need to give RetroAchievements a try.

I want this as OSS so I can selfhost it - it looks fantastic, I probably give it a spin to get rid of google sheets.

Slightly disagree - while LibreOffice might be better in features, the UI/UX of Google Docs worked so much better for me, it's not even funny.

I liked that one when it was still called "Wunderlist". I'm still mad the owner sold it. He now makes "Superlist" but it's simply not the same :/

M2 with 16GB: It's slow for me. ~13GB RAM usage, not locking up my mac, but took a very long time thinking and slowly outputting tokens.. I'd not consider this usable for everyday usage.

So you are using Google or what? I feel like in Enterprise Environments you don't have much choice between bad and worse.

Interesting stuff! I've been trying ollama/gpt + continue.dev and copilot in VSCode for a bit now and the chat-style assistant is a huge plus. Especially in DevOps (my main work) the codegen is rather unhelpful, but the ability to let LLMs explain some sections and help in rubber-ducking is huge.

I see that a good output requires a good input (prompt). How does copilot workspace determine a good input for the prompt? I see that in the github repo there is already a bunch of "Tips and Tricks" to get better results. What is your experience so far? Should we change our way of creating issues (user-stories / bug-reports, change-requests) to a format that is better understood by AI/Copilot? (half-joking, half-serious).

you can generate serviceAccounts in google cloud that act as clients for your google workspace with no additional cost. It's a neat hidden trick to circumvent the google quotas, but you need to write your own clients/wrappers to utilize that properly.

Totally forgot that Pivotal was acquired by vmware - that makes the whole thing even worse. AFAIK Spring is huge in the java ecosystem, but it's also mainly open-source, right? So maybe the community will take care of it.

DNS is still possible with Google Cloud DNS, but you cannot purchase domains.

- When you fire a lot of engineers, legal, security experts... things will still somehow keep working - Also some people still want to keep working at this place (or must, because of VISA etc); It probably happens all the time, just this time everyone was watching it in full motion. - I was sure this whole takeover was the end of twitter, but somehow with how many users twitter has, it just won't die. Goes to show the advantages of the mass.. probably the same applies to microsoft/google.. - The whole 8$ for a checkmark story.. which destroyed the whole trust in the checkmark basically immediately. The whole verification process (how that worked) - many people shared some insights on that and how much effort it was to fine-tune all of that with the scale of twitter. - The free API just being shut down with basically zero communication to devs. and somehow getting away with it. I guess this is a reoccuring theme in tech that a small company has to be open for developers until it's big enough to turn on them. - With the reduced engineering and the new management, it seems more errors slip into production (and incidents like the one now) - or maybe it just feels like it with all the focus on twitter right now - but anyways, you just see things breaking you normally would not expect to see.. - How people are communicating, or in this case not communicating.

I'm probably not the ideal person to write this down, there was so much stuff going on, some people probably made a whole blog-article series on this. This is just a few of the things that I'm able to remember right now.. and with everything on hn here it gives you some ideas and things to think about. Hope that Helps.

In case people are wondering what this is about: All links and images are not working on twitter right now. Seems like they accidentally included their own services in the api blocklist? Sending best of luck to the engineers. The whole twitter saga has given me a good chunk of valuable "lesson learned" over the last weeks and months.. so thanks for that.