HNHacker News
TopNewBestAskShowJobs

MattJ100

2,079 karma · joined December 30, 2008

Open-source developer and proponent of decentralized communication platforms.

Currently building Snikket <https://snikket.org/> - a self-hosted alternative to proprietary messaging apps.

Email/XMPP: 'me' (...at...) 'matthewwild.co.uk'

submissionscomments
MattJ100··on Upcoming changes to Let's Encrypt and how they affect XMPP server operators
Sorry, it's late here and I guess I didn't word it well. Dialback (these days) always runs over a TLS-encrypted connection, as all servers enforce TLS.

The next question is how to authenticate the peer, and that can be done a few ways, usually either via the certificate PKI, via dialback, or something else (e.g. DNSSEC/DANE).

My comment about "combining dialback with TLS" was to say that we can use information from the TLS channel to help make the dialback authentication more secure (by adding extra constraints to the basic "present this magic string" that raw dialback authentication is based on).

MattJ100··on Upcoming changes to Let's Encrypt and how they affect XMPP server operators
> Is there a reason why dialback isn't the answer?

There are some advantages to using TLS for authentication as well as encryption, which is already a standard across the internet.

For example, unlike an XMPP server, CAs typically perform checks from multiple vantage points ( https://letsencrypt.org/2020/02/19/multi-perspective-validat... ). There is also a lot of tooling around TLS, ACME, CT logs, and such, which we stand to gain from.

In comparison, dialback is a 20-year-old homegrown auth mechanism, which is more vulnerable to MITM.

Nevertheless, there are some experiments to combine dialback with TLS. For example, checking that you get the same cert (or at least public key) when connecting back. But this is not really standardized, and can pose problems for multi-server deployments.

> It has never been secure to accept the clientAuth EKU when using the Mozilla root store.

Good job we haven't been doing this for a very long time by now :)

MattJ100··on Upcoming changes to Let's Encrypt and how they affect XMPP server operators
There might be some confusion here, as there is no refusal at all.

As stated in the blog post, we (Prosody) have been accepting (only) serverAuth certificates for a long time. However this is technically in violation of the relevant RFCs, and not the default behaviour of TLS libraries, so it's far from natural for software to be implementing this.

There was only one implementation discovered so far which was not accepting certificates unless they included the clientAuth purpose, and that was already updated 6+ months ago.

This blog post is intended to alert our users, and the broader XMPP community, about the issue that many were unaware of, and particularly to nudge server operators to upgrade their software if necessary, to avoid any federation issues on the network.

MattJ100··on Upcoming changes to Let's Encrypt and how they affect XMPP server operators
Thanks! I didn't intentionally write this for a broader audience (I didn't expect to see it while casually opening HN!). Our user base is quite diverse, so I try to find the balance between being too technical and over-explanatory. Glad it was helpful!
MattJ100··on Anthropic: You can't change your Claude account email address
What logical fallacy, exactly? I think you're perhaps misunderstanding the conversation. This translates just fine to your proposed analogy.

In your analogy, the claim would be that some online account is tied to a laptop and whoever possesses the laptop has access to that account. The online service does not permit the account owner to revoke access from that laptop and move the account to a different laptop. I stand by my statement that this would be a serious security hazard. Because yes, laptops can and do get hacked or stolen, just like email addresses.

Where your analogy isn't quite as strong is that at least you can generally add additional anti-theft protections such as full-disk encryption to a laptop, while with an email account generally 2FA is the best you can do.

MattJ100··on Anthropic: You can't change your Claude account email address
You're very wrong, because account takeover can still happen due to a compromised email account. People can and do permanently lose access to their email account to a third party.
MattJ100··on Self-hosting a Matrix server for 5 years
Prosody dev here. Good to know this is useful :)

One of my favourite small features we added in the latest release is a 'prosodyctl check features' command which will validate that your configuration is up to date with current best practices in various ways.

