openthc

Some of us still trying to use it the proper way.

If you had any pointers I'd be grateful

Not good. Stripe rejects anyone even close to the regulated cannabis space (with no room for appeal) but PayPal will accept these tranctions. So, this would put a non-zero amount of businesses (that don't even touch that deadly, deadly plant) in a tight spot with this monopolisation of the industry.

Which is super bullshit; cause now offering open source solutions many folk see it as a trick!

We create open-source software and attempt to get government agencies to adopt/use it. It's crazy how alergic these agencies are to open-source. Some will even create their own, with legacy style implementations (csv uploads, broken parsers), complete with bugs/flaws that are predicatble rather than use someone elses code.

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.

Another thing that happens to outdoor grown cannabis is pesticide contamination. Even if your farm is a good distance from some commercial agriculture, if they spray it can, and does, contaminate your crop -- which for regulated cannabis requires destruction. Literally burning (or composting) thousands of dollars of product.

And if the pesticides test are hot on the cross-contaminated cannabis; how much is on those apples three fields over?

Another thing that kinds of sucks about this whole "license rug-pull" kind of business is that other teams (like ours) who are publishing open-source software/tools are now suspects too.

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.

Bong shop in Berkeley, CA

With UUIDv7/v8 (and ULID) there are some timestamps in the front half. I've seen spots where the query was in the style of `uuid_col >= 'SOME_UUID_0000' AND ulid_col <= 'SOME_UUID_FFFF'` When one is using them ast the timing for record create/insert these things happen.

I love ULID too; but it's really just UUIDv7 (or v8) with a mustache (it's all just 128bit IDs). And in the PG world, where there isn't native support for ULID one can use UUIDv7/8 and bridge that gap. We use ULID extensively in exposed IDs, it's very URL friendly, copy/paste friendly, etc -- but it's a UUID datatype in the DB. (ie: ULID => UUID => DB)