That’s too much organic material in the water and it will start competing with the BTI when it starts decaying (spoke with manufacturer/inventor’s son).
A couple improvements are to:
- Add bifenthrin to the sticks
- Use a black bucket for better attraction
- Consider spinosad vs BTI for longer lasting larvicide action
I have a big Obsidian file if anyone’s interested.
Annoying that they don’t mention the third party cloud provider (legal reasons?), so we have to assume. The evidence of their architectural reliance on GCP for storage is the most likely culprit I’ve come across. Is that right?
And then, assuming, between GCP and Cloudflare being down, the rest of the dominos fall.
Is this directionally accurate? What’s wrong or missing?
It’s so great this app is getting attention. Hopefully the devs/PMs come here and pay attention.
The sound ID works very well, especially in the jungles/forests of Colombia with zero network availability.
The rest of the app needs a lot of love, though. Buttons don’t work often, screens are inconsistent, results get lost, and more issues.
Features: I’d love an iNaturalist bridge. Going back into a previous recording shows “No matches” when the original capture did. Many times we’re with groups in nature, and we ID something, but it’s gone by the time we show it to someone.
A quick starting point would be to add a quick feedback button vs opening a web form, so issues can be reported conveniently.
And a resounding thank you to everyone making this app possible!
Playing last weekend I extracted the audio using yt-dlp, ran that through Whisper (found the quality of that better than YT subs/transcript).
However, then I ran into the 2048 token limit for longer videos. Because it doesn’t hold the full context, it wasn’t good enough at summarizing or providing insights.
The solution is to do smaller summaries of 2048 chunks recursively until you have a single one.
This felt and worked… meh.
We’re you able to get around this in some other clever way?
We're launching a remote-first and video-first communication environment for modern teams. We recently closed our seed round and are staffing up. Our tech stack is React/React Native/TypeScript, Electron, Java (moving to Node), WebRTC, and more.
One important factor that this statement doesn't take into account is that you can only approximate understanding what the other person is going to understand when they read what you expressed. This becomes harder when it's more than one person receiving the message.
Step 6 shows olives that seem tp have been scored (cut). I couldn't find a reference to this in the previous steps. Did I miss it? Is this something that should be done?
Thanks for this! We had a bunch of olives on a property and some of the pickling worked while others didn't. This will be quite helpful.
A couple improvements are to: - Add bifenthrin to the sticks - Use a black bucket for better attraction - Consider spinosad vs BTI for longer lasting larvicide action
I have a big Obsidian file if anyone’s interested.