I will be verbose if there is an actual keyboard under my fingers but unless I’m extremely invested in the topic and not also doing something else at that time I keep messages from my phone terse.

Because it’s “easier” to support Windows from a business perspective and it’s easier on users to use Windows as most already do use it and thus need no additional training/decreases support tickets.

I’m a small business environment it’s much easier to manage with Linux but you still need an OK Linux admin on staff.

Once you start scaling up on paper Linux certainly works but there are a lot of factors that most people (such as yourself) don’t consider.

This is coming from a pure Linux admin working on a mixed Enterprise environment where 99% of the infra is windows

What’s bad about it? I’m a Linux admin by nature but an admin of all by profession and overall I have no real complaints about Teams. Has always worked just fine for me and to my knowledge everyone else.

I constantly hear this but I just want to be the counter argument here.

Self hosting email is not the impossible tasks that people make it out to be. It is on the more advanced side of things though if you are hosting your primary email that you rely on.

I’ve been hosting my own email forany years now and have had no issues whatsoever but I also have years of experience and know how email works better than many that have no interest in such.

I would NOT recommended starting your self hosting journey with email but I will never discourage people from doing it.

Take your time. Ask questions any time you don’t understand something. Be ready to learn a lot and design a solid plan for disaster recovery.

Let’s see the rule(s) then

Just configured your mail clients pop/IMAP server as your fetchmail target and SMTP as your hosted service.

Yes and what exactly is a radical feminist to you

In the scope of wireguard it’ll just be a matter of you building appropriate firewall rules.

Since you want their internet traffic to go through you then i assime you’re effectively pushing a 0.0.0.0/0 route to your clients. You then need to add firewall rules on your server to block traffic to its local subnet and in the future allow traffic to only your jellyfin server.

This is also pretty simple and nothing wrong with that setup.

You did not answer what VPN tech you are using.

Without that knowledge i would recommend setting up tailscale and having your users use that. If you want to be fully self hosted you can also run Headscale as the control plane instead of relying on Tailscales own service.

I recommend tailscale as it is very easy to grant a user privileges to ONLY use an endpoint as an exit node but also grant access to any other endpoints as needed (such as your future jellyfin server) via theor ACLs.

Best practices comes down to what you do or do not want the VPN clients to access. This mostly comes down to routing and firewall rules.

So, what should your users have access to?

Also what is the vpn?

I’m not entirely sure what the actual question is. Can you rephrase what exactly you are trying to accomplish?

Debian

Assuming the implementation is done in such a way that I am not indirectly owned by the manufacturer of the BCI and am capable of maintaining its software and firmware myself…yes yes absolutely yes stick that shit in my head.

But if it is not open source and I’m expected to be tied to some corporate entity just to utililze it, no, absolutely not.

Yeah thats mostly the one that keeps me going.

I mean I’m not sitting here defending soldered on ram but your unnecessary aggression and sarcasm in your previous responses overshadows the fact that while solder on ram sucks for the upgrade and repair market the underlying tech has very tangible improvements and now we can maintain that improvement and the upgrade and repair functions.

I agree, soldered ram is bad. But I disagree that LPDDR ram is fundamentally bad and this improvement allowing it to be modular while maintaining its improvements is a very good thing.

As far as your complaints of battery life on your thinpad goes, there is much more to battery life than the consumption of the memory but naturally every part plays a role and small improvements in multiple places result in a larger net improvement. I’m assuming you’re running linux which in my experience has always suffered from less than optimal power usage. I’m far from an expert in that particular area but its always been my understanding that it is largely caused by insufficient fireware support.

As a whole this looking at this article in a vacuum i only see good things. A major flaw with lpddr has been address and i will be able to expect these improvements in future systems.

So you believe that the performance improvement and power saving is not worth creating a new standard?

But the article explains that there is a technical reason.

Debian for all things.

Add a test folder, add some data, delete the test root folder and see if it deletes the data.

Error message? Nextcloud logs?

Can’t tell you whats happening without information about what’s happening other than “it doesn’t work”.