Oliver Lowe

Depends how you look at it! Here’s me accessing Mastodon and the fediverse via email: https://lemmy.world/post/11020167 I’ve written a a couple more prototypes to connect one to the other. If anyone is interested I could write up more about how it works or do a more public demo

I wonder whether they are aware of the ForgeFed project?

Thought that’s already supported? e.g. https://gitlab.com/diasporg/diaspora.atom

Oh wow thanks! :) One program syncs my home Mastodon timeline, with all replies, to a Maildir. Dovecot serves that over IMAP. Sending involves a custom SMTP server which reads the mail message and creates a post from it.

For Mastodon it was all about converting statuses (toots? Posts?) into RFC 5322 messages. Using the status’ ID as Message-Id in the message header is handy. Mail clients do the heavy lifting of rendering threads thankfully!

Ha good eyes! :) I have basic receive-only working with Lemmy using a virtual file system interface I wrote (https://pkg.go.dev/olowe.co/lemmy). Just realised we actually spoke about this a while ago haha (https://lemmy.sdf.org/post/1035382 )

But synchronising to disk is super inefficient: too many API calls. Should subscribe using ActivityPub proper and store updates received as RFC 5322 messages.

From there we could serve the messages via NNTP. Then, finally, we could use nntpfs(4)

Devil’s advocate: what about the posts and comments I’ve made via Lemmy? They could be presented as files (like email). I could read, write and remove them. I could edit my comments with Microsoft Word or ed. I could run some machine learning processing on all my comments in a Docker container using just a bind mount like you mentioned. I could back them up to Backblaze B2 or a USB drive with the same tools.

But I can’t. They’re in a PostgreSQL database (which I can’t query), accessible via a HTTP API. I’ve actually written a Lemmy API client, then used that to make a read-only file system interface to Lemmy (https://pkg.go.dev/olowe.co/lemmy). Using that file system I’ve written an app to access Lemmy from a weird text editing environment I use (developed at least 30 years before Lemmy was even written!): https://lemmy.sdf.org/post/1035382

More ideas if you’re interested at https://upspin.io

They even have a term for this — local-first software — and point to apps like Obsidian as proof that it can work.

This touches on something that I’ve been struggling to put into words. I feel like some of the ideas that led to the separation of files and applications to manipulate them have been forgotten.

There’s also a common misunderstanding that files only exist in blocks on physical devices. But files are more of an interface to data than an actual “thing”. I want to present my files - wherever they may be - to all sorts of different applications which let me interact with them in different ways.

Only some self-hosted software grants us this portability.

This was the provider I went with after self-hosting my mail for 7+ years on an OpenBSD VPS. I feel like Migadu is an honest and good-value service.

Each time your browser makes a request (such as updating the graphs), it’s submitting a new DNS query each time.

That would be surprising; most HTTP clients reuse network connections and connections are deliberately kept open to reduce the overhead of reopening a connection (including latency in doing a DNS lookup).

Then again, I’ve seen worse ;)

Slightly off-topic: I’m not too familiar with FreeBSD (I use OpenBSD), but others may be interested to know you may be able to configure wireguard interfaces without installing any packages. It probably just involves running some ifconfig commands at boot via some entries in /etc/rc.conf. See https://docs.freebsd.org/en/books/handbook/network/

Yeah I’ve always found that AllowedIPs name a little bit misleading. It is mentioned in the manpage:

A comma-separated list of IP (v4 or v6) addresses with CIDR masks from which incoming traffic for this peer is allowed and to which outgoing traffic for this peer is directed.

But I think it’s a little funny how setting AllowedIPs also configures how packets are routed. I dunno.

You could start troubleshooting by manually executing DNS queries from mainDesktop.lan, and watching the DNS server logs. Not sure what OS the desktop is running, but assuming Windows you could run:

nslookup -type=A pihole.example.duckdns.org.

On macOS/Linux/etc.:

dig -t A pihole.example.duckdns.org.

This could rule out behaviour from the proxy or applications.

Here’s a slightly different story: I run OpenBSD on 2 bare-metal machines in 2 different physical locations. I used k8s at work for a bit until I steered my career more towards programming. Having k8s knowledge handy doesn’t really help me so much now.

On OpenBSD there is no Kubernetes. Because I’ve got just two hosts, I’ve managed them with plain SSH and the default init system for 5+ years without any problems.

Great points. It’s the proprietary nature and lack of interoperability of “the cloud” that causes problems. My email is hosted on a remote server but I have control over my data. There’s no algorithm controlling what order I see my mail in or who I can forward stuff to. There are many different tools and clients available to me and to everyone else to work with their data.

Imagine if publishing a photo from my phone to Instagram meant copying a file from one folder to another. Or if I want to create an automatically translated voiceover from the captions of all my old Facebook photos in a video editor. Right now these operations require complex software. But the technology is all there and has been for a long time.

I often think about https://upspin.io

And sharing changes can be done with just email and regular git! https://git-send-email.io

Thanks! Is there something about the larger area space which means there are fewer hops?

Maybe a silly question: any ideas why there are shorter routes using IPv6?

Oh, I’m sorry that you found that :( Hopefully we can all help each other more :) If you have more time in the future I’m interested to hear how you go setting up Lemmy on Windows :)

Everyone else here is saying it’s not recommended. I’d agree with that. But I’m super curious to hear whether we can, not whether we should! So, OP: I say give it a go and report back what problems you run in to!

May be worth having a look at the ActivityPub protocol. It’s the way Lemmy instances (and other stuff!) communicate with one another. From there I think it will be clearer how a single Lenny instance could behave. https://activitypub.rocks