jeremywho

Not 100% sure what I'm looking at, but I know that it looks awesome!

I always thought of developer relations as essentially a tech-sales role. Isn't that ultimately what its trying to do, "educate" people to use your product?

Historic IPO price? It opened at $160 10 days ago, did it not? Currently it is below that price. What historic price are you referring to?

I've been eyeing the "10G PCI-E Network Card with 10Gbps Dual RJ45" on Amazon. Does that not cover what you're asking for?

When can we buy these?

> this story has have nothing to do with the cameras or AI

This story wouldn't exist without flock cameras constantly surveilling the public...cameras have EVERYTHING to do with this story.

I'm on windows. Claude Code via WSL hasn't been as smooth a ride.

My workflow is to use Claude desktop with the filesystem mcp server.

I give claude the full path to a couple of relevant files related to the task at hand, ie where the new code should hook into or where the current problem is.

Then I ask it to solve the task.

Claude will read the files, determine what should be done and it will edit/add relevant files. There's typically a couple of build errors I will paste back in and have it correct.

Current code patterns & style will be maintained in the new code. It's been quite impressive.

This has been with Typescript and C#.

I don't agree that what it has produced for me is hobby-grade only...

What are you using instead?

Is there a breakdown of this anywhere?

ie, something that shows what was proposed in p2025 and what policies/procedures/orders have pushed a particular part of the plan forward?

Are you saying you expect to pay one time and never again and want continued support for the lifetime of the app?

This has been my view for a while. Basically health-care != health-insurance.

People I've talked to can't quite to wrap their heads around that idea. Not sure why.

I used Claude to draft something, might help others submit comments:

RE: WT Docket No. 24-240, RM-11989

To the Federal Communications Commission:

I strongly oppose NextNav's petition to reconfigure the 902-928 MHz band. As an amateur radio operator and user of various devices operating in this spectrum, I believe this proposal would have significant negative impacts on both hobbyists and consumers.

1. Impact on Amateur Radio: This band is crucial for amateur radio experimentation and innovation. I personally use it for Meshtastic devices, which provide valuable experience in mesh networking and could be vital for emergency communications. Displacing these activities would hinder technological advancement and public service capabilities.

2. Consumer Device Disruption: Many common household devices operate in this band. For example, I use Z-Wave devices for home automation. The proposal could render these devices inoperable, forcing consumers to replace expensive equipment and potentially reducing the availability of affordable smart home technologies.

3. Unlicensed Innovation: The 902-928 MHz band has fostered significant innovation in unlicensed devices. Restricting this spectrum could stifle future developments in IoT, smart cities, and other emerging technologies that rely on license-free operation.

4. Inadequate Protection for Incumbents: NextNav's vague assurances about working with incumbents are insufficient. The proposal lacks specific, enforceable protections for existing users, including amateurs and Part 15 devices.

5. Potential Windfall Concerns: The proposed "spectrum swap" appears to grant NextNav significantly more valuable spectrum rights without clear public interest benefits. This raises concerns about equitable spectrum management.

6. Alternative Solutions: The Commission should explore alternative methods to support PNT systems that don't involve disrupting a heavily used and innovative spectrum band.

I urge the Commission to reject this proposal and maintain the current diverse ecosystem in the 902-928 MHz band, which supports amateur radio, consumer devices, and technological innovation.

Respectfully submitted,

[Your Name]

Amateur Radio Operator, [Your Call Sign]

What should we say? I'm a licensed ham, meshtastic user and z-wave user but I'm not sure exactly what to include in an FCC comment that would be useful, other than "Hey! I use this!".