 |
|
eQSL.cc Home
Search
Login
Authors
Recent Posts| Viewing User Profile for: SP5NZF Jakub Rusiecki | |||||||||||||||||
| About | Contact | ||||||||||||||||
|
Send Private Message |
||||||||||||||||
| Post Statistics | |||||||||||||||||
|
SP5NZF Jakub Rusiecki has contributed to 1 posts out of 11815 total posts
(0.01%) in 1,418 days (0.00 posts per day).
20 Most recent posts:
Mobile with many QTH's »
Muitiple QTH's Aug 27, 2022 07:06 PM
(Total replies: 6)
I like eqsl.cc because I like getting QSL cards (pictures). It is special as buro does not work here and LoTW is so ugly... so I want EQSL work ! Let's take example: Greek regulations require that I use SV5/SP5NZF/P for ALL activities on Rodos (in any EU country principle is same just replace SV5 with respective are prefix). /P stays there whether I work from vacation house (kind of fixed location) or real portable going around SV5. I visited Rodos and worked (same days) : 1. From Vacation house, KM35WW, qsl card picture related to that location 2. From POTA SV-0258, grid KM35VV, qsl card picture related to POTA AND with POTA logo. Same date range, same callsign, distinct QSL designs (only one has POTA logo), grids, descriptions I understand that problem is that account = location (and eqsl needs to know where to "route" incomming qsl to). The reali life is that account=callsign under which come locations. So if structure of account would be Owner-> Callsign=Account -> Location=QSL card design and location info (grid, IOTA,....) then: a) incoming card would go to Account (callsign+date) b) outgoing cards would use Account(callsign)+Location to choose QSL card content BTW it would simplify retrieving cards (if location is ignored by eqsl.cc; this could be account parameter). Let me know if I can help by e.g. testing this fix. 73, Kuba, SP5NZF SP5NZF Jakub Rusiecki Edited by SP5NZF Jakub Rusiecki on Aug 27, 2022 at 07:08 PM |
|||||||||||||||||