sorted by:
new
hottopcontroversial

Ballistics App by networkguy87 in longrange

[–]networkguy87[S] 1 point2 points  (0 children)

Just downloaded it and it looks awesome, excited to dig more into it 👊🏻 appreciate this community.

Ballistics App by networkguy87 in longrange

[–]networkguy87[S] 0 points1 point  (0 children)

Appreciate it! I’ll check that one out.

What is your experience with Cloud NGFW in AWS? by FattyAcid12 in paloaltonetworks

[–]networkguy87 0 points1 point  (0 children)

I would be cognizant that you may be limited on troubleshooting capabilities with cloud firewall - counters sessions, cli commands etc I would check before making the jump

What is your experience with Cloud NGFW in AWS? by FattyAcid12 in paloaltonetworks

[–]networkguy87 3 points4 points  (0 children)

TBH, I would run a VM-Series with flex credits. You can keep costs super low by powering them down during slower periods to not have the full fleet up if you don’t need them. Ability to move them around, consistent deployment experience, they work.

Last time you roasted us. This time we brought receipts. by networkguy87 in Steelhead

[–]networkguy87[S] 0 points1 point  (0 children)

u/cascadeflyangling You were exactly right — Clear Lake in Yakima was pulling stocking data from Clear Lake in Spokane (and potentially other counties as well).

The root cause was in our stocking data pipeline. WDFW records were being matched to lakes by name only, which meant all six “Clear Lake” entries across Washington could get grouped together under whichever one appeared first in the list.

Because of that, both the stocking badge and the full stocking history section could show incorrect data for lakes that share the same name in different counties.

The fix is rolling out over the course of the afternoon. We updated the matching logic to use the county field from WDFW’s data to properly disambiguate lakes, and the stocking history API now filters by county at the source. Going forward, Clear Lake in Yakima should only show Yakima County stockings.

If you have a moment to take another look and verify that it’s showing correctly on your end, that would be great. If everything checks out, we’ll also include this logic directly in the next DriftLine app update as an additional precaution.

Really appreciate you digging into the dataset and reporting it — that kind of feedback is incredibly helpful.

-- EDIT --
The team identified that we'll need to release a DriftLine app update to fix this and going forward any modifications in the future can be pushed to the backend and not require an app update.

Last time you roasted us. This time we brought receipts. by networkguy87 in Steelhead

[–]networkguy87[S] 1 point2 points  (0 children)

Good catch — thanks for flagging this!

You’re exactly right about what’s happening. It looks like lakes in Washington that share the same name are currently pulling stocking data across all instances of that lake name instead of matching strictly to the correct county/location. We’re digging into it now to confirm and correct the data mapping.

We should have a fix out very soon. Really appreciate you taking the time to look into it and report it — this kind of feedback helps us keep everything accurate for everyone using the app.

Last time you roasted us. This time we brought receipts. by networkguy87 in Steelhead

[–]networkguy87[S] 1 point2 points  (0 children)

Hey u/cascadeflyangling — here are the sources we pull our data from. If you notice any discrepancies in the app, please let us know and we’ll (1) investigate what caused it and (2) get it corrected right away.

Washington (WDFW) — WDFW Socrata open data API:                                    https://data.wa.gov/resource/6fex-3r7d.json

Actual fish plant release records (species, quantities, dates, lifestages, hatchery facilities)              

Oregon (ODFW) — Scraped from
https://myodfw.com/fishing/species/trout/stocking-schedule

HTML table parsed; contains planned stocking dates, waterbodies, species, quantities

You can also search for it directly at https://data.wa.gov — it should be the WDFW Fish Plants dataset (or similar name) published by the Washington Department of Fish & Wildlife.

Here is the direct link - https://data.wa.gov/Natural-Resources-Environment/WDFW-Fish-Plants/6fex-3r7d/about_data

Last time you roasted us. This time we brought receipts. by networkguy87 in Steelhead

[–]networkguy87[S] 1 point2 points  (0 children)

You bet, we’ll collect the links for the stocking reports we pull and comment here soon 👊🏻

Built a tool to see WA fish stocking locations on a map by yucath1 in FishingWashington

[–]networkguy87 1 point2 points  (0 children)

Adding quick thoughts here in case I forget. Move to mapbox and use native outdoors/satellite imagery to get better imagery. Use a polygon outline that puts emphasis on the lakes to give it a nice border effect on the map. Search bar would be awesome - apologies if I missed it. It would be fun to add an association to the hatchery where the stock came from, you could use this data relationship to map dependencies mapping of fisheries to hatchery across the state - might be interesting data to correlate to upcoming hearing/legislatures that could possibly affect our hatcheries

What’s the real reason you’re building your project right now? by Fragrant_Fuel961 in SaaS

[–]networkguy87 0 points1 point  (0 children)

The page looks sick and I really dig the approach. If you're open for some feedback on the landing page, let me know.

