haarts

There's little spam at the moment. There will be. But at that time the relays (pieces of server software that relay nostr messages) can step in and implement spam control via whatever they see fit. Perhaps some smart filtering, perhaps pay a few sats to have a message relayed or perhaps some real name policy. Clients can pick a (set of) relay(s) which fit their preference best. Or not, and accept the default.

The protocol is surprisingly simple to read [1], many relays and clients exist already.

I exchanged messages with a friend of mine who was using a very different client and it just worked!

Personally I like the fact that you can 'like' posts by sending a couple of sats via Lightning. I think it is a great motivator to write thoughtful, quality content.

Currently nostr is radical, weird and unpolished. The Amethyst client is slow at times. But the pace of development is incredible.

[1] https://github.com/nostr-protocol/nips/blob/master/01.md

I didn't even know Postgres had a queue last year. I used it just for fun and it is GREAT. People using Kafka are kidding themselves.

I've been reading a bit but it seems you can't add containers after you have booted the Flatcar distro. So define it on first boot or reinstall?

I don't think this is such a big deal. Yeah, you'd spent a couple of days cursing at your fingers. The bindings are an improvement and they require an investment, like all things worthwhile in life.

Where are you banking?!?

I'd be interested to learn a bit more about this. What are you referring to?

Is there something like hackaday.com for this kind of stuff?

From the article I understand that airship can only fly so high (I think because of the density of the air decreasing when you go higher). A jet stream (10km+) is far too high for an airship to reach (1.5km).

Enjoy the view obviously. Cruise!

I have one. Beautiful. But bought a GPU that doesn't fit because the cabling of the GPU is just a bit too much. Stick with the GPUs Thor recommends.

I take heart when reading about recovered parts of expensive ashes.

But I firmly believe that no project is wasted especially one that pushed the boundaries of what is commonly done. All the people working there learnt something. They might apply their new found knowledge to other fields or future carriers. The money invested is not lost but converted into bigger brains.

I look at VC money in much the same way. It's not great when a startup fails. But a lot is learnt.

I was not familiar with it. Thank you.

But it is. Your negatively charged comment just proved that.

I've switch from years of Vim to years of Kakoune and am now trying Helix. While annoying I find I pick up the right keys fairly quick. A week until I get decent productivity back and a couple of months tops to truly get the hang of it.

I find it immensely helpful that Kakoune and Helix _make sense_. It is also a great boon that there's visual feedback.

This sounds more plausible than all other explanations I've read.

This is a work in progress. Version 1.4 included minimal support for WASM (we are currently at version 1.5): https://crystal-lang.org/2022/04/06/1.4.0-released.html.

I expect full WASM support in the near future.

> You. Are. Not. Google/Facebook/Netflix/TikTok.

That cannot be repeated enough. 90% of the tech flaunted here on HN is interesting only on a technical level, never in a business setting.

I suspect Google released Kubernetes to hamstring all competition. You do not need it. Unless you're Google.

Is there something like Freestyler for Linux?

How does it work?

There's a lot of confusion regarding this.

TLDR: This actually involves two pieces of legislation: - Travel Rule - unhosted wallet verification

Both are Anti Money Laundering (AML) laws and not Know Your Customer (KYC) laws. On any exchange you have to tell the exchange who you are.

The first is global FATF[1] wrote a 'recommendation' and all jurisdiction on the world are expected to implement it. It mandates the exchange of originator/beneficiary data. When you do a regular/fiat bank transfer you also need to fill out the name of the beneficiary. This legislation brings that to crypto.

The second much less global. The Netherlands wants it, but the EU and UK (to a degree) will follow suite. The reasoning behind this law is that IF you DO NOT provider beneficiary data THEN you must be transferring to an unhosted/private wallet. You need to prove that you do.

Coinbase is merely a trailblazer here. Every single exchange will do this in the near future (within 2 years).

Elaboration:

This move has been a long time coming. FATF published their recommendation in 2019 and ever since the industry has been working to come of with a solution. There are MANY different approaches: TRP[2], TRISA[3], TRUST[4], Netki[5], VerifyVASP[6], Shyft[7], Sygna[8]. Some are purely a protocol, others are purely a SaaS offering and anything in between.

The main trouble with these laws is that exchanges need to exchange data. That means they need to talk to each other via mutually agreed upon standards. Added difficultly is that some exchanges are in a jurisdiction that requires this, while their counterparty is in a jurisdiction that doesn't require this. Solutions to this and more need to be devised.

Coinbase is heavily involved, and one of the initiators of TRUST. They are pushing this more than anyone else and see being compliant early as a competitive advantage. Binance, for example, got a reprimand of the Dutch National Bank. Making it harder for them to do business there.

While I'm not a fan of this regulation I believe this to be a crucial step into making Bitcoin (and others) mainstream. Without clear regulation institutionals won't enter. Retail will see this as a clear sign of endorsement from the government. The challenge is now to make the implementation of these new laws as sensible as possible, preserving privacy. Some initiatives I listed do that better than others.

The EU will have legislation in place in 24 months. The UK will start enforcing this in September 2023. Switzerland and Liechtenstein already enforce this since a couple of years. Singapore started to enforce this since not too long ago. As does South Korea. It is not clear to me when the US will actually start to enforce.

Disclaimer: I am one of the co-founders of 21 Analytics[9] and we are trying to make a living keeping the Travel Rule compliance space sane and clear.

[1]: https://en.wikipedia.org/wiki/Financial_Action_Task_Force [2]: https://www.travelruleprotocol.org/ [3]: https://trisa.io/ [4]: https://www.coinbase.com/travelrule [5]: https://www.netki.com/ [6]: https://verifyvasp.com/ [7]: https://www.veriscope.network/ [8]: https://www.sygna.io/ [9]: https://21analytics.ch/

I would very much like to read about that too.

Setting some sane security parameters for your SSH setup looks like a less jarring/drastic approach into securing SSH further[1]:

- Use keys.

- Allowing only strong cyphers.

- Remove weak primes.

[1]: https://disknotifier.com/blog/simple-ssh-security/

This project deserves more credit than it gets. It is vital to have a clear, unbiased view of our leaders, large and small. For investigative journalism but also for the curious citizen. Being sanctioned is no small matter and being able to find the source opens the door to recourse.

I'm happy to see that OpenSanctions choose to become sustainable by allowing companies to get a license to use their data.

I've been using it for the better part of three years after using Vim for many years.

What I like about it that it is intuitive. Selections make sense. The visual feedback is great too. I've configured nearly nothing, the out of the box experience is great.

I'm never switching back to Vim.

I couldn't agree more.

Recently I switched back to Rails after 10 years. I can't say I enjoy the whole asset pipeline business but I yearn for a simpler time and Rails gives that (to a degree).

My only wish it was simpler to host. I don't necessary want to buy into render.com or heroku.

That last sentence surprises me a bit. What does a 3.5 audio jack have to with any of this?

I use https://tailscale.com, Teleport looks similar? Or do you prefer one over the other?

I liked this article about it: https://smallstep.com/blog/use-ssh-certificates/

I don't think the defaults are bad. I think the defaults are generic. And I don't have a generic machine. Nobody has. Old SSH clients don't need access to my server. So I think it is a good idea to remove old cyphers.

Staying ahead of the pack.

I was long of that conviction too. But the default install optimizes for a different thing, compatibility. Or at least emphasizes is more than I would do.

For example I never use RSA keys. So these can go. Less cyphers => less attack surface.

But I do agree that I'm sure the defaults picked are sensible.

That's brilliant!