2bluesc

I'm surprised they don't allow exit nodes to function as funnel servers.

Seems to me this would save them the hassle of dealing with the bandwidth.

I'd love to learn what the bandwidth limits are.

Interesting, this is blocked by CloudFlare's 1.1.1.2 malware DNS service:

    $ drill -Q @1.1.1.2 share.ipfs.io -> 0.0.0.0
    $ drill -Q @1.1.1.1 share.ipfs.io -> 209.94.78.1

Suppose it's probably a popular method to exfiltrate data for malware?

Wish I would see more mentions of `podman` where you can just run a container without a daemon and all permissions issues (root by default in Docker).

Podman seems like a simpler container management tool for things that are merely wrapping/emulating traditional command line tools.

I had an entire Comcast account registered to someone with the same name in another part of the state that took me years to get rid of. Could even login with my email address because he registered it to my account and somehow the email side stepped verification.

Imagine dealing with Comcast customer support. Then imagine not even being a customer anymore trying to get this resolved. Now imagine explaining how you're not the person on the account yet have the same name and how this is a huge privacy/security violation.

Took years to get rid of. One day I'm waiting for a silly collections bill or something to show up in "my" name for the other person.

I've used this kernel on some products and would recommend staying away when possible because you're kind of stuck in a corner wrt to feature and security updates.

Most of Xilinx's SoCs are very close to working on mainline kernels out of the box. You'll need to build/patch some advanced FPGA features, but with nothing more then a kernel config you'll have a functioning Linux system.

IMHO, putting in the work to use a mainline kernel (and Yocto in place of petalinux) is well worth it in the long run for real products.

Xilinx is to be commended for their efforts to mainline many features.

Petalinux and linux-xlnx are ultimately early dev and platform demonstration tools. They provide many features, but are lacking polish and stability needed for real products.

Wow, totally unaware of the performance speed-up 5x over sha1 and blake2b. Even more for others!

Are there cases where the benchmark doesn't hold true? Different architectures?

I'm inclined to use this on some less security sensitive things I need a hash for.

Traefik Proxy[0] was a game changer for my self-hosted setup of Docker containers.

Traefik can read labels applied to Docker containers (easily done with docker-compose) and setup the proxy for you as containers come and go. Even maintains the Lets Encrypt certificates seamlessly.

[0] https://traefik.io/traefik/

Probably not if the Helium 5G offering is similar to their LoRaWan stuff.

Due to some security issues with the Helium LoRaWAN proof-of-coverage, only authorized hotspots/access points are allowed to participate. Helium manages this by issuing keys or certificates (IDK which it is) via the Decentralized Wireless Alliance[0].

I think it's highly unlikely Amazon would deploy Helium enabled 5G radios.

[0] https://dewi.org/

Helium is (initially) focused on shipping a LoRaWAN[0] network with a crowd sourced model for Lora RF hotspots that uses blockchain for to pay incentives to those supporting the network (via hardware, power, bandwidth). LoRaWAN focuses on low power, very low bandwidth, long range devices like sensor networks and simple controls.

Nearest competitor to Helium's LoRaWAN deployment that I'm aware of is The Things Network[1] which has no incentive model and instead people often host an access point for their personal use and sometimes for the use of those nearby.

Helium is expanding to CBRS[2] 5G service which will offer traditional higher bandwidth services, but this deployment is very early and the first units are shipping next month from FreedomFi[3].

Coolest thing about the Helium LoRaWAN offering is that you can buy a $20 ESP32 microcontroller with Lora radio on Amazon, write some software, buy Helium data credits and use it anywhere helium has coverage. No contracts, no special hardware. And if it sucks you could switch your application to use another LoRaWAN offering (The Things Network). That said, I think the coverage of Helium vastly outpaces anything else because of the crypto incentives fueling the madness and growth. [4]

[0] https://en.wikipedia.org/wiki/LoRa

[1] https://www.thethingsnetwork.org/

[2] https://en.wikipedia.org/wiki/Citizens_Broadband_Radio_Servi...

[3] https://freedomfi.com/

[4] https://explorer.helium.com/coverage

There's a comparison halfway down wallet page. Seems the main benefits are:

* Browser native (obviously)

* Open license (not familiar with MetaMask license)

* Live market data via CoinGecko

* Reduced resources (seems to fold in to browser native integration)

Also quote from the FAQ:

> Q: What makes Brave Wallet better than other wallets?

> A: Most crypto wallets are browser extensions. These extensions have inherent security risks, and are much more susceptible to account spoofing and asset theft. Extensions also require extra CPU to run, creating performance issues on your device.

> Brave Wallet, by contrast, is browser native. With Brave Wallet, there’s much less risk of account spoofing, phishing, and other scams. It requires less CPU to operate, and is overall much more performant and reliable. Brave Wallet allows you to connect other self-custody or hardware wallets and other web3 DApps, see live market data, and manage your portfolio all in one place.

