I'm looking into using pass / keepass, any particular reason you are switching over to pass?

I think I'm currently in a minimalist phase; the KeePassX UI is too feature rich and cluttered and makes me want to configure everything but I don't want to manage that.

If that's not a problem for you, KeePassX is definitely a solid password manager!

How would availability of the data compare? Will the stored files be available at all times & under high loads?

There are tiers of hosts/miners with different options.

Cool! May I ask how do you hook it up with opening / closing lid, sticking usb drive etc?

I simply do `udevadm monitor | telltg & i3lock`.

It's ugly to look at, but the idea is that you should never receive any logs, if you do, don't look at them but rather get your laptop in sight quickly because something is happening to it (I use it in the public library or such settings).

I personally curl a slack webhook that sends me a message.

If the task is already running, ctrl + z and run bg. Then i run `wait <pid> && slack 'job done' `

Adding on to this, how do you guys version control your notebooks?

We still just check them in directly. Not great, but it works. You can at least have github render the notebook at any point.

300 rides x average of approx. $15 per ride = $4500.

Cars here require a certificate of entitlement that cost around $100k and only last for 10 years if im not mistaken. So if he continued taking 300 rides every year for 10 years it would still be half as expensive.

This might very well backfire on them. The buyers will want to buy at the lower price and the seller would want the higher price. Both parties end up being unhappy even if the end price was within the given band.

Advertising in my experience as an end user has been very ineffective.

The ads that I see on Facebook are very obviously based on my browsing history/cookies - I look at a mechanical keyboard on Lazada and decide to not buy it. Next I go to Facebook and get ads about a keyboard on Lazada - no discounts, exact same model. It could've shown me similar keyboards, gave me a lower price, or anything that adds value than just showing me the exact same thing I just decided not to buy.

Advertising for the sake of letting people know something exists is not particularly valuable to the end user, and most of the time they are not even able to predict correctly what people are interested in.

Has anyone actually bought something because of an advertisement?

There's the worse (and very common) case: you decide to buy it, and still see ads about that keyboard you just bought, in case, you know, you'd want another (and even if you did, isn't having it in front of you and liking it more efficient than an ad?).

I'm actually thinking of doing this starting this weekend (mostly for fun). Any tips you care to share?

1) Have fun 2) Start from obvious opportunities first, then move to less obvious 3) Commissions are the killer, minimize it at all costs.

IPFS, in particular, plan to have native browser support via a Javascript dependency. There was also PeerCDN (and bunch of similar clones), but they all don't tend to stick around for long or get widely used even though the setup is supposedly one line.

The problem with PeerCDN and other WebRTC based solutions is that they can't solve the DNS DDOS problem. Since the WebRTC API needs a server for the handshake to start communicating between 2 peers directly.

Eh, but the DNS server isn't necessarily the same as the bootstrapping server for the WebRTC API, and in most cases it generally would not be.