I pride myself in the fact that it’s easier to cancel a subscription on my email service than it is to subscribe. From the home page, it’s four clicks.

This is not possible. The other servers need to be able to communicate with yours, and for that, yours needs a domain name.

If you only care about local users following other local users, and only other local users, then this is possible. But if you add remote users into the mix, you need to federate, and to federate requires a domain name.

It’s pronounced like Liminiux. Lominoliux is also acceptable.

It takes the raw code, bakes it at 450°F for 90 minutes, then does some magic.

Line-yoox.

That’s correct, subaddressing is a ubiquitous feature. That’s not what I was talking about.

Port87 is built entirely around subaddressing. The “bare” address doesn’t even go through to you. It also labels email automatically based on the subaddress, and you can control setting per label, like mark-as-read and notifications. You can also have screening on any of your labels, so that only humans can email you there. Subaddressing is not an optional afterthought, it is required and how the system works.

Port87 does not have an inbox. (Which I found out while creating it is something that basically all open source email software expects to exist.) It has an “Aggbox”, which is not a real place, but a filter for which labels you want to see when you open the app.

Port87’s search box is, I would say, the most powerful email search feature of any email service. It’s nearly as powerful as a straight up SQL query.

So yeah, I would say it’s unique among email services.

Also, simple login and addy aren’t really email “providers”, they’re more accurately called forwarding services. Email provider, or officially “mail service provider”, is specifically the term for an email service that sends, receives, and stores email.

Right now, only downloading single emails. This is an area I’d really like to improve on though. The single best option, and what I’ll be working on as soon as I’m done with mailing lists, is supporting IMAP. That will let you import/export mail directly, and give support for a bunch of third party clients. Unfortunately, because Port87 is very different than other email services, I’m going to have to write my own IMAP server. I have the spec printed out in a binder in my office, so I’ll be getting started on it pretty soon. That’s a big big project though, so realistically, it’ll probably be over a year, maybe two, before Port87 supports it.

I mean, there’s not really a clear definition, but if your distro has an upstream distro and the only difference between yours and the upstream is that you added a few packages and some config files, I would call that a community flavor at best, not a distro.

Take Bazzite for example. They don’t have their own package manager (well, they kind of do, but it doesn’t use their own repos to my knowledge), but the installation is so vastly different from the upstream repo (Fedora) that calling them a distro makes sense.

Or take Ubuntu. It’s just Debian with some new packages, or? No, it’s so vastly different from a base Debian install, including their own repos and builds of every package, that it’s definitely a different distro.

Omarchy, by contrast, it’s basically a set of packages and config files that you install onto Arch. Not a distro.

Same with Proxmox VE, but they don’t try to call it a distro. They call it what it is, a “solution”. That’s not a bad thing. It’s bad to pretend it’s a distro, like Omarchy does.

Proxmox Virtual Environment is an open source server virtualization management solution based on QEMU/KVM and LXC.

- Proxmox’ Wiki

Omarchy is a beautiful, fun & agentic Linux distribution by DHH.

- Omarchy’s GitHub.

Version 2 explicitly declares that dependencies are not considered:

This does not include source codes and object codes of dependencies that are merely linked to, not stored, within the project, and any portions of object code resulting from the compilation of the imported source codes of linked dependencies when compiled during the normal build process of the project.

Version 1 basically could be interpreted this way, but it wasn’t explicitly stated.

If it’s a fork, and you want to accept upstream patches that have AI code into the codebase, then you can use the the upstream excepted version:

https://sciactive.com/human-contribution-policy/version-2-up/

As long as you clearly identify the upstream project as an upstream project.

Disgusting. Ban all clanker code.

All my projects use this:

https://sciactive.com/human-contribution-policy/

🤢🤮

I remember when HEY first came out, I got to try it and thought it was kinda useless. Defining an entire email service by the removal of one step from any other email service seems silly. (Coming from a guy who’s actually written a unique email service.)

It’s a new distro in the same way that Minecraft with a texture pack installed is a completely different game.

Fedora is a great choice.

I was afraid when I saw this

that it was just slopware, but it seems like it only has a few commits by Claude. And the commits aren’t just a firehose, like slopware tends to be.

I use Nextcloud Deck. It’s amazing.

For eink, the XTEink devices work offline. If you put https://crosspointreader.com/ on them, then it’s not even XTEink’s software running on it.

It’s because they changed the deal! The deal I had to write code, and now the deal is that I have to write code and not not write code! That’s crazy!

- The maintainer, probably

I agree. I guess it wasn’t obvious that I was being sarcastic.

This wholly depends on where this code is running. If it’s running on the server, you want the best algorithm for most cases, to try to minimize work and power consumption, and maximize capacity. If it’s running on the client, just use whatever.