Derin

Yeah, really don’t get this one. As an example, I’ve been supporting the guy who writes most of the software I use via Github sponsors for a while, now. It’s nice to get access to additional support chat rooms and perks and stuff, but just the feeling alone is satisfying enough.

Feelsgoodman.jpg

I genuinely recommend those with gainful employment to consider supporting the people who make the software and media you like (E.g. Patreon).

Issue reports and the likes are nice, but they’re really not a substitute for cash (in my opinion).

Yep, check out yabai.

I’m annoyed to see you getting down voted - I had a similar issue years ago with my work MacBook (couldn’t run a custom WM because any modification to the Finder was blocked without putting the machine into “unsafe” mode).

I love OSS, but without a verifiable way to distribute it large swaths of the workforce won’t be able to use it.

F-Droid is great, but sadly it isn’t enough.

Yeah, I recently bought the GL-MT6000 and it’s been great.

Its latest commit is from 4 days ago, so it looks like work is still ongoing.

It’s odd, but not unheard of for open source applications to have large windows between releases. They just might not have a reason to bump major versions, at the moment.

If you want the commits since 2022, you can always install a dev build from github.

Ooh, I’ll tell them to try it out - looks cool, cheers!

Conduit sounds very exciting - but my synapse installation (and its concomitant database) is too old and big for me to make a switch to anything else just yet.

But I’m hoping Dendrite will one day allow me to migrate over - I don’t like how one of my most mission critical programs is a Python program running out of a packaged venv. 😅

This is the correct answer, IMO.

I loved using XMPP back in the day, but I struggled talking with people who weren’t on the same server as me because of spec and client variations.

While Synapse is a resource hog, it (and Element) - to a certain degree - does the job. Can’t wait until sync v3 lands in the main server.

The only issue I have is with one friend who insists on deploying his own version of Synapse, but can’t figure out coturn and - as a result - we can’t voice chat properly.

Goddammit. Two steps forward, one step backward. 😅

This section of the tutorial you followed shows how you enable registration.

This section shows how you add a user.

The official Prosody documentation for adding users and opening registration can be found here.

I use Fantastical; pretty decent for an iOS App - if not a bit pricey.

Edit: As an important note, while I’ve used Fantastical for years, it’s really only for the Mac ecosystem so I’m looking to move away from it.

Nowadays Morgen is my Calendar app of choice, but its iOS app isn’t feature complete yep. It’s fantastic on desktop, though.

There are some great ones. Check out Tempo and Symfonium

Well, at least you gave it your best!

Sorry man, I don’t know what to tell you. I’ve got a pretty medium end VPS on which I host my Matrix instance - only had to add an extension for storage after the first few years when the DB got too big. Things were never as bad as you said early on, and as time passed I absolutely got to the point where it would take 10-20 seconds to sync - but this was after 2 years or so of constant use.

The reason why it takes long is because of the size of the sync payload - logically, for a new server/user, this really shouldn’t be that big (unless you’re in rooms like Matrix HQ). So, genuinely, look into optimization: postgres, your web server (nginx, apache, caddy), and limiting your users from accessing “problematic” rooms.

Barring that just deploy the sliding sync proxy and be done with it. It’s not really a problem that requires you to attempt it a thousand times.

So either you put some fancy wizardry into your system or you’re just in denial.

It’s called pure Debian, baby. Also, you’ll need a decent chunk of RAM if you don’t have that yet. Avoid a pagefile if you can.

Might need to check your setup. But, I will concede that after 2 years in - a point at which the DB grew into something massive, what with the massive Matrix rooms I was idling in - I started to notice slowdowns. The whole sliding sync proxy thing (with the new generation Element X clients) fixed everything.

You shouldn’t be having 10-20 second syncs with a new deploy (and limiting the amount of massive rooms your users can join, depending on your hardware), might be something awry relating to your config. If you’re absolutely certain it’s not that, check out the sliding sync proxy until it gets merged into the main spec - it’s great.

Been using matrix as my primary communication method (including bridges to other networks for things like Slack and WhatsApp) for over 3 years now, doesn’t feel slow?

Try Baikal, it’s a pretty lightweight CalDAV server!

Any client I use it with supports notifications, however it should also be able to send emails for you (e.g. Its scheduling feature).

What does this have to do with self hosting?

As a person who oversaw the implementation of GDPR in a large software house (which wasn’t EU specific, but had to in order to operate legally in the EU), the requirements were:

1. Allow users to request data deletion or a copy of their data.
2. If the former, delete all data of their data on the server, send it to them, and then (this was the important part) forward the data deletion request to every single partner we were working with.

For us, this was multiple ad companies. We had to e-mail each one, ask them about their GDPR implementation (most of them were somewhere between “we’re thinking about it” and “we have an e-mail address you can send something automated to and we’ll get to it sometime within the next month”), and then build an automated back-end system to either query their APIs for automated deletion, or craft/send e-mails for the more primitive companies.

As far as the data being deleted, it was anonymized IDs that were tied to their advertising IDs from their mobile phones. I used to try and argue that “no, it’s anonymous” - but we also had some player data (these were games) associated with that, so we ended up just clearing house and deleting everything on request.

So, legally, this means every instance - in order to be GDPR compliant - would have to inform every instance it federates with that a user wants their data deleted. If you’re not doing that, you’re not fully compliant.

Kind of shitty, but that’s how it went for me. (this was back when GDPR was first being released)

Edit: Also, the one month thing was relevant: you have 30 days to delete GDPR stuff after receiving a data clear request. I don’t recall what the time was for a “see my data” request. Presumably, though, on Lemmy the latter is superfluous as all your data is already present on your profile page. An account export option would be enough to satisfy that.

Good luck!

Just so you know, running an email service isn’t as easy as you think. You’ll most likely deal with a lot of blocks from Gmail and the rest.