lol, my husband does the same thing… I told him I can’t see the door at night and sometimes walk into it, so we leave it open at night, solves the problem.
Motion activated (night) light - even a little battery powered one - and the same in the bathroom. Not enough light to stir you awake but enough to find your way without turning on lights or fumbling in the dark.
The attack relies on social engineering to get the victim to disable protections and could just as easily have happened with a plugin for any code editor.
Anyway,
What I like about obsidian is that it can handle a truly huge amount of notes without slowing down, and the notes are just markdown files on disk, so there's no lock in.
I have used evernote, ms one note and zoho notebook before, and had issues with all of them.
That isn't a response to my post, it is a bit of information already present in the thread that isn't relevant to my question followed by a positive review. This suggests that a shill brigade has been attracted to these comments. I suggest you don't do that, it isn't a good look.
I used to work for a sports betting company that identified individuals who were a little too good. The key is to remember that they are addicts and will bet on events regardless of if they have insider knowledge or not, so you have to account for this and not only identify the individuals with insider knowledge, but also what events they have that knowledge about and what they don't.
every casino's business model is about get-in-the-door appeal in order to fish out a handful of very lucrative whales. polymarket included. so no they're not really comparable.
I have been using Opus (in zed) to find the “in between” bugs. Bugs that kinda live in the space between micro services or between backend and frontend.
It takes a bit of preparation to get good results, but it can usually find the source of bugs in 1-2 hours (200k-300k context) that would take me a week to track down.
I create a folder, and then open up git worktrees in sub folders for every repo I think might be involved. I also create an empty report.md file.
Then I give it a prompt that starts with “I need you to debug an issue”, followed by instructions for how to run tests in each repo, followed by @mentioning any specific files or folders I think is relevant (quick description of what they are), then the bug description.
After that I tell it to debug the issue, make no code changes and write its findings to the report.md file.
reply