And all that for about a tablespoon of thyme in the end.
Thanks. This is creative. It raises many questions though:
- why RAK instead of another brand? Do others not fit?
- why those antennas instead of something else?
- how long will the battery last if we get a string of very cloudy days?
It's about #thyme!
Seriouly, this stuff grows so slowly. At least, indoors.
#gardening
Does anyone have links to build guides for some waterproof #solar + #battery + #meshtastic nodes?
I'd like to build upon the work of those that have practical experience.
#AskNostr
Pro Tip: when air drying basil, cut up the leaves first.
Basil leaves are very good at retaining water. It will take longer and you will get more browning if you dry them whole.
#garden #gardening #homestead #homesteading #prepper #prepping #food #foodstr #yum
Yeah, when I hit a high spot, I got a very nice range, even despite the trees and buildings. 🎊
It's interesting to see what makes a difference in practice, with my tx power, antenna, and so forth. People always talk about having line of sight, but that's great, but completely impractical in the midwest. There are no real hills to climb here. Also, we have lots of trees and a few 3 story buildings that get in the way.
I plan on trying to somehow schmooze some radio tower space at some point. I need to get a reliable solar powered node with an optimal antenna first. I don't want to have to climb the tower repeatedly, especially if it requires coordination/permission for each time.
I hope to find a wiki or forum or something so I can contribute my experience and learn from people who have already built & debugged solar LoRa nodes.
And yeah, tall grass prairies are a great place to hide/get lost. You can't see people 15 feet away at all. It also absorbs sound, which is pretty cool. 😁
I did several more hours of range testing the Heltec v3 #Meshtastic nodes. Is there a place to stash independent testing results and notes for others?
After the first round of testing, I moved the reviever node to the very peak of the roof to see how mych difference it made. A **LOT**, it turns out.
I can quantify that better later aftet I map everything out so I can give everyone the 2 sentence advice on what impacts reception **in practice**.
So far, it seems like RF is absorbed by trees and tall grass (like 12 ft tall, Illinois doesn't fool around when it comes to tall grass prairies!). Banking on straight roads to carry the signal (or rather, the lack of buildings and trees in the road) seems to work well. As a result, straight lines go further than diagionals. And elevation makes a big difference, exactly as you would expect.
#unlicensed #radio #mesh #emergency #prepper #prepping
The High Cost of Privacy: Is It Worth the Investment? https://fedijournal.wordpress.com/2024/10/20/the-high-cost-of-privacy-is-it-worth-the-investment/ #Ai, #Cybersecurity, #Privacy, #Security, #Technology
I've seen some people get a huge reduction in stress by increasing their privacy by doing things like installing GrapheneOS, or using Nextcloud for calenders and storing files.
I've also seen other people get more stressed out by just learning about the overehelming number of steps people recommend to increase privacy.
I do my best to try to focus on the things that require a small amount of time, give a significant benefit and don't have a bunch of gotchas. It's hard, and what I suggest depends on what the person is specifically worried about.
If people would just vote harder, we wouldn't have people being killed by ferry dock collapses.
#sarcasm #news #violence #death #vote
Too many distractions to make much progress on this. I did take some notes on data storage structures in the firmware.
I also found some structure parsing in the client, but they don't match up, so I'm guessing "block" is an overloaded term.
Once I get it straight, I'll turn my notes into documentation. I'm going yo need dedicated time to really focus on this.
Not sure about potential size restriction issues here. But I think newer versions of GPG actually support elliptic curves, so yeah, that could get the job done in a pinch.
Today's mission: find #0days in #Signet!
No, seriously, I'm writing tools to determine the impacts of a malicious client. What can the firmware defend against & what are its limitations?
Whether the code is vulnerable or secure, we should have proof. Right now the proof is "it's open source, just read the code" and that's not good enough. I want any independent security professional to be able to audit the firmware in a weekend, by themselves.
In summary #PoCorGTFO
#security #infosec #exploits
The text is more difficult to read than most sites. It doesn't need to be black and white, but more contrast might help.
I like the pictures, especially on the front page.
People have already commented on the location being unclear at first glance. I'd add that mentioning that some of your services (like classes, planning, etc.) might be helpful to people across a wide section of North America. That way people don't see Oklahoma and think they should stop paying attention because they are in Iowa.
I don't expect you'd be an expert on native plants in both Flordia, Nevada and Montana, so knowing what areas you're comfortable with would be helpful. It might be helpful to day you cover something like the midwestern USA, or between the Rockies and the Atlantic, or whatever the case may be.
Overall, I like the concept and might even be able to send some people your way if you can cover East Central Illinois and have rates my friends can afford.
Hot take: #Nostr support should be added to as many of those "we put your post on all the social media platforms/protocols" apps and services.
Why? Because nostr seems to have higher engagement and it will help show people the value of the #protocol.
If they get interested, they may set up a #lightning address to get #zaps and it could hit harder.
If there is a way to indicate that sending eCash to a nostr key will actually be noticed and received, along with a UI to see #eCash received, it could hit triple time.
In case you haven't already stumbled across nostrastic... 😁
That's weird. The ticket said it was in Izzy's repo, but didn't mention Sideband's custom repo. That must have come later.
So I guess the devs went through all the trouble of setting up and running a custom FDroid repo instead of just getting their app into the official repo?
That seems pretty strange
I'm going to have to go ahead and say no on the basis that I don't even see any instructions for getting into zap .store
I expected the "Home" link on the downloads page to take me to a page that would have more information about the project, but it just goes back to the downloads page.
I was interested in the Sideband Android app until I discovered that they closed ths ticket asking to be added to the #Fdroid repos, claiming it's too much work and not enough benefit. 😭
F-Droid reviews all apps in their default store to ensure they are really #OpenSource (or #FOSS or #FLOSS if you will) and looks for trackers. They also require a description of what changed from one version to another.
These are benefits that you don't get by installing an APK directly from Microsoft GitHub.
It's completely valid to say that benefit isn't worth the effort. That's a value judgement. To some, even a trivial amount of effort is too much. To me, it's a significant value, and if it were my project, I'd create a .yml file and submit a MR to FDroidData.
Now, the effort to make their build reproducable is a different question. That may be easy or it may take a significant effort. Whether reproducable builds are worth the effort or not depends on how much the project cares about #security. How much work it is depends on whether and other projects using buildozer have already done this. If not, it'll also depend on whether the builddozer devs are interested in helping their users do this.
https://f-droid.org/docs/Submitting_to_F-Droid_Quick_Start_Guide/
It looks like buildozer does have built-in support for reproducible builds. Their documentation is very sparse, but I found a ticket that seems to indicate this.
https://github.com/bazel-contrib/rules_oci/issues/315
Again, reproducible builds are completely independent of being included in FDroid.
I was interested in the Sideband Android app until I discovered that they closed ths ticket asking to be added to the #Fdroid repos, claiming it's too much work and not enough benefit. 😭
F-Droid reviews all apps in their default store to ensure they are really #OpenSource (or #FOSS or #FLOSS if you will) and looks for trackers. They also require a description of what changed from one version to another.
These are benefits that you don't get by installing an APK directly from Microsoft GitHub.
It's completely valid to say that benefit isn't worth the effort. That's a value judgement. To some, even a trivial amount of effort is too much. To me, it's a significant value, and if it were my project, I'd create a .yml file and submit a MR to FDroidData.
Now, the effort to make their build reproducable is a different question. That may be easy or it may take a significant effort. Whether reproducable builds are worth the effort or not depends on how much the project cares about #security. How much work it is depends on whether and other projects using buildozer have already done this. If not, it'll also depend on whether the builddozer devs are interested in helping their users do this.
https://f-droid.org/docs/Submitting_to_F-Droid_Quick_Start_Guide/