maybe showing him this would help?

just tell them "it's been a long time"

except: pass

thanks!

here is a side-by-side comparison of the neural network upscaling slop (left) versus a conventional zoom in on the original (right):

and then of course there is the text:

😦

nice work!

The server isn’t exposed to the internet. It’s a local IMAP server.

if it is processing emails that originate from the internet, it is exposed to the internet

security updates are for cowards, amirite? 😂

seriously though, Debian 7 stopped receiving security updates a couple of years prior to the last time you rebooted, and there have been a lot of exploitable vulnerabilities fixed between then and now. do your family a favor and replace that mailserver!

From the 2006 modification times, i wonder: did you actually start off with a 3.1 (sarge) install and upgrade it to 7 (wheezy) and then stopped upgrading at some point? if so, personally i would be tempted to try continuing to upgrade it all the way to bookworm, just to marvel at debian stable's stability.... but only after moving its services to a fresh system :)

i'm not aware of anybody who allows public signups and is interoperating with bsky.app yet (besides Bridgy Fed which will create an ATP identity for your ActivityPub identity), but I'm pretty sure it is possible because I follow people there who appear to be doing it for themselves.

see also my reply to you in another thread.

Very interesting, thanks! Is it possible for people to register on that relay?

(if I understand correctly) you don't register on a relay, you register on a PDS (which you can easily self-host on a small computer at home). But, to register with a PDS, you need a DID, and to interoperate with the rest of bluesky it needs to be using one of their two currently-supported DID methods: either did:web or did:plc. The former is a thing which you can create using a domain you control, which gives you an identity that you lose control of when you lose control of that domain. The latter is the actually-centralized "placeholder" DID method implemented by an append-only log operated by BlueSky PBC, which is what most people are actually using. I'm not sure if/how you can create a did:plc without first creating an account on a bsky.app PDS, but you can migrate it to your own PDS after creating one there. or, you can use did:web and rely on your domain name registration instead of their centralized log.

Further reading:

• How to self-host all of Bluesky except the AppView (for now) (from November last year)
• minimal AppView example
• "self-hosting entire bluesky" with docker-compose (including AppView, apparently)

as i wrote in another thread:

Content addressability is absolutely essential for building something that will last, and BlueSky gets that right. Decoupling the many responsibilities which an ActivityPub instance operator has (especially for identity) is also essential, i think, and while BlueSky’s identity solution is less than ideal it’s much better than ActivityPub and I expect it to improve.

If you’re interested in the topic you probably want to also read the followup post from the same author (after reading the reply linked there from someone on the BlueSky team).

Christine’s analysis is by far the best I’ve read on the topic, but I think she is too dismissive of the possibility that people will actually build things using ATP in a manner more like ActivityPub (where there doesn’t need to be a global view). It’s also possible/likely that ActivityPub will eventually evolve to adopt content addressability (Christine actually built a proof-of-concept of doing that years ago, linked in her blog post, but there doesn’t appear to be any recent progress in that direction), and decouple identity from responsibility for data availability, and adopt something like BlueSky’s composable moderation.

Given their respective advantages over the other, i’m pretty sure that both ATP and AP will make changes which make them more like the other in the coming years.