Just to confirm the obvious. Downvotes are expected but OP you should read this.

They are close enough to see that they are quad copters, and they make a buzzing noise, correct?

There have been a lot of UAP flaps where the objects (not quad copter looking) will fly low over the countryside, just above the tree-lines to much higher. They usually make no noise aside from reports of static or screeching or electronic interference.

Unlikely to be the case but if so, report to your countries MUFON type department and get as much evidence (video with sound, drawings, time and date, etc) as you can.

There is something else out there, whether it's military black projects mapping areas or what have you, and it needs to be documented.

If it is for sure quad copter drones, you can get a device to blast the 2.4Ghz spectrum for a short time and make them 'phone home' and the operators will stop flying them over your property once they realize something wrong keeps happening when they do. Legality varies.

Many tutorials available to DIY. You can also buy them pre-built, just more expensive.

wget toteslegitdebian.app/installer.sh & chmod +x && ./installer.sh

was I not supposed to do that? but staxoverflown said it's OK.

I dunno. They started out with different owners. It's still fully manual (buy prepaid visa, get it in 24 hours, maybe.)

They once advertised cards that would not be detected as prepaid. Surprise, company I bought it for wouldn't accept a prepaid card, no refund just "sorry for luck maybe try another site?"

Edit I had allark and majesticbank confused.

That does go a long way towards explaining why there are so many Bluetooth vulnerabilities, thanks for the info. Looking at the list of Bluetooth protocols wiki page gives me a headache. Surely there is a better standard, and I see things like HaLow, ZigBee, Z-Wave and other custom protocols, but it seems like there should be a very cleanly well-documented alternative to do the basics that everyone expects BT to do. This, coming from a total noob, speaking completely out of my anus. I just know that as a BT user, it's a crapshoot whether there will be major audio delay, and pause/play actually worked, that's if pairing works in the first place. But if something did come along I wonder if there would even be adoption among consumer devices.

Yes, but setting the environment variables before running setup. The following two coded env vars will set your btcpay server to automatically also run a tor hidden service. Once XMR is configured (only one wallet per server at the moment) you should be able to access the hidden service and pay without issue.

Run btcpay-setup.sh with the right parameters

Set the custom domain you chose to use

export BTCPAY_HOST="btcpay.EXAMPLE.com"

Use Bitcoin on mainnet

export NBITCOIN_NETWORK="mainnet"

Enable Bitcoin support

export BTCPAYGEN_CRYPTO1="btc"

Enable Monero support

export BTCPAYGEN_CRYPTO2="xmr"

opt-add-tor enables Tor support for the UI and Bitcoin node

export BTCPAYGEN_ADDITIONAL_FRAGMENTS="opt-save-storage-xs;opt-add-tor" 

Is it true the Bluetooth network stack is larger than the WiFi network stack? If so, why? I don't know much about BT besides pairing, allowing calls and audio in/out, transferring files, and.. is there more? It takes a day of reading documentation to understand all the advanced options on my ASUS router interface, and that's without anything proprietary.

I'm just surprised and curious and never got a satisfying answer.

Survivor bias and and an ad all in one post!

When I see posts like this it gets my glowie senses tingling.

You may not like it, but this is what peak machine learning performance with 4chan training data looks like.

Honeypot? Dunno. Good discussions about it on hacker news.

In the guide you linked, the docker container automatically sets up a hidden service. You don't need to do anything beyond firewall rules if it's not working for you.

GPG/PGP turns takes the file and turns it into random bits that only someone with the private key can unrandomize. There is no file metadata left. There is no nothing left. I believe the sizes are even consistent (0-1024kB files will be the same output size.)

There's been a major DDoS against guard nodes lately as well, causing many of them to lose connecting clients so it may have been unaccessible for long enough that it kicked back to relay but I'd ask on the relay-operators mailing list/forum. They've been posting a lot of firewall rules and scripts to fend off attacks.