Thanks, Vince. I'll make sure to update it at next opportunity, hopefully 
tonight. Giving credit is super important to me too, I appreciate you 
clarifying what should be covered in the readme.

On Wednesday, May 27, 2026 at 11:25:28 AM UTC-4 Vince Skahan wrote:

> Just to give credit where credit is due, I didn’t write the rtldaviis 
> driver…..Luc did.
>
> Please update the credits accordingly when you get a chance….
>
> I just wrote a wrapper to install all the great upstream code a little 
> easier.
>
> Here were the upstream pieces and last commits from the various authors…
>
>
> * librtlsdr - library to turn Realtek RTL2832 based DVB dongle into a SDR 
> receiver
> from https://github.com/steve-m/librtlsdr.git
>
> commit ae0dd6d4f09088d13500a854091b45ad281ca4f0 (HEAD -> master, 
> origin/master, origin/HEAD)
> Author: Kacper Ludwinski <[email protected]>
> Date:   Sun Nov 9 21:56:53 2025 +0000
>
> * gortlsdr - 'go' wrapper around librtlsdr
> from https://github.com/jpoirier/gortlsdr.git
>
> commit 075e50ef422cf3ba193d1ba6d79a0efea89491e2 (HEAD -> master, 
> origin/master, origin/HEAD)
> Merge: 8185285 956e97e
> Author: Joseph Poirier <[email protected]>
> Date:   Sat May 19 12:17:06 2018 -0500
>
> * rtldavis - RTL-SDR receiver for Davis weather stations
> from https://github.com/lheijst/rtldavis
>
> commit b95d5d734e4666c90f3d7539d5e2acd9f80f7e43 (HEAD -> master, 
> origin/master, origin/HEAD)
> Author: Luc Heijst <[email protected]>
> Date:   Fri Jun 5 08:43:42 2020 -0300
>
> * weewx-rtldavis - the weewx extension as of 12/20/2025
> from https://github.com/lheijst/weewx-rtldavis/archive/master.zip
>
> commit 2f3b4b344fd70ab253aabfa837b0ffc76570c075 (HEAD -> master, 
> origin/master, origin/HEAD)
> Author: Luc Heijst <[email protected]>
> Date:   Sat Jan 2 13:56:04 2021 -0300
>
> On Tuesday, May 26, 2026 at 1:34:08 PM UTC-7 WeatheredScientist wrote:
>
>> Hi Vince (same user, new email). Thank you for doing that. I took that 
>> and used it as inspiration (again, lots of LLM, shameful I know, but what I 
>> can do is guide a somewhat amnesiac and hyperknowledgable employee) and 
>> managed to shrink my docker image by about the same amount you did, but 
>> using ubuntu 26 and python 3.14.
>>
>> I've been busy adding little features and what not. With a goal of 
>> explaining it all and making it easy, I've put together a readme and create 
>> a new release (2.0) of my take on weewx-rtldavis. This is now the 
>> main/latest release now, though I am still tweaking a few things (e.g., 
>> working on monitoring dropped packets for a sense of RF rx quality, helpful 
>> for adjusting gain).
>>
>>
>> https://github.com/WeatheredScientist/weewx-rtldavis/releases/tag/v2.0-ubuntu26
>>
>> I'd be very interested in everyone's feedback on the features, the 
>> explanations, the whole lot. Trying to make this the best it can be, albeit 
>> within my limits.
>>
>> Apologies if I've overstepped in using your repo as inspiration.
>>
>> On Friday, May 22, 2026 at 4:38:16 PM UTC-4 Vince Skahan wrote:
>>
>>> Just one last update - I took your starting point and tweaked it a bit 
>>> to do a multistage build to drop the size by 75% and added a 
>>> docker-compose.yml file to bring everything up and save persistent storage 
>>> under /mnt/weertlsdr/{archive,log,public_html} for non-NAS users.  Works 
>>> fine here for me on a current raspios pi4 under docker.
>>>
>>> https://github.com/weewx-contrib/weewx-rtldavis/tree/main/docker if you 
>>> wanted to take a look.
>>>
>>> Thanks again for posting the good starting point.
>>>
>>> On Thursday, May 21, 2026 at 8:40:35 AM UTC-7 WeatheredScientist wrote:
>>>
>>>> It is meant to be a starting point. I'm bandwidth limited at this point 
>>>> in life, so can't just pick up the skills necessary to do it right. AI was 
>>>> not just a convenience but a necessity, despite my many reservations about 
>>>> it. This was an acceptable use case in my book.
>>>>
>>>> On Thursday, May 21, 2026 at 11:06:34 AM UTC-4 Vince Skahan wrote:
>>>>
>>>>> Interesting but risky. Having done this kind of stuff for so long my 
>>>>> continued fear is minimally functional unsupportable garbage. It gave you 
>>>>> a 
>>>>> working solution ‘as a starting point’ which is fine but ‘shipping the 
>>>>> prototype’ rarely ends well. 
>>>>>
>>>>> And 100% of what it told you was fiction. You”ll not learn best 
>>>>> practices not spot security or privacy holes, nor learn what good even 
>>>>> looks like. If that works for you, cool. You scratched your itch, and 
>>>>> thanks for the github repo which is always appreciated,
>>>>>
>>>>> On Thursday, May 21, 2026 at 7:13:44 AM UTC-7 WeatheredScientist wrote:
>>>>>
>>>>>> I think it's interesting how far the LLM enabled me to go. Just 
>>>>>> setting up the configs was interesting, I saw it make a lot of the same 
>>>>>> errors I would have been likely to make (appending text strings instead 
>>>>>> of 
>>>>>> replacing, for instance). 
>>>>>>
>>>>>> Ultimately, it's working, and I've shared it on github and docker. 
>>>>>> But it's fair to challenge what's up there to make it better, and make 
>>>>>> sure 
>>>>>> there isn't anything unnecessary or sloppy. If anyone is interested in 
>>>>>> helping, I'm open to learning and improving.
>>>>>>
>>>>>> On Thursday, May 21, 2026 at 7:38:37 AM UTC-4 Greg Troxel wrote:
>>>>>>
>>>>>>> WeatheredScientist <[email protected]> writes: 
>>>>>>>
>>>>>>> > @Vince, great questions. Keeping in mind, this whole build was 
>>>>>>> heavily 
>>>>>>> > AI-assisted, i used claude to answer some of your questions, but i 
>>>>>>> think 
>>>>>>> > the responses are reasonable. Please challenge if they are slop! 
>>>>>>>
>>>>>>> Different people have different norms, but I think it's not ok to 
>>>>>>> ask 
>>>>>>> other humans to wade through and fix LLM output. It's usually overly 
>>>>>>> verbose, and wrong in ways that are harder to spot than an actual 
>>>>>>> confused human. 
>>>>>>>
>>>>>>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion visit 
https://groups.google.com/d/msgid/weewx-user/3b622830-ce4d-4a53-9099-447769c810dcn%40googlegroups.com.

Reply via email to