Two clothing items entered in the local county fair (San Diego County, California, USA). Description in alt text. The Tuxedo won third place and the reversible embroidered jacket won first place.
I enjoy thinking and doing. Not necessarily in that order. This is my amateur radio account. I can also be found at @abraxas3d
de W5NYV. Open Research Institute co-founder and CEO, ARRL Technical Advisor, ARRL San Diego Section Technical Specialist, #OpenSource HEO #amateur #satellite lead (Haifuraiya), and member of FCC TAC š³ļøāš
Two clothing items entered in the local county fair (San Diego County, California, USA). Description in alt text. The Tuxedo won third place and the reversible embroidered jacket won first place.
I've boosted a few posts about the AIDS quilt exhibit in London, but haven't linked to anything under the #QuiltingNews hashtag. Here's a couple of recent articles - Huck has better pictures of the quilted panels, but the BBC has personal stories about some of the people memorialized in the project
https://www.huckmag.com/article/largest-ever-display-of-uk-aids-memorial-quilt-opens-at-tate-modern
Inside every QA tester there are:
- Two wolves
- One wolf
- Zero wolves
- 0.5 wolves
- 2,147,483,648 wolves
- -2 wolves
- Beer wolves
- Two coyotes
- šŗšŗ
- ŠŠ²Š° волка
- '); DROP TABLE WOLVES;--
- <script>alert('Awooooo')</script>
@BlindHams thank you - we will gratefully accept as soon as it's ready. We got the constant overhead byte stuffing protocol part working just now, and have something weird going on with frame order out of the priority queue. Command line in general is stable, with a verbose mode producing copious debug and quite mode knocking things down to "just the facts". There are potentially a lot of statistics and quality indicators that can be exposed, but I can't have that be messy or intrusive.
We now have all the network layers installed- RTP UDP IP for voice, UDP IP for chat and control, and UDP TCP IP for data.
The next part could or should be an HTML interface that does not get in the way of anyone that wants to do radio, following best practices advice.
Nothing works better than actually using it, so we're trying to get it working over the internet, treating a server like a satellite or a "groundsat" earth station central node, as soon as possible.
Online version of our Inner Circle Newsletter for May 2025 can be found at www.openresearch.institute/2025/06/0ā¦
@azonenberg @whitequark @G_glop
Ok now. Have you ever had a dream? Have you ever wanted to do something that everyone else said you couldn't do? Like, build a bridge to Mars, own a unicorn, or get enough sleep.
Far be it from me to impugn the efforts of a company to simply provide the specifications that I need to connect my SDR directly up to JTAG.
@sluttymayo literally laughed out loud.
"hey sweetie, i'm sorry, they were sold out of the warhammer space marine codex you wanted, so i bought you a copy of the catechism of the catholic church and a history of the at&t bell telephone system and glued them together. i hope that gets you started at least"
@BlindHams Things are working as a command line python script. Now, early on in the process, is the time to ensure accessibility for hams.
I'm getting conflicting advice. I'm a compromised vision developer but can get by. Making this digital mode really work is very important to me. What is the best radio interface practice that we should adopt?
@BlindHams greetings blind hams network. I'm working on Opulent Voice which is a high quality voice, text chat, and file transfer amateur radio protocol. I must have this be accessible. It won't move forward unless it is accessible. We are at an inflection point. What is the best interface? Is HTML-5 interface to the radio station the best way forward?
Another piece of cool, open source, user repairable #linux #hardware ordered because #accessibility focused guides on user-repairable hardware basically don't exist. I can't wait to evaluate it and make a post series about the experience. Maybe with some videos! I need a Patrion or something if I keep this up, but oh well. It's fun and people seem to enjoy what I have to say. #mnt #linuxHardware #a11y #openSource #foss #openHardware
@nivex @OpenResearchIns doing our best - this week so far is human-computer radio interface improvements. We have Opulent Voice delivered over LAN from a Raspberry Pi "station" to a Mac "station" on a desk, with almost all of the framing implemented. We are not convinced RTP is working right, and COBS is not in there yet. Accessibility, a browser interface, test server, and internet repeater demos are probably next. Hoping to show all of this by DEFCON.
@nivex @OpenResearchIns you are very welcome and I am sorry for any disappointment about that project.
@nivex @OpenResearchIns commercial success is absolutely possible, achievable, and desirable for open source amateur radio innovations.
However, treating āin it for the long haulā volunteers and sponsors like garbage, for temporary short term gains, harms your project very badly.
@nivex @OpenResearchIns thereās been at least half a million dollars given to this project from ARDC. There is more from the community and other sources. There was always a āwhy canāt we get paid to do this?ā and āwe deserve to be paid for this workā type of conversation from some of the leaders. M17 definitely viewed their āshed labā as a future corporate office, and the grant money as essentially VC funding for a commercial product.
@nivex @OpenResearchIns Fortunately, two M17 board members came forward during all of this and provided all the proof in writing. We are very thankful because this prevented wasting more time with sneaky unserious people.
ORI moved on from this very quickly. Weāre proud of the progress we were able to enable, ORI genuinely loved supporting M17, we know what our value added was, and we were very disappointed about the decisions made by their āhead honchoā.
@nivex @OpenResearchIns ORI canāt do this because the contract clearly said that remaining money needs to go back to ARDC.
So, we returned the remaining funds. Work stopped.
The idea that a sponsored project would actively collude with the funding agency to cut out a high-performing sponsor to get more money - to go directly to someoneās pocket? This is just not done. Itās low rent silly behavior, and we wanted nothing to do with projects or funders that did this.
@nivex @OpenResearchIns An ARDC employee and a M17 volunteer set up a back room deal to get another 250k (note, there was still quite a bit of money left from the first one) but only if there was a new fiscal sponsor.
Why? No idea, but we think itās because M17 didnāt like following rules like āyou canāt have a bunch of travel money if youāre not giving a talk about the project at the eventā.
Woj wanted remaining money be transferred to an account he controlled.
I have a story for you.
@OpenResearchIns administered the original 250k grant from #ARDC. ORI achieved all of M17ās capital expense goals, got them started on the standards process (ANSI/IEEE), helped fix 6 or 7 major issues, and had about 100k left. Really good performance. ORI had some rules like āwe pay for travel to events if youāre giving a talkā. It wasnāt a bad project at all. Things were progressing well.
In return, M17 leads decided to burn ORI.