641 karma · joined August 12, 2018
Or email the help@ my domain
""Open-Source Low-Latency Accelerated Linux WebRTC HTML5 Remote Desktop Streaming Platform for Self-Hosting, Containers, Kubernetes, or Cloud/HPC""
When responding to RFPs, the open-source stuff has an a higher level of scrutinty than the closed systems. Like, if it's open then you have to show it's good but if it's closed the vendor just says "yep, we are perfect" and the agency could move on. It feels like the agency, and the employees don't want any responsibility. But I've never seen anyone lose their government job from some incompetence.
I just got a message from WA-LCB today with updated pesticide information, working with WSU, so here's some details -- https://agr.wa.gov/departments/cannabis/pesticide-use
And here's the Action Limits defined in WA law: https://app.leg.wa.gov/WAC/default.aspx?cite=314-55-108
And if the pesticides test are hot on the cross-contaminated cannabis; how much is on those apples three fields over?
Folk ask themselves, why contribute to this thing (MIT/GPL licenses) if there some for-profit entity involved?
Folk can't take us at face-value (I'd argue demonstrated value) and level (unfounded) accusations at us; because some other player did things "dirty".
Well, other folk wanted to pay for support/customisation and in USA you make a for-profit entity to do that. So the corporate part of the open-source project is, nearly, a requirement.
- https://alex7kom.github.io/nano-nanoid-cc/ - https://devina.io/collision-calculator
Perhaps they let this one slip through because their team was too busy dragging out the review process for our cannabis compliance application, they can only afford so many reviewers after all. We wouldn't want children accidentally getting their hands on regulatory compliance data for deadly deadly cannabis. (which could happen with our application, after they had signed up and verified their agency cannabis license (which only takes many months/years and $$$$$s to get))
In one case; we spent like a year with an agency working on design goals for a track-and-trace system. At the end, they had only one conclusive finding -- use algorithimic IDs for a distrubted/federated type system; they even stated in the findings to use 128bit IDs (eg: ULID/UUID). Then when they implemented their system; that wasn't indidcated as a requirement and the other soft-findings from their year long study were completely ignored.
https://www.forbes.com/sites/forbes-personal-shopper/2023/11...
Why not shake-up CEOs of AI if the "CEO of cannabis" is doing wild thing?
And more importantly, in 2014 when the regulated cannabis industry started -- electronic only would have blocked it -- or created an additional huge hurdle. It's taken eight years to get to this crap-tastick hack of workarounds and outright lies.
Here's some core-fee details: https://gravitypayments.com/support-library/card-brand-fees/
And Gravity's general fee range here: https://www.cardpaymentoptions.com/credit-card-processors/gr...
This is because 100% of the electronic payment players currently block it; and they block it because the federal government blocks it.
The only path to legalized cannabis there would have been at the federal level; it would have blocked 20+ states with their experiments.