Ed Braaten, N7EKB

Hey #nostr #Hams! Amateur Radio Newsline is available on Fountain.fm with streaming SATs enabled! Its the first #amateurradio podcast that I've seen that's supporting value-4-value. nostr:nevent1qqswdspxedamz5260wzeyngt5s9mza8x2c79h8rtapznt9qawqasfggpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsygrnl6hgjantg4u0evz9c9gjndqan8yl04en79amvdgcuffyjdcjs5psgqqqqqqsyd699d

Added this #BitAxe to the #Hamshack today. It's solo-mining (also known as the "Bitcoin Lottery"). It's a lot quieter than I anticipated. Now it just needs to hit the lottery to help pay for some new #hamradio projects! 😀

Just getting started with "block 44" in the #hamshack. Are there any other #nostr #hams using a #block44 address? My #hamradio/#technology web site is still hosted on my VPS with an ordinary IP address, but is now also reachable at www.n7ekb.ampr.org .

A 2 watt RNode design. #reticulum #PE1RXF #nomadnet #hamradio #meshtastic #homebrew #esp32 https://www.meezenest.nl/mees/projects/reticulum_design_my_own_rnode/index.html

Looking at the below abstract from the #Reticulum manual brings the following ideas/questions to mind: How hard would it be to modify a #nostr relay to allow connections to/from a #Reticulum network? Along the same lines, how hard would it be to modify a #nostr client to utilize a #Reticulum network as a transport? #asknostr #strfry #nostrrelay #nostrclient #meshnetwork Pipe Interface Using this interface, Reticulum can use any program as an interface via stdin and stdout. This can be used to easily create virtual interfaces, or to interface with custom hardware or other systems. `````` `[[Pipe Interface]] type = PipeInterface enabled = yes # External command to execute command = netcat -l 5757 # Optional respawn delay, in seconds respawn_delay = 5 `

I don't quite understand this article. I just finished setting up my own #XMPP / #Jabber messaging server on https://xmpp.n7ekb.net. I don't get the connection between a phone plan and XMPP. Especially the comment "privacy-enhancing phone service using XMPP". #asknostr

The installation of my self-hosted Jabber/XMPP modern messaging server on #Debian is done. For the second time. That's right. I had it all up and running on a shiny new VPS a few weeks ago. I had the new installation passing with 100% compliance on https://compliance.conversations.im/server/n7ekb.net/. Then I *deleted* it instead of the old #Rocky #Linux VPS I had on the same hosting service... Of course I made this swift rookie mistake *before* I'd setup my offsite backup! Soooo. Guess what? The new re-installation is now backed up three ways to Sunday. My old friends git and rsync are happily guarding the server from this incompetent server admins! Setup for family and friends and #hamradio, https://xmpp.n7ekb.net is ready for action.

https://endof10.org/ #Linux #Windows #Windows10

My self-hosted #Nostr #Relay logs were growing, growING, GROWING! So I set out yesterday to determine exactly what was going on. Guess what I found?!? A handful of clients from different IP addresses were causing a continuous stream of error messages where the relay was complaining of a "filter item too small". So I tweaked the logging settings to get dumps of the requests generating the errors. Each error entry looked like the following: [Ingester 0 ]INFO| [21] dumpInReq: ["REQ","6zn9yubmmkm557n78kkta2e7aahjbn",{"since":1746216000,"authors":["00","01","02","03","04","05","06","07","08","09","0a","0b","0c","0d","0e","0f","10","11","12","13","14","15","16","17","18","19","1a","1b","1c","1d","1e","1f","20","21","22","23","24","25","26","27","28","29","2a","2b","2c","2d","2e","2f","30","31","32","33","34","35","36","37","38","39","3a","3b","3c","3d","3e","3f","40","41","42","43","44","45","46","47","48","49","4a","4b","4c","4d","4e","4f","50","51","52","53","54","55","56","57","58","59","5a","5b","5c","5d","5e","5f","60","61","62","63","64","65","66","67","68","69","6a","6b","6c","6d","6e","6f","70","71","72","73","74","75","76","77","78","79","7a","7b","7c","7d","7e","7f","80","81","82","83","84","85","86","87","88","89","8a","8b","8c","8d","8e","8f","90","91","92","93","94","95","96","97","98","99","9a","9b","9c","9d","9e","9f","a0","a1","a2","a3","a4","a5","a6","a7","a8","a9","aa","ab","ac","ad","ae","af","b0","b1","b2","b3","b4","b5","b6","b7","b8","b9","ba","bb","bc","bd","be","bf","c0","c1","c2","c3","c4","c5","c6","c7","c8","c9","ca","cb","cc","cd","ce","cf","d0","d1","d2","d3","d4","d5","d6","d7","d8","d9","da","db","dc","dd","de","df","e0","e1","e2","e3","e4","e5","e6","e7","e8","e9","ea","eb","ec","ed","ee","ef","f0","f1","f2","f3","f4","f5","f6","f7","f8","f9","fa","fb","fc","fd","fe","ff"]}] 2025-05-02 13:12:41.038 ( 198.848s) [Ingester 0 ]INFO| sending error to [21]: bad req: filter item too small The culprits were trying to request a list of articles with an author list that basically covers every possible Nostr ID... Or something along those lines. If you're using a nostr relay you aren't paying for, remember to #zap your relay operator. They deserve a little love from time to time! #sysadmin #admin #linux #cybersecurity #nostr is not just #bitcoin

