641 karma · joined August 12, 2018
Or email the help@ my domain
That and not supporting B2B transactions via their API. They would alternately claim it's for security or that the States were not asking for it. States would tell other software vendors that Metrc coludn't do it. Neither party could move the ball.
Only now, in 2023, have they started responding with the ID of the newly created items (why not a fully inflated record of what was just created) and working to support B2B.
These state run APIs, from a for-profit corporation, are not good for the public (they hide, or cannot handle important laboratory testing data) and they are not good for the licensees, especially the small businesses. And there is no accountability -- agency points to vendor & vendor points to agency.
Sadly, getting these State agencies to understand the beauty of distributed/federated systems -- and the difficutly for small businesses to respond to RFPs -- keep us from having nice things.
End of rant.
It's way more fun to debug than some single-monster code base with a complete stack-trace from the single-process. That basically tells you exactly where to look and how it got there! What fun is that, where's the adventure!?
But the higher-level Apps we publish under GPL, so that downstream is obligated to keep it open-source (but there is no obligation to submit a PR upstream).
And there are more than a few companies that use our GPL stuff, internally and don't redistrubute and therefore don't have to make their internal modifications available under GPL -- because there is no distribution happening.
I'm not a lawyer but our decision was informed by one who has prior experience in IP, licensing and specifically FOSS-style licenses.
Stars are a vanity metric but, they can help with monitoring some early growth.
Everyone on this thread should list their projects, then we all star each others stuff all the way up!
Update: It's now YELLOW -- inside of 5 minutes of my own observation of the outage.
remote: Resolving deltas: 100% (4/4), completed with 4 local objects.
remote: fatal error in commit_refs
To $REPO
! [remote rejected] main -> main (failure)
error: failed to push some refs to '$REPO'
Status Page: https://www.githubstatus.com/ -- actually shows red -- it was almost updated as fast as HN.https://www.washingtonpost.com/archive/politics/2002/01/14/b...
Total jerk.
https://pubmed.ncbi.nlm.nih.gov/2554344/
https://www.algonquincollege.com/umbrellaproject/dont-hold-y...
But one of our crew found info on Crunchbase about Alameda Research + Moonstone and we nope-d out of that deal. They said "we don’t have any risk or exposure from Alameda Research" -- but, still -- too close for comfort
We don't care if our chat is search-indexed; it's mostly internal; there are client channels, specific topic channels. At least for our case being OUT OF SEARCH is better. However, we do use the conversation as seeds for our help-docs, blog post, etc, etc.
Perhaps Linen could be the winner by putting Slack+Discord+Mattermost+Matrix+ActivityPub in to a better search-index.
Anyone remember MARC? -- https://marc.info/
You have to write to the SQLite via the rqlite HTTP API but it will replicate the data to N nodes (at least 20) via RAFT and then others can read-only the SQLite replica files directly; and file-permissions prevent the accidental write.