Your first commit is 1.1 then 1.2, then 1.3, the. 1.4. let's assume now you branch off a different line of changes. That branch is named 1.4.1, and the first commit is 1.4.1.1. the. 1.4.1.2. the. 1.4.1.3. if you made a second branch off 1.4, that's 1.4.2.1. if you branched off 1.4.1.3, that's 1.4.3.1.1.
An odd number of numbers is a branch name. An even number of numbers (x).y is commit number y on branch x.
@RL_Dane oh by the way did I mention that CVS is just a wrapper around RCS, which only tracks individual files. Therefore, 1.4.1.2 is not actually specific commit identifier, that identifies that it was the second check-in of that file and that file alone onto the 1.4.1 branch. It is possible that a single check-in command gives every single file in your working copy a different commit ID because CVS works on individual files completely individually, to the point where I commit operation is not atomic
Got my K1 cables for the #DigiRig today, meaning I should be able to have an audio I/F to most HTs. (And if they're RS-232 serial, I can program them too.) So I just did some low-power APRS testing... and sure enough, plug in the GT-5R and my 878 was decoding packets from it.
Only one issue: the AnyTone 878 doesn't PTT in the same way, apparently, so that's not doing anything. I guess that means this cable is Baofeng only... but you know, the GT-5R has "enough" filtering (certainly more than the UV-5R) and a portable APRS station is a portable APRS station. I think I can work with that.
@thememesniper Or more specifically (and less sarcastically) I don't think I've seen someone be as elitist over the OS as I have the ecosystem.
There's the Apple people that love the Apple Just Works™️ walled garden, who judge (now ex) friends for having the dreaded "green bubbles," the people that are genuinely confused and unable to use an Android phone for the lack of Control Center on it (I'm not joking, I used to live with that one... and funnily enough he just bought a Pixel)...
...and then there's the "X product" people. The Final Cut Pro people. the Keynote people. The Logic Pro people. The- you get the point. Those types that only know mac-specific apps and so therefore staunchly refuse to learn anything else.
But I've yet to see someone whole-sale defend the entire "UNIX with a coat of techbro smooth minimalism" that is macOS.
The people that just want everything to visually flow together, and therefore become Apple elitists because they have a consistent design language and superficially look futuristic and clean (until you need to charge your ergonomic disaster of a mouse)
And the people (read: execs) who just go "APPLE PRODUCT HIGH DOLLAR. HIGH DOLLAR MEAN PRODUCT IS LUXURY. CEO DESERVE LUXURY. THEREFORE CEO REQUIRE APPLE." (or the offshot, the Creative team that was only trained in college with Adobe on a mac so they immediately demand a mac and Adobe licenses)
Speaking of rigs, does anyone out here have any recommendations for a VHF/UHF rig that has CAT control? Doesn't need to have a built in sound card, just something that I can plug a DigiRig into with the right accessory cables for automatic frequency control. Bonus points if it can do SSB on V/UHF but not strictly a requirement.
The current one I'm working on getting set up has nothing (I think it's actually designed as a mobile rig), so to DigiRig it, the audio cable I need literally just plugs into the 8-pin mic socket, and then the external speaker jack at the back.... that's a bit too jank for my liking, long-term.
Just had to pick up the local club's weekly UHF net because there was no NCS... I did sign on to be available on a fill-in basis, so I guess it was my chance to shine!
Would have been helpful if I didn't spend a full two minutes just running around looking for my NCS notebook before giving up and just using a Notepad window (turns out someone put it in the Midwest Junk Drawer™️, no wonder I couldn't find it.
Hopefully before the next time the club's simplex net rolls around I'll have this VHF/UHF rig up and running, so I'm not limited to just 7 watts of power!
Update: the last time I tried to turn this thing on, it powered on but no display. Buttons worked, knobs worked, no lights. Something tells me somewhere I either bent a pin too far or broke it in the cable... I'm expecting I didn't break anything. I don't know too much about 80s/early-90s display tech, but I'm very certain that most things that would be connected to those cables, are not the kind of thing to fail silently when incorrectly connected. No pop and no smoke tells me I probably just missed a connection.
New cables on order. 100mm same-side 1.0mm 12-pin pitch FFC. Pennies. Then it'll be round 2. And, now I have the cabling to DigiRig this thing as well.
@adamsdesk Going to be honest, I don't know how much I like the vibe of VerneMQ... OSS, true, but everything on that page is so heavily steeped in corporate up-sell that I'm already expecting they'll split off a free and paid tier at some point since almost every word seems to be trying to convince your business why you need MQTT, why this MQTT broker is the best option built on the best foundation, and why there's next to no risk or cost (especially compared to other MQTT broker solutions)
@adamsdesk Oh... also the EULA you get with pre-built binaries already prohibits disassembly or derivation, including
...gain access to the source code of the Software or any part thereof
as part of the restrictions which immediately makes the binary build suspicious, even if it states that these clauses don't affect the case where you may receive portions of the software under an open-source license.
No usage information opt-out.
The fact that they reserve the right to demand you cease and desist usage of VerneMQ and destroy all held copies of it, at their convenience, is also funny.
My favorite part (not necessarily a red flag like the rest, but still funny) is the last clause that says if any part of the EULA is found unenforceable then the entire agreement (and your license to use VerneMQ) terminates.
Also, 100% a nitpick: Using erlang distribution as your clustering mechanism, while cool, needs to come with the caveat that it's not suitable for wide-area usage. EDP and the EPMD are not encrypted, not really authenticated (challenge / response using a pre-shared key and MD5 that's not required after the initial handshake), and not protected from malicious interference. Sure it's a barely-documented dense protocol that's hard to make heads or tails of, but the fact remains that it's insecure and needs to be handled as such through extra means. I'd think that's worthy of a footnote, at least.
RabbitMQ, for example, sure it has its upsell, but the front page and documentation isn't as packed full of buzzwords. Or at least, their blob of buzzwords doesn't seem to have a heavy lean towards commercial partners.
Also using them as an example, as an Erlang system as well, yes, you'll be hard pressed to find something on the OTP that doesn't use its distribution protocol for clustering. RabbitMQ has instructions for wrapping EDP in TLS, which is something your team appears to have overlooked. Just because it's not intended to do something (like clustering over WAN) doesn't mean someone won't try it... And I speak from having seen that happen.
Actually, I'll break (1) out a little more detailed.
The experience of your page makes it feel like the open source side is, frankly, "the afterthought." I get that there's a reason to tailor to businesses, and to some extent everyone has to. But look at the first paragraph in comparison here:
Clustering MQTT for high availability and scalability. VerneMQ is open source software, extendable, and enterprise support is available.
RabbitMQ is the most widely deployed open source message broker. With tens of thousands of users, RabbitMQ is one of the most popular open source message brokers. From T-Mobile to Runtastic, RabbitMQ is used worldwide at small startups and large enterprises.
Clustering, HA, scalability, extendable, and enterprise support. RabbitMQ is doing a product upsell, but they lead with "it's popular."
I know this is all subjective. That's why I never said your product is bad or that it shouldn't be used, it just feels "off," an opinion that's specific to me.
Or, (and I'll shut up after this one), the getting started guide, of both.
Theirs is just a list of tutorials on not only what specific MQTT parts are and how to implement them with code, but also some amount of "why."
When I press the getting started button on your site, I get.. one page, that's again, tailored to enterprise, and the first three headings as well, "Low Entry and Exit Risks," "Think Forward," and "Battle-tested Telecom Technology." That means nothing to me as an individual.
I get that self-hosted and individual user usage isn't a focus. We're the small fry, this is true.
I'm not saying the product is bad. I've never tried it. But when you're trying this hard to appeal to whatever MBAs might be looking at your product, in addition to the fact that the other ones I have used in the recent past don't require I agree to an EULA to run a precompiled binary... It gives off the impression that you're not going to stay open source for very long. Or that you're going to very quickly split a community edition and enterprise edition (already done), with feature disparity growing on every release.
Put simply, the entire (subjective) experience is that the open source side is an afterthought - a realization that you get higher conversion with lower barrier to entry, so here's a free chunk to let you play around with it non-commercially.
I'm not saying it's bad. Just that I don't get the best feeling. And that's fine, that's what the free market is for.