#reticulum #rncp https://github.com/markqvist/Reticulum/discussions/804

Did some cleanup on the web page today. https://n7ekb.net #radio #xmpp #n7ekb #hamradio #nostr #reticulum #meshtastic #shortwave #nomadnet #aprs #opengd77 #jabber #ares #ni4l

Here's one for #asknostr: Filed in https://github.com/greenart7c3/Citrine/issues/61. I run #Citrine on my phone (Thank-you!!!) and also run a personal nostr relay (strfry) on my VPS so that I have two locations for all my notes. These are entirely dependent on the commercial internet however. I also run a program called #Sideband which connects to the #Reticulum network using a locally hosted transport router for Reticulum. How feasible/difficult would it be to add support in Citrine to publish/interact with my local Reticulum transport? The Reticulum transport has a lot of options: Reticulum Interfaces. Such a feature would make nostr over Reticulum possible in areas where commercial internet is unavailable (#disaster/#censorship).

Finally got around to troubleshooting my #NIP-05 setup after the move to a new #Debian #Linux server. In the process I used #Grok to research the needed Apache configuration to allow #nostr client access to the /.well-known/nostr.json file. Grok did great on the basic research query! But on my subsequent bunny trail queries it determined that I'm the ONLY #hamradio operator known to the interwebs that hosts a nostr relay! #CQ, CQ all #hams! Tell Grok you use nostr and that you host a relay! 🤪

The #Reticulum Network World #Map Project went live today: https://rmap.world/index.php I'd like to see some #EMCOMM minded #hamradio sites show up on this map. In theory #EOC client computers running reticulum-meshchat day-to-day would have transparent fallback to RF-based connectivity when their commercial TCP network goes away in a #disaster event.

Has anyone investigated the possibility of building a LoRa-like low-power transceiver for 49.82-49.90 MHz band for use as an #RNode? This might have greater range in rural, tree-covered areas that limit 800/900 MHz signal propagation. #AskNostr #reticulum #meshnetworking #mesh #LoRa #hamradio #nomadnet ( Quoting from the https://www.hfunderground.com/wiki/index.php/Part_15 ) The 49.82 MHz to 49.90 MHz band allows for personal hobby transmitters up to 100mw output with any modulation as long as the modulation stays within the 49.82-49.9 MHz band. This provision within Part 15 opens up opportunities for 49 MHz beacons, provided an effective antenna is used. § 15.235 Operation within the band 49.82–49.90 MHz. (a) The field strength of any emission within this band shall not exceed 10,000 microvolts/meter at 3 meters. The emission limit in this paragraph is based on measurement instrumentation employing an average detector. The provisions in §15.35 for limiting peak emissions apply. (b) The field strength of any emissions appearing between the band edges and up to 10 kHz above and below the band edges shall be attenuated at least 26 dB below the level of the unmodulated carrier or to the general limits in §15.209, whichever permits the higher emission levels. The field strength of any emissions removed by more than 10 kHz from the band edges shall not exceed the general radiated emission limits in §15.209. All signals exceeding 20 microvolts/meter at 3 meters shall be reported in the application for certification. (c) For a home-built intentional radiator, as defined in §15.23(a), operating within the band 49.82–49.90 MHz, the following standards may be employed: (1) The RF carrier and modulation products shall be maintained within the band 49.82–49.90 MHz. (2) The total input power to the device measured at the battery or the power line terminals shall not exceed 100 milliwatts under any condition of modulation. (3) The antenna shall be a single element, one meter or less in length, permanently mounted on the enclosure containing the device. (4) Emissions outside of this band shall be attenuated at least 20 dB below the level of the unmodulated carrier. (5) The regulations contained in §15.23 of this part apply to intentional radiators constructed under the provisions of this paragraph. (d) Cordless telephones are not permitted to operate under the provisions of this section.

#reticulum #rns #meshnetworking #mesh