As your keybase user run:
$ keybase bot token create > /tmp/bot-token
You'll get back a base64 token, like: 6C37sjCBgMNf06Z6oTgixIxHJpja8G-Qp. This is your bot token that allows you to sign up bots.
Researched by Robert Quattlebaum darco@deepdarc.com.
Last updated 2020-02-03.
This gist is to configure a Mosquitto MQTT Broker behind a Traefik reverse-proxy, both in a docker container. Mosquitto will be configuread as a TCP Service.
This is a simple configuration used on the same single server. Probably to be adapted for other cases. Having mosquitto behind a reverse proxy enables you to configure TLS on Traefik (likely you already do that for other applications as well) and to load balance different MQTT instances, but that goes beyond this gist.
As noted in Traefik docs, in the router you must use the rule HostSNI(`*`) when using non-TLS routers like in this example. Ref. https://docs.traefik.io/routing/routers/#rule_1
docker-compose.yml
(^ that's a short-link to this page, so you can open it in Linux)
Some users are discussing this guide in #hacking on the JoyConDroid Discord: https://discord.gg/SQNEx9v.
DO NOT ask for, or share links to, Amiibo bins in the comments! They will be removed. Thank you for understanding.
| # official docs: https://graphql-ruby.org/dataloader/sources.html | |
| # app/graphql/sources/association.rb | |
| class Sources::Association < ::GraphQL::Dataloader::Source | |
| def initialize(association_name, scope = nil) | |
| @association_name = association_name | |
| @scope = scope | |
| end | |
| def fetch(records) |
java -jar gp.jar -d \
-a 00a4040010C238E449F725B1510EAA699550CABA16 \
-a 00f00000 \
-a c0d6030510404142434445464748494a4b4c4d4e4f \
-a c0d6032110404142434445464748494a4b4c4d4e4f \
-a c0d6033D10404142434445464748494a4b4c4d4e4fA newer version of this info is available at https://badcfe.org/how-to-paxton-with-rfidler/
Paxton fobs and readers are popular in the UK especially the Net2 system where the fobs look like this with a blue ring:

Paxton readers often look like this:
A list of rewritable RFID blanks that are compatible with Flipper Zero.
X indicates a particular protocol is writable.
? indicates it is unknown if a particular protocol is writable.
| Brand | Type | Chip | EM4100 | H10301 | Indala26 | IoProxXSF | AWID | FDX-A | FDX-B | HIDProx | HIDExt | Pyramid | Viking | Jablotron | Paradox | PAC/Stanley | Keri | Gallagher |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ETEKJOY | Fob | EM4305 | X | X | X | X | X | X |
| Term | Meaning |
|---|---|
| WUP-SAK | SAK Value found during the Wake up & Anti-collision process, what you would see reported from a basic search. |
| Vanity SAK | SAK Value represented in Block 0 of a Mifare Classic, on legitimate cards this does not inform the value of the WUP-SAK. |
| Magic Card | An illegitimate card capable of changing it's UID; some magic cards are also able to change other values such as ATQA/SAK. |
Here is somethig you might find useful: automatic pio assembly -> h file generation for platformio.
I have tested it on Linux only.
The pioasm tool by earlephilhower has been removed from the official Platformio repository, thus installing it requires choosing the correct version (OS) from the releases and providing a direct link to the package.
Visit the tool release page: