mrusme

Joined 10 years ago

Karma

Submissions

Member since

Jan 6

$argon2id$v=19$m=8192,t=2,p=4$HdG89kfmqyoMWPovDbWOCg$YhQkaU/ogpN0dkkSbCZ8A7qH0bjLMpC9

View on Hacker News

Recent submissions

Comment · 1 year ago

How?

Comment · 1 year ago

I'm a fan and active user of XMPP. However, it unfortunately is true that encryption is a can of worms. OMEMO should be the standard, yet there is fragmentation in terms of the specific OMEMO spec version that clients use. Not even the most prominent clients keep up with the latest spec, as can be seen here [1]. One of the issues is, that everything prior to 0.4.0 uses AES-128-GCM, instead of the standard that is used by other platforms (eg Signal), that is AES-256-CBC with HMAC-SHA-256. In plain English this means that most mainstream XMPP clients do not offer encryption at a level that can and should be expected these days.

[1]: https://xmpp.org/extensions/#xep-0384-implementations

Comment · 1 year ago

It just so happens that France is the country producing over 50% of the EU's cheap nuclear electricity.

Comment · 1 year ago

Some might not know this, hence I'm pointing it out: There's an ENV variable that you can set in your dotfiles [1] to make the Go tooling skip any proxy and instead access the the module's repository directly:

export GOPROXY="direct"

I've had this in my ENV for a long time, primarily because I don't agree with how the Go proxy operates. For teams/organizations, as well as CI environments it also makes sense to set up an own proxy [2] and use this variable to let the toolchain use that instead.

While this wouldn't have completely prevented this incident from having an effect, I would argue that it would have at least minimized the impact.

[1]: https://github.com/mrusme/dotfiles/blob/772f09615cdcac94fec9... [2]: https://github.com/goproxy/goproxy

Comment · 1 year ago

You have built a beautiful TUI, hats off. Having that said, however, if feels like a missed opportunity for this project to use an SQLAlchemy-based database backend over the more simplistic and widely supported ledger [1] format. While I understand that the your tool might not want to leverage the full complexity of a double-entry accounting system, as a friend of plain text accounting [2] I would have preferred a format that I can alter with existing tools, in order to be able to integrate _Bagels_ into an existing workflow.

Nevertheless, the TUI looks very clean and shows nicely how powerful the Textual application framework is.

[1] https://ledger-cli.org [2] https://plaintextaccounting.org

Comment · 2 years ago

Thank you!

Comment · 2 years ago

I once built a firmware for the Pimoroni Keybow with it: https://xn--gckvb8fzb.com/projects/kiwi/

Comment · 2 years ago

Unless you want to impose blurry fonts onto your visitors, this font won't be it unfortunately. The required increments of 11px to display a crisp font with DepartureMono makes your content either too small (11px) for most people to read, or too large (22px) to look good.

I am always saddened by landing pages like this, because they communicate an idea that only works in very specific cases. Are you looking to use this font for a similarly polished, "Apple"-style landing page that is form-over-function? Then this font clearly is for you. But on 99% of pages that have actual content on them this font likely won't work, as much as I, too, would like for it to.

Comment · 2 years ago

Maybe the content of what their official agreement provided differed to what the tip-off was offering.