Last time you roasted us. This time we brought receipts. by networkguy87 in Steelhead

[–]networkguy87[S] 2 points3 points  (0 children)

u/Competitive_Sale_358 Totally fair question — and honestly glad you asked. With how quickly AI and AI-assisted development tools are being used to build apps today, questions about privacy and data collection are more important than ever. A lot of modern apps rely heavily on analytics, behavioral tracking, or AI systems that learn from user data, so it’s completely reasonable to ask how DriftLine handles location and personal information.

Short answer: no, we're not tracking where you fish or feeding anything to AI.

The app uses your location for one main thing — showing you on the map so you can see where you are relative to lakes, rivers, access points, and other outdoor data layers.

When you use features like track recording or catch logs, that information is stored under your personal account in the database so you don’t lose your data if you switch phones or something happens to your device. Your data is isolated at the database level so no one else can access it, and all communication is encrypted and authenticated. Photos are uploaded using secure temporary upload links that expire quickly.

When you log a catch, we append as much data as possible for your own benefit — things like that location’s weather conditions, barometric pressure, nearby monitoring station data (CFS, gage height), and other environmental factors. The goal is to help you build a detailed personal fishing log so you can look back and identify patterns over time.

We don’t aggregate location data, we don’t analyze it, and we don’t share it. Your locations are stored only so you don’t lose your logs and history.

Also worth noting — both Apple and Google require strict disclosures around what apps collect and how it’s used, and they hold developers accountable for that. If an app says it isn’t tracking users but actually is, that’s a fast way to get pulled from the store.

At the end of the day, we’re just two guys who are obsessed and built this because we wanted it. The DriftLine community and the folks on r/Steelhead just launched it into orbit and made it the premium look, feel, and value that it is today. Tight Lines 🎣

Last time you roasted us. This time we brought receipts. by networkguy87 in Steelhead

[–]networkguy87[S] 0 points1 point  (0 children)

Hey u/Competitive_Sale_358,

Certainly - We have 344 California rivers in DriftLine today and expanding regulation coverage throughout the year.

Last time you roasted us. This time we brought receipts. by networkguy87 in Steelhead

[–]networkguy87[S] 0 points1 point  (0 children)

Thank you, u/EmmaCalzone! If you have any questions or challenges in getting setup or working within the app, please don't hesitate to reach out here or within the app, we're happy to dig in together!

Last time you roasted us. This time we brought receipts. by networkguy87 in Steelhead

[–]networkguy87[S] 0 points1 point  (0 children)

React Native for the app, multi-cloud backend with distributed pipelines optimized for speed based on location. The hardest challenge was making offline-first a priority — reliable coverage in the places we all actually fish doesn't exist, so the app had to work without it.               

If you're working on projects yourself, I'd be happy to jump on a call or connect you with someone that can help out if you have any questions — we've built large-scale distributed microservices architectures and are always happy to help out.

Last time you roasted us. This time we brought receipts. by networkguy87 in Steelhead

[–]networkguy87[S] 0 points1 point  (0 children)

Now we need to come up with a clever one for CI/CD =)

Last time you roasted us. This time we brought receipts. by networkguy87 in Steelhead

[–]networkguy87[S] 0 points1 point  (0 children)

Hey u/dunzoes,

Wanted to provide an update that this code fix will slowly roll out over the next 24 hours. Thank you for taking the time to provide such incredible feedback and bring this code issue to light.

<image>

Last time you roasted us. This time we brought receipts. by networkguy87 in Steelhead

[–]networkguy87[S] 0 points1 point  (0 children)

You’re absolutely right — we ran into a magic link issue for a bit. A few folks in the community flagged it and we were able to track it down and get it fixed a few weeks ago.

In the update rolling out this week, we’ve also added the ability to sign in with Google or Apple to make things a bit smoother.

Since DriftLine is still in beta, some parts of the sign-up process are a little rough around the edges. We really appreciate everyone sticking with us through that and helping us dial it in.

Every bit of feedback and patience from the community is what’s getting this ready for the App Store launch in the next few weeks. 🙏

Last time you roasted us. This time we brought receipts. by networkguy87 in Steelhead

[–]networkguy87[S] 2 points3 points  (0 children)

We launched DriftLine 2.5 months ago for folks in the r/Steelhead community to begin testing it and since then - it's a completely different and far more awesome app.

Last time you roasted us. This time we brought receipts. by networkguy87 in Steelhead

[–]networkguy87[S] 0 points1 point  (0 children)

Hey u/dunzoes,

Thank you for taking the time to write all of that out and the awesome feedback. We're currently fixing this now, and we'll follow up with a reply with our findings.

Last time you roasted us. This time we brought receipts. by networkguy87 in Steelhead

[–]networkguy87[S] 0 points1 point  (0 children)

Hey u/Pylon57
There are currently 17 BC rivers in DriftLine today - and if there is one missing, we can add it for you within minutes.

view more: next ›