It supports Ledger and Trezor hardware wallets to sign transactions like MetaMask.

> Firefox development conflicting with my environment

https://bugzilla.mozilla.org/show_bug.cgi?id=360323

Oops, good catch.

I wrote similar onfailure script[0] for failing systemd services that could be invoked by the `Onfailure` unit option[1].

[0] https://github.com/kylemanna/systemd-utils/tree/master/onfai...

[1] https://www.freedesktop.org/software/systemd/man/systemd.uni...

Should probably include "[2019]" in title as I thought there was some recent update.

The dm-verity feature was merged to the mainline kernel for the 5.4 release which was tagged on Nov 24, 2019.

Never bought a PMS5003, couldn't find any real data suggesting it was better. The only indication I had was the PMSA003 was newer, so I ran with it.

I've had one running 24/7 for 9 months now with no issues. I checked the accuracy outdoors relative to PurpleAir sensors in the area and they were with a percent or two which was pretty close for such a simple experiment.

I built a similar thing last year affectionately named "Sniffer"[0]. My build uses the newer PMSA003.

* Uses an ESP32 + ESPHome + PMSA003 + BME680.

* Data collection is via MQTT -> HomeAssistant -> InfluxDB -> Grafana.

* Software and PCB design files are on Github[1].

Looks like adding the SenseAir CO2 module would be trivial with ESPHome[2]

[0] https://blog.kylemanna.com/hardware/sniffer-air-quality-moni...

[1] https://github.com/kylemanna/sniffer

[2] https://esphome.io/components/sensor/senseair.html

One of the most painful things about using tumxp is modifying the YAML to make it useful.

Was hopeful this would leverage TOML as it's built using rust.

Anyone looking for an open reverse proxy should checkout frp[0].

I stumbled on frp and inlets some time back and frp had an amazing feature set yet I had never heard of it.

[0] https://github.com/fatedier/frp

Kind of close with TokenSets[0] managing Mirror[1] backed assets.

Things like the DeFi Pulse Index[2][3] I believe are automatically re-balanced by evaluating the weights on the third week of the month and then applied the first business day of the following month. I'm not sure if a human is involved?

[0] https://www.tokensets.com/portfolio/dpi

[1] https://mirror.finance/

[2] https://www.tokensets.com/portfolio/dpi

[3] https://www.pulse.inc/

What support exactly? Years ago I added Yubikey support[0] to KeePassXC. You'd have to migrate your database to KeePassXC and you could use any combination of keyfile, password, and YubiKey.

[0] https://github.com/keepassxreboot/keepassxc/pull/127

Didn't know this, makes sense. Least the UI still seems pretty nice almost 4 years later and not ruined by other non "decent" parts.

For those curious: https://www.coindesk.com/kraken-acquires-digital-currency-da...

Also I think it's admirable that the cryptwat.ch web page is mostly free and ready to use (+ features for some fees) and no where above the fold are they promoting Kraken to funnel users in.

Looks like they just want to make a solid trade UI. In my case I had to know who was behind the tools (I always look for conflict of interest in finance) and fell in love and made the leap.

They even post an actual _comprehensive_ changelog. How often does this happen? Usually it's some product marketing framed blog post.

https://docs.cryptowat.ch/home/updates/changelog

Another vote for Kraken.

I discovered https://cryptowat.ch and thought it was the most polished and feature rich trading UI I had seen for crypto. I later learned this is a Kraken project that works with any exchanges and that they use mostly the same UI for their trade UI. After poking around the UI I was convinced they cared about UI/UX and their fees seemed better and I made the jump. Haven't looked back to Coinbase since.

This is true when writing to a file. The goal of my PoC was to not write a file and instead to stream to the web browser.

> I need to open a very large CSV file in Python, which is around 25GB in .zip format. Any idea how to do this in a streaming way, i.e. stopping after reading the first few thousand rows?

Replace the `file_paths` list in my proof of concept with your large file(s), delete the rest (lines 61-68, 77-79) and it should just work.

As a borg user I've been quite happy after iterating between rolling my own and managing the headaches.

My most recent memory of borg was when I realized I'd been backing up superfluous files I didn't expect. I thought I'd be stuck with them until the end of time because they've made it in to my long term snapshots. Fortunately `borg recreate` did exactly what I needed and didn't feel as dangerous as the page suggests.

I built a streaming zip app using nothing more then the Python stdlib zip implementation and some os primitives.

It runs on a small embedded device that can stream zip archives many times larger then the disk or system ram without any issue.

Example Python Falcon Proof of Concept:

https://gist.github.com/kylemanna/1e22bbf31b7e5ae84bbdfa32c6...

Other then what Python's zipfile buffers in memory, my implementation shouldn't use much more then a os.pipe()'s buffer (typically 64kB?).

I'm a big fan of cgdb;

https://cgdb.github.io/

Works great for native and cross compiled apps