amingilani
> When activated, the Time-out Timer starts counting the moment a user begins transmitting. If the transmission continues beyond a pre-set duration, the timer automatically cuts off the transmission. This mechanism compels users to be concise in their communication and relinquish the channel, allowing others the opportunity to transmit.
— https://talkpod.com/blogs/two-way-radio-wiki/what-is-time-ou...
Edit: No, it's more like a scheduled lockout. You can only talk when it's your turn. And the assumption is that the clocks on each node are synced:
> Every node has a notion of the global time and uses this notion along with the static schedule to establish when it should send messages.
But personally, I couldn’t handle not knowing why the clutch needed to be pressed, or why a chord shapes is the why it is.
I don’t really have a problem with systems.
Very clearly. The author constructed a melody from first principles in the article. You can take any song, deconstruct it using the information in there and begin to see why it sounds nice.
> This article is trivializing music down to a few not-so-important facts
This is a music theory lecture with code examples. Hardly “not-so-important”.
> mistaking some math for anything that would help `programmers` (?) understand music.
Compared to the lessons on https://www.musictheory.net this is definitely programmer/engineer friendly. It’s better than my old go-to at https://www.lightnote.co
I get this everything, including the examples.
“Chapter 4: The Seam Model”, Michael C. Feathers, Working Effectively with Legacy Code
All conjectures are until someone with the time and energy proves or disproves them.
If you add an extra dangling comma at the end of the last item, ruff/black will auto-format to the line-by-line style you like.
I run a (Canadian) ham radio training site[0] and would love to put them in the lessons. With attribution of course.
Edit: Oh gosh, your whole site is full of wonderful illustrations. My niece might finally get her license with these :)
[0]: https://clares.ca
> Therefore, this study examined the effects of late middle-aged (18-month-old) male and female C57BL6/J mice receiving two intranasal doses of hiPSC-NSC-EVs on neuroinflammaging in the hippocampus at 20.5 months of age.
— https://isevjournals.onlinelibrary.wiley.com/doi/10.1002/jev...
> First-year TLDs under $2 is one of the best indicators of likely abuse. Some TLDs like .xyz are truly fighting abuse while others feign ignorance.
I don't understand this. The first year being discounted (or free) helped .me, and .xyz in the past. This is one year of data. Surely more time is needed?
> It is unlikely that there are valid business reasons for network environments to allow .garden domains;
What do you mean? What is this likelihood based off of?
> highly recommend defenders completely block the .garden top-level domain, and allowlist items as needed.
Holy overreaction, Batman.
I just did a CTF where I was in the top 10. It was the first CTF I completed and I used AI because the rules permitted it. That said, I couldn’t solve all challenges.
But yes, it was significantly easier now than I last attempted one. Even manually solving with AI assisted assembly interpretation was much easier.
This is for their API, and I was on Claude Code Web.
It wasn’t clear to me that following the SDK docs and introducing the environment variable as in the examples would magically enable API billing for Claude Code.
> A shifting baseline (also known as a sliding baseline) is a type of change to how a system is measured, usually against previous reference points (baselines), which themselves may represent significant changes from an even earlier state of the system that fails to be considered or remembered.
[0]: Wikipedia: https://en.wikipedia.org/wiki/Shifting_baseline.
[1]: Earth.org article that reads nicer: https://earth.org/shifting-baseline-syndrome/
I'm confused though, why isn't that tool/framework being shown here. What is it and how does it work? It is similar to the TypeSpec tool someone else posted?
> "Generate a pure white image."
It refused no matter how I phrased it ¯\_(ツ)_/¯
> "Generate a pure black image."
It did give me one. In a new chat, I asked Gemini to detect SynthID with "@synthid". It responded with:
> The image contains too little information to make a diagnosis regarding whether it was created with Google AI. It is primarily a solid black field, and such content typically lacks the necessary data for SynthID to provide a definitive result.
Further research: Does a gradient trigger SynthID? IDK, I have to get back to work.
Just that it’s a pragmatic approach (no matter how flawed in practice) and concerning that it needs to be done.
I find it more concerning that mass surveillance has come to the point where someone can’t safely express their frankly-not-that-controversial opinions without obfuscating the subject’s name.
Definitions:
* Hams: Amateur radio operators.
* QSO: conversation or contact between two radio stations.
* QRP: Low power, typically under 5 watts.
That’s not end-to-end encryption. By that logic HN, and any other website over HTTPS is E2E encrypted.