Although we like to curate the default configuration with care, people tend to keep their existing configuration file when they upgrade (we generally recommend this, as we aim for backwards compatibility). The new command makes it easier for folk who upgrade to ensure they are still getting the expected experience as the recommendations evolve.

Obviously that has to be somewhat opinionated. One thing many people appreciate about Prosody is that you can customize it however you want to, even if it's not following the mainstream. E.g. if you really don't care about synchronizing to multiple devices, you can totally disable that message cache. Don't need audio/video calls? Fine!

MattJ100··on The risk of round numbers and sharp thresholds in clinical practice
Depends what you call "high", but the risks are far higher than most other drugs relative to availability.

"Paracetamol toxicity is one of the most common causes of poisoning worldwide." -- https://en.wikipedia.org/wiki/Paracetamol_poisoning#Epidemio...

MattJ100··on Using FreeBSD to make self-hosting fun again
I'm curious which aspect(s) became a time sink for you? I self-host a bunch of stuff myself. I can't say I never spend time on it, but it's measured in hours per year. Once stuff is set up, it just runs.
MattJ100··on Wren: A classy little scripting language
That's unusual that you struggled to build Lua. Lua is primarily C89, and used on non-POSIX microcontrollers for example. There are some optional bits of the standard library you would have to leave out - module loading uses dlopen(). This is done simply by defining the right feature macros for your target environment: https://www.lua.org/source/5.4/luaconf.h.html

You may also be interested in this project: https://github.com/fengari-lua/fengari

MattJ100··on Modern messaging: Running your own XMPP server
Yeah. I'd be surprised if Apple didn't use similar logic. XMPP can do multiple ports (a deployment can specify the recommended order in DNS). I've not heard of an all-ports deployment, but it does sound like an interesting experiment :)
MattJ100··on Modern messaging: Running your own XMPP server
I see these comments a lot from people who have very old deployments and didn't keep up with changing best practices. The users of these deployments also tend to be using out-of-date software such as Pidgin to access their account.

There is zero reason for long delays or lost messages in XMPP.

MattJ100··on Modern messaging: Running your own XMPP server
As an open-source XMPP project, we tried hard to find iOS developers willing to help with development (as volunteers, or even paid) and it's just so hard to find people in this intersection of interests.

If anyone reading this thread has iOS dev skills and cares about improving open-source messaging on iOS, feel free to get in touch.

MattJ100··on Modern messaging: Running your own XMPP server
Here are the official docs for deploying ejabberd using containers: https://docs.ejabberd.im/CONTAINER/
MattJ100··on Modern messaging: Running your own XMPP server
The default ports are often blocked on such networks (public wifi, corporate firewalls, etc.), but also often open. 5222 is used by e.g. WhatsApp, 5223 is used by e.g. Apple push notifications. So it's not as bad as it could be.

But it's also totally possible to run XMPP over 443, and this is a feature of many popular XMPP deployments. If you're self-hosting, there are some guides for different deployment approaches here: https://wiki.xmpp.org/web/Tech_pages/XEP-0368

MattJ100··on Modern messaging: Running your own XMPP server
ejabberd should work fine, it won't care. But you're right - whether apps will allow you to accept self-signed certificates can vary. Some are strict and don't allow bypass, others may just issue a warning prompt that you can dismiss. I haven't personally tried aTalk.
MattJ100··on Modern messaging: Running your own XMPP server
Or push notification support (which is the same, but basically the OS (Android/iOS) is the thing holding an open connection :) )
MattJ100··on Modern messaging: Running your own XMPP server
Thanks, I've forwarded it to their chat channel.
MattJ100··on Thoughts on Cloudflare
It's the ASCII encoding of a Unicode domain name: https://en.m.wikipedia.org/wiki/Internationalized_domain_nam...
MattJ100··on PYREX vs. pyrex: What's the difference?
I'm curious about the method you used to measure this accurately at home.
MattJ100··on The value of bringing a telephoto lens
Worked for me in Firefox Android (the race condition theory seems likely).
MattJ100··on The value of bringing a telephoto lens
Interestingly, it was what pushed me back into it. Even just capturing family stuff, the limitations of smartphone cameras were always niggling, the article gives one example of why, but focal length is just one of the things you gain more control over with a real camera.

I realised a big reason I defaulted to my phone was simply that it's always there in my pocket, while my "real" camera was a burden to carry around. Related to the popular photography maxim that "the best camera is the one you have with you".

One day, after "seeing" some good shots in my head and totally missing them due to phone camera limitations, I decided I had to fix it. I started with an RX100 (I got the M3 secondhand at a decent price), which is as pocketable as a phone and immediately improved things for me.

Eventully that reminded me how much I enjoyed real photography, and now I often cart a big camera and multiple lenses around with me again. Oh well :)

MattJ100··on De-Clouding: Music
Spotify has an option to show songs in your playlists which have been removed. In the mobile app, Settings->Content and Display->Show unplayable songs.

Hope this helps!

MattJ100··on A month using XMPP (using Snikket) for every call and chat (2023)
You're not wrong at all, but despite it all, XMPP has actually supported push notifications for years.

For various reasons it wasn't included "out of the box" in Prosody for a while and was maintained as a community plugin, but that's no longer the case with 13.0.x+ where it's bundled with Prosody and just works.

Monal is probably the most popular XMPP iOS app today.

MattJ100··on When photography was born, fascination, obsession, and danger followed
> photography enabled integrity and authenticity of images, which fueled journalistic credibility

Countercounterpoint: https://en.m.wikipedia.org/wiki/Cottingley_Fairies

MattJ100··on I watched Gemini CLI hallucinate and delete my files
Git allows deleting commits, and the whole .git directory can be deleted. I'm sure there are enough instances of git frustration out there on the web (the training data) of people doing exactly that to recover from problems with their git repo that they don't understand, even if it's not the right way to fix things.
MattJ100··on I built something that changed my friend group's social fabric
I work on a project in this space, and the endless insistence of people that they have to run clearly non-web things through reverse proxies always amazes me :)

Not everything is a web app, and it's trivial these days to obtain certificates, even without a proxy (certbot, etc.).

Of course I understand that if you host a lot of web apps, having all web requests routed through a universal proxy is nice for various reasons. But platforms like Discord and such are complex beasts and use more technologies than HTTP(S).

MattJ100··on Show HN: Attune - Build and publish APT repositories in seconds
As a FOSS project which publishes debs, it's a real hassle using current tooling. The tools are heavily biased towards the needs of distro maintainers, forcing projects into overly complex workflows which are overkill for a small numbers of packages. Features that would benefit smaller repositories with more frequent updates are limited or missing.

The other options is to DIY without tooling (essentially, write custom tooling as scripts or whatever), which is messy and full of pitfalls to the inexperienced.

MattJ100··on The Bitter Prediction
I agree, but only for situations where the probabilistic nature is acceptable. It would be the same if you had a large team of humans doing the same work. Inevitably misclassifications would occur on an ongoing basis.

Compare this to the situation where you have a team develop schemas for your datasets which can be tested and verified, and fixed in the event of errors. You can't really "fix" an LLM or human agent in that way.

So I feel like traditionally computing excelled at many tasks that humans couldn't do - computers are crazy fast and don't make mistakes, as a rule. LLMs remove this speed and accuracy, becoming something more like scalable humans (their "intelligence" is debateable, but possibly a moving target - I've yet to see an LLM that I would trust more than a very junior developer). LLMs (and ML generally) will always have higher error margins, it's how they can do what they do.

MattJ100··on Alexa+
I don't think you can say that is the problem. It may have exacerbated the issue, but problems exist when summarising full news content too: https://www.bbc.co.uk/news/articles/c0m17d8827ko
← PreviousPage 2 of 17Next →