Well, the title was mostly a take from this post:

• Help designing a tiny solar system

But I guess I should have said a “PV system”? Or do you have a better name?

We’re not looking to be tied to a grid outside the community. Do you have any links to recommended resources to learn more about microgrids and/or community grids?

If it were me and I understand correctly I would probably not tie the systems together.

Well, the loads of the buildings are different, so tieing them together would be very beneficial. For example, one building is a workshop with lots of power tools and heavy machinery and some other buildings (with equal sq meter rooftops) are residential (with less energy requirements)

Thank you for your input, but I think it’s worth mentioning that that’s absolutely not true.

To be clear: I’m not asking for a no-KYC solution. I’m happy to auth with my company’s official government-issued registration records, with my personal government-issued ID, etc.

I’m not aware of any regulations that require a phone number. There are regulations (eg UK’s PSD2) that effectively require 2FA – and many banks chose to implement this requirement via phone numbers.

Hopefully one day the regulations will explicitly prohibit 2FA OTPs from being transmitted at all (ie so banks are forced to use secure 2FA methods like TOTP or U2F instead of insecure methods like SMS, email, etc). But currently I’m not aware of any KYC regulations that require a phone number from the customer.

You associate everything that can be bought with cryptocurrency as a scam? It sounds like you haven’t even read the post. I spent a lot of time making it easily accessible here on Lemmy. You don’t even have to click the link. Just scroll-up and read :)

How exactly did you come to the conclusion that this is a scam? We’re a fully open-source hardware & software project that’s been around for a few years. If you don’t want to buy from us, we go out of our way to help users build their own 3D-printed BusKill cables (currently in prototype stage).

• https://www.buskill.in/tag/3d-printing/

Our software is free as in speech and free as in beer under the CC BY-SA and GNU GPL licenses.

• https://github.com/buskill/buskill-app

Thank you for supporting open-source security hardware <3

This article is literally a guide to building your own.

I build open-source USB Dead Man Switches and the accompanying (also free) software

Watch the BusKill Explainer Video for more info youtube.com/v/qPwyoD_cQR4

You attach the kill cable to your body and if the connection between you to your computer is severed, then your device will lock, shutdown, or shred its encryption keys. It’s designed to protect high-risk users’ data. Data could include private keys (eg theft of cryptocurrency assets), contacts of correspondence (eg sources of a journalist – such as whistleblowers), etc.

It’s called cross-posting. Welcome to Lemmy.

Theft of high-risk users’ data. Data could include private keys (eg theft of cryptocurrency assets), contacts of correspondence (eg sources of a journalist – such as whistleblowers), etc.

For more information, see the Who Uses BusKill? section of the documentation.

• https://docs.buskill.in/buskill-app/en/stable/introduction/what.html#who-uses-buskill

I’m curious if any security engineers have covered this incident.

Stripe does support generating Restricted API Keys. With “Restricted API Keys” you’re able to mint a key that can live on your e-commerce website that has permission to accept payments but does not have permission to modify your merchant account’s payout methods (eg adding a new “Instant Payments” debit card to the merchant account as this attacker did).

Unfortunately, I’ve asked WooCommerce to support Restricted API Keys 1 year ago, but they marked it as “low priority”

• https://github.com/woocommerce/woocommerce-gateway-stripe/issues/634#issuecomment-1168340952

…I would appreciate if more people would jump-in on ^ that ticket and scold WooCommerce so that they add support for Restricted API Keys ;)

I’m curious if any security engineers have covered this incident.

Stripe does support generating Restricted API Keys. With “Restricted API Keys” you’re able to mint a key that can live on your e-commerce website that has permission to accept payments but does not have permission to modify your merchant account’s payout methods (eg adding a new “Instant Payments” debit card to the merchant account as this attacker did).

Unfortunately, I’ve asked WooCommerce to support Restricted API Keys 1 year ago, but they marked it as “low priority”

• https://github.com/woocommerce/woocommerce-gateway-stripe/issues/634#issuecomment-1168340952

…I would appreciate if more people would jump-in on ^ that ticket and scold WooCommerce so that they add support for Restricted API Keys ;)

Everything is blocked by beehaw lol