It probably has to do with the boiling point of pine resin. There are probably other less noxious substances that boil in the 300c range that would produce similar results without the risk of fire or poisoning.
Its a Nixos based Linux distribution where the Nix config and Nix flake is written for you and configured using a GUI. It attempts to bring the benefits of Nix to people who don't care to learn the insanity that the Nix language is (I say this as a full-time nixos user)
a Nix Flake is basically just a file to pin packages against a specific version (ie go.mod cargo.lock etc...) you then write a config that defines your system state and packages that you want to be available.
What's wrong with it? I'm not fond of the standard library (esp. the mkOverride and its friends), but the language itself feels fine. (Or am I just too used to it?)
Personally, I would've preferred statically-typed language with proper GADTs, but Nix is far from what I'd call "insanity". Malbodge is insanity, JavaScript is a mess (mainly because of its birth defects), Nix is... not a dream language, has a few odd bits that one needs to get used to, but feels quite okay.
I understand Nix the language if it is all in one file.
But try to call one file from another - it is confusing - the parameters are not explicit like a function call - they suddenly appear - adding more arguments is odd. Modules are not simple imports they add options and config to "help" you.
I do wish they had used a well documented language with some form of modules rather than invent their own idiosyncratic one.
Nix-the-language imports are dead simple: https://nixos.org/guides/nix-pills/05-functions-and-imports#... - `builtins.import ./foo.nix` makes it like we had `./foo.nix` copied and pasted in place of it. If we want to pass something, we make contents of `./foo.nix` a function (thus the frequently seen `import ./foo.nix {}` or `import ./foo.nix { inherit bar; }`).
Oh, and Flakes have inputs (which are closer to built-in module system, as IIRC Flake support is baked into Nix itself rather than being a part of Nixpkgs like the module system), which is another different convention, but it all boils down to using `builtins.import` somewhere deep down the chain, all extra semantics in the libraries.
Again, I would've preferred a language with module system built-in but it's not a bad design either - it's just minimalistic. IMHO, Ruby and Perl can be more confusing than this - and they're still sane (if we don't intentionally start having fun with their metaprogramming capabilities). But then Flakes probably wouldn't be a thing, so minimal core has its advantages too. Or disadvantages, as it all depends on the viewer.
Either way, it’s all well documented. I still forget how it works now and then, but that’s my memory/attention span problem rather than a Nix/Nixpkgs issue.
The language is absolutely not the problem. It's not a particularly difficult or complex language at all. In fact, it's pretty elegant and easy to understand the language. It's the things built on top of it that are difficult.
Presumably it comes from the aphorism "every snowflake is unique", which ties into Nix flakes as being uniquely identifiable units of distributed software.
I stopped donating when they declared ‘rss is too complex to be maintained and is also old and gross and stuff, so we removed it’. Oh by the way totally unrelated here is Pocket(tm)!
I’m sure we could spot what the high risk behavior in question is with your business if you provide us with the url.
But truth is, stripe decides who they want to be in business with. They have decided they don’t want to be in business with you. Tough, but they also aren’t placing you on the MATCH list or other common nightmare senerios many non-compliant businesses find themselves in when dealing with violations of payment processing guidelines.
My advice is to cut your losses with stripe and get a real merchant account.
The pre-vetting process will likely be quite clear with you about what and why your business is considered too high a risk, or you’ll end up with a less frangible business relationship you can depend on to not rug pull you in the future.
Probably related to soliciting donations (See "Businesses that are prone to abuse by fraudulent actors" on that Stripe link)
A lot of payment processors do not like it when individuals (versus certified nonprofits) take donations. Because, well, it is more prone to fraud. It's a really easy way to cash out stolen credit card numbers. The systems are set up for a transaction, not a one way transfer of funds.
"taking the wife out on date night" sounds like the kind of thing a regular nonprofit wouldn't be able to solicit donations for. I have no reason to believe that the OP is not representing that honestly or abusing it, but Stripe is not going to care.
The first linked website (https://www.barnhardt.biz/) says (if I'm understanding it correctly) some pretty unkind things about the Pope regarding to his conciliatory attitude towards homosexuality.
Stripe's page says that their prohibited categories include "Businesses that engage in, encourage, promote or celebrate unlawful violence toward any group based on ... sexual orientation..." among other things.
Practically/realistically, there's also some content in the podcast that's going to make payment processors nervous. Even if made with best intentions, legal departments will worry eventually someone is going to end up sued or worse, and the company will be named. Even algorithmic filters are likely to class this as fringe/conspiracy. So regardless of what rule they're pointing at to cut the account, they may really just want to cut the risk regardless.
For context, some random excerpts from barely a skim that jump out and are going to raise eyebrows:
203: "we attack the topic of In Vitro Fertilization and break down how this grotesque process"
195: "part of what made the fires in Hawaii worse than they needed to be: the deeply-seated paganism of the natives who worship the volcanoes"
191: "it’s possible that “they/them” pronouns are favored among trans because of the demonic they/them legion possessing such poor souls"
187: suggests extracting and storing your own blood and taking methylene blue?
I don't have all the context, and generally I do support the author's right to expression, so I'm trying to be objective and kind here. But candidly, I'd have difficult to overcome personal reservations about partnering in business with (and in Stripe's case, since they take fees: profiting from) the content here.
I don't mean to offend anyone, just seems like an elephant in the room worth noting.
Stripe is a minimal to no vetting payment processor. A real merchant account will require contracts and pre-vetting that includes a review of your payment processing history and suitability to the rules of the card networks in question.
People blame the payment processors, and they can certainly be opaque sometimes. But perhaps fairer to lay most of the blame on the fraudsters.
I’m sure Stripe would love the revenue from this enterprise, but they can’t have it without making KYC as complex as banks and losing a lot of their value prop.