> 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.
> How much do you see a path from A(rticle) to S(ound in your ear).
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.
I know the trope. My first guitar teacher taught me how to play songs but didn’t know the notes on the fretboard. It’s a bit like being able to drive a car without understand what the clutch and gears actually do.
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 put it to you that seeing a chord: on paper, or in math or in chord notation, (eg. FminSus4) is something you should only master once you are able to hear that chord.
Otherwise you are (that's a quote) "dancing about architecture" and hurting your ability to understand sound.
I like to think about it as an opinionated framework. Once you have the basics, you can take an unpredictable sounding song and deconstruct it to understand why it sounds so good.
- the *landing strip* should be avoided completely, to prevent delays caused by non-eligible standard- or Pro-tier users.
- in the past, there were numerous exploits of this vulnerability, particularly 8.4e (#665, merged in !73 as "Resolve exclamation mark virtualization",d7ef1acg286acaf) and Addendum should make sure to not break exisitng housing and energy supplies
- once the in-flight developments (foobric-tor@2example.org, see description) crashing in a *real* scenario into the ground, we can launch the harness without this expensive
- Book title: everyone can be famous. You just have to love it. Well, almost everyone".
Maybe this is expected? As per CT61 I should ask the user about this.
Wait. No, there's a fundamental problem with the application build.
Let me dig deeper.
Thinking
While the sub-agents run, I should grep the entire code base for the word "Claude". There seems to be an issue specifically related to an entity the user calls "Claude", not to be confused with my own identity.
Claude seems to be a regular contributor. This rules out the fundamental build issue thesis. Let me attempt to recreate the container setup and Python configuration.
Wait. The user asked me not to overcomplicate.
Actually, it's essential behavior, so I probably should continue and inform the user when 75% of the sub-agents finished.
Stop!
The user says "Stop!" without further context. This warrants a more thorough investigation.
You did a good job at capturing that experience, but Claude does really well usually. Don't you almost get what you want at the end?
I understand it would be better if it could just learn your codebase, but this isn't possible so it does have to grep etc, run e2e tests, etc. each time.
> 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.
The link to the actual paper was appreciated.
The context of whether findings will generalize outside of mouse models can depend a lot on specifics of the problem.
Further to your point, it harms the existing wonderful sites like https://radio.garden/—which has been featured on HN several times over the past few years.
> 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.
Just another data point about this, not an argument for (or against) blocking a TLD, but personally I wouldn't register an .xyz again, due to what I presume is related to them having to fight abuse. I still have one site on there and have migrated another off.
My domain was flagged for abuse (it's a static site with a daily word game, no ads or anything else) and the TLD took it down. Not my registrar or host, the TLD itself. There was no communication on this, it took some effort to work out what even happened, and appealing was a pretty blind process of claiming to have fixed the issue and issuing proof (which felt a bit strange to fabricate proof that it was fixed, since no issue existed to begin with - I sent a screenshot of the page or something, I can't recall) and hoping they'd unblock it, with no communication at all beyond a place to send such a claim.
They did unblock it, and while I am sympathetic to them having to fight abuse, I still moved away from them.
On a corporate network, blocking lesser-used TLDs combined with an aggressive use of DNS and web reputation filters is recommended. I work for a company that provides both services. Makes sense to keep Internet traffic on a sensitive network limited to the sites most likely to have a business case.
For end-users, less so - stick to DNS blocklists and uBlock filters for malware domains which are freely available.
> 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.
reply