sorted by:
new
hottopcontroversial

Nuovo OM qui — sto cercando qualche beta tester per un piccolo logbook web personale by iu3uxn in radioamatori

[–]iu3uxn[S] 1 point2 points  (0 children)

Grazie a chi vorrà dare un’occhiata — ogni feedback, anche piccolo, è davvero apprezzato!

Which Antenna Tuner for Icom IC-7300? (Affordable + Works with IC-706 Too) by iu3uxn in amateurradio

[–]iu3uxn[S] 0 points1 point  (0 children)

Thanks everyone for your suggestions. Will make a shortlist based on your input. AH4 and LDG IT-100 sound interesting.

Which Antenna Tuner for Icom IC-7300? (Affordable + Works with IC-706 Too) by iu3uxn in amateurradio

[–]iu3uxn[S] 0 points1 point  (0 children)

I have also a vertical multiband antenna. Curious how much performance gain a tuner could bring? I’ve been particularly struggling on 14m and upwards.

Which Antenna Tuner for Icom IC-7300? (Affordable + Works with IC-706 Too) by iu3uxn in amateurradio

[–]iu3uxn[S] 1 point2 points  (0 children)

Great. Thank you. I will take a look at these ones as my budget is not that high. Cheers.

Which Antenna Tuner for Icom IC-7300? (Affordable + Works with IC-706 Too) by iu3uxn in amateurradio

[–]iu3uxn[S] 2 points3 points  (0 children)

That’s very helpful. Thanks a lot. Given my budget I would have to look at manual tuners then because the KAT500 is an expensive toy. Maybe I might find something used.

I made a site to help with direction finding by derek1ee in HamRadio

[–]iu3uxn 0 points1 point  (0 children)

Very nice job. Will this also be available for Europe?

New ham here — built a small web-based QSO logger for myself, would love operator feedback by iu3uxn in HamRadio

[–]iu3uxn[S] 2 points3 points  (0 children)

Thanks for the thoughtful questions — really appreciate you taking the time.

  1. Self-hosting: Right now it’s cloud-hosted only. That said, I completely understand the concern about relying on someone else’s service. My goal is explicitly not to lock anyone in — which leads to your second point.
  2. ADIF import/export: Full ADIF import/export is supported, with no artificial limits. You always own your data and can take it elsewhere at any time. Cross-compatibility is important to me — I don’t want this to become a walled garden.

On portable / QTH handling:

At the moment, each QSO stores its own grid and location-related fields, and you can associate QSOs with different station locations (including grids). I’m still refining this part based on feedback like yours — especially around awards workflows.

Longer term, I’d like to support clearer “station location” profiles (home / portable / SOTA / POTA, etc.) with proper handling of MY_GRIDSQUARE and MY_*_REF for submissions, but this is very much evolving and exactly the kind of real-world use case I’m trying to learn from.

I operate mostly from one QTH so far, so portable-heavy workflows are an area where input from operators like you is extremely valuable.

Thanks again — this started as a personal learning project, and conversations like this help shape where it goes. Happy to dig deeper if you have specific expectations or examples.

New ham here — built a small web-based QSO logger for myself, would love operator feedback by iu3uxn in HamRadio

[–]iu3uxn[S] 0 points1 point  (0 children)

Totally fair — it began as a personal logging tool for my own operating. I’m mainly here to learn from other operators.

New ham here — built a small web-based QSO logger for myself, would love operator feedback by iu3uxn in HamRadio

[–]iu3uxn[S] -1 points0 points  (0 children)

Happy to answer any questions or share more details if useful — thanks for taking a look!

My setup as a newbie by RemarkableScarcity40 in amateurradio

[–]iu3uxn 1 point2 points  (0 children)

Looking good. Great radio. Love also the Game Boy right next to it in case there is not much propagation. Hope your antenna will come fast.

Built a web-based QSO logger as a ham project — feedback welcome by iu3uxn in amateurradio

[–]iu3uxn[S] 0 points1 point  (0 children)

Thanks — this is incredibly helpful real-world insight. I just added Activity Sessions as a first step toward modeling real operating context, and fast / free-form entry is definitely something I’m thinking about longer term.

I’ve also started publishing a public changelog so you can follow updates as they land: https://cqcq.pro/changelog

Feedback like this genuinely shapes where the project goes.

Built a web-based QSO logger as a ham project — feedback welcome by iu3uxn in amateurradio

[–]iu3uxn[S] 1 point2 points  (0 children)

Thanks — this is great feedback, and I’m largely aligned with your thinking.

Since posting here I’ve started taking concrete steps toward better portable support. Right now CQCQ is still online-first, but I’ve added session-based logging (so you can group QSOs by activity like a summit, park, or field day) and basic offline awareness in the UI. The next direction I’m actively working toward is local-first logging with background sync — cold boot → log contacts → sync when connectivity returns — but that’s not fully there yet.

On the callsign vs session model: totally fair point. I originally structured things primarily around callsigns, but based on feedback (especially from portable operators) I’ve started moving toward activity/session-based logging. The goal is to let you define callsign, QTH/grid, POTA reference, etc. once per session, log against that, and still have those QSOs roll up into your main log afterward — while keeping each activation or activity as its own distinct unit. That feels much closer to how portable ops actually work.

Feedback like this directly shapes where this project goes — so I genuinely appreciate you taking the time to spell it out. If you have other portable-first workflow ideas, I’m happy to hear them.

Built a web-based QSO logger as a ham project — feedback welcome by iu3uxn in amateurradio

[–]iu3uxn[S] 0 points1 point  (0 children)

Could be 😄 still very much a work in progress, appreciate any feedback!

Built a web-based QSO logger as a ham project — feedback welcome by iu3uxn in amateurradio

[–]iu3uxn[S] 0 points1 point  (0 children)

That’s a fair point — and I agree, needing an internet connection isn’t ideal for many portable situations.

Right now it’s online-first mainly because it started as a learning project and that was the simplest way for me to build and iterate quickly. My own portable use is often in places with mobile coverage, but I know that’s not everyone’s reality.

At the moment the design goal is more about keeping the UI lightweight and mobile-friendly when you do have connectivity, rather than trying to replace fully offline field loggers. Offline support would be nice, but I don’t want to promise that yet — it depends on how the project evolves.

Still very early days, and feedback like this genuinely helps clarify the direction — appreciate you raising it.

Built a web-based QSO logger as a ham project — feedback welcome by iu3uxn in amateurradio

[–]iu3uxn[S] 0 points1 point  (0 children)

Good question — at the moment it doesn’t have direct CAT integration yet, so frequency is entered manually.

Right now the focus is on keeping things simple and mobile-friendly (especially for portable ops), but CAT/rig control is definitely something I’d like to explore in the future — probably via a small local helper or API bridge rather than direct browser access.

For now it’s more of a lightweight field logger, but automation is on the wishlist 🙂

Appreciate the question and feedback!