#openSUSE isn't just for #servers & #devs; it's for #gamers too! Install. #Play. Repeat. #openSUSE makes gaming easy. #GameOnLinux #UpgradetoFreedom https://get.opensuse.org/

From powerful #servers to creative #desktops, #openSUSE scales with you.
Built by the community.
Updated with purpose.
Powered by freedom.
Try it: https://get.opensuse.org
#Linux #opensource

VSCode's SSH agent is bananas
https://fly.io/blog/vscode-ssh-wtf/
#ycombinator #fly #fly_io #elixir #docker #cdn #hosting #servers #networking #deploy_app_servers #close_to_users #postgresql_clusters #heroku_competitor #heroku_alternative

Auto Encrypt version 4.1.0 released

• Removes OCSP stapling, as Let’s Encrypt is removing OCSP support.

If you’re already using Auto Encrypt upgrade before May or your certificate renewals will start to fail. Upgrade now if you want to get certificates for new domains as new certificate requests are already failing.

https://codeberg.org/small-tech/auto-encrypt#readme

Auto Encrypt automatically provisions and renews Let’s Encrypt TLS certificates on Node.js https servers (including Kitten¹, Polka, Express.js, etc.)

Regular Node.js HTTPS server (without Let’s Encrypt certificates):

```js
import https from 'node:https'
const server = https.createServer(…)
```

Auto Encrypt https server with automatic Let’s Encrypt certificates:

```js
import AutoEncrypt from '@small-tech/auto-encrypt'
const server = AutoEncrypt.https.createServer(…)
```

(Certificates are provisioned on first hit and automatically renewed 30 days before expiry.)

¹ https://kitten.small-web.org

I have a problem that is caused by one of two issues..

1. Storage costs are high
2. My need to have tons of data is high

Which one should I be more annoyed at?

Hi and welcome to the #Fediverse to all #newcomers!

I am Tommi [tommi.space], the administrator of Pan [pan.rent], a tiny, cozy, friendly, #antiFascist, #transFeminist, and #antiCapitalist instance.

As you are wandering around this whimsical space, I know it might be a bit confusing and hard to figure it out.

Just give yourselves time! This place does not follow the algorithmic rules of mainstream, billionaire-owned, centralized social networks.

Actually, the Fediverse has no rules at all! Every community chooses their own principles and governance. If there is anything you are not comfortable with, you are completely free to move anywhere you want, without losing the people you are in touch with.

If you believe you share the vibe and the values of #Pan (this instance), we would be super happy to welcome you! Just get in touch with me however you want. It is of paramount importance that we all spread around, populating smaller servers, rather than flooding big ones.

Have fun and be excellent to each other!

#FreeOurFeeds steps for an enshittification-proof digital future:

"First, Free Our Feeds wants to create a nonprofit foundation to govern and protect the #ATProtocol, outside of #Bluesky the company.

We also need to build redundant #servers so all users can leave with their data or build anything they want—regardless of policies set by Bluesky.

Finally, we need to spur the development of a whole #ecosystem built on this tech with seed money and expertise."

https://www.technologyreview.com/2025/01/17/1110063/we-need-to-protect-the-protocol-that-runs-bluesky/

Qualcomm is hiring a data center chip architect for Snapdragon-based reference server designs - Qualcomm is looking for a server SoC security architect, ac... - https://www.tomshardware.com/desktops/servers/qualcomm-is-hiring-a-data-center-chip-architect-for-snapdragon-based-reference-designs #desktops #servers

Just spent 6 hours trying find out and solve why my Matrix instance is showing: {"errcode":"M_NOT_FOUND","error":"Not found"} when trying to access images. I did not notice this problem before, because Matrix/Element caches images locally using blobs, but realized this after uploading images to IRC via heisenbridge.

I first thought I had messed up my S3 Object Storage. Then thought I messed up my filesystem. Then I thought I made a mistake in yaml configs. But it was none of that.

It's a while since I installed my Matrix server and completely forgot on how I set up my S3 Object Storage. It seems it is literally not documented. Like at all. Just like the half of Matrix and Synapse.

I ended up debugging literally anything and everything without any solution. After turning all stones I even asked ChatGPT and it started to run in loops in despair. Finally ended up reading synapse changelog here one bit by bit: https://element-hq.github.io/synapse/latest/upgrade.html#authenticated-media-is-now-enforced-by-default

It seems, I have upgraded in some point. And wow, in between of upgrades the whole thing has broken. I mean it runs without erros, but it's broken. No deprecated warnings in the log, no warnings in release logs. Left a comment here: https://github.com/element-hq/synapse/pull/17889#issuecomment-2564520513

My solution was to add in homeserver.yaml:
enable_authenticated_media: false

What I hate about Matrix is:

- Nothing is documented
- Nothing is explained
- Everything is complicated to set up

Each upgrade and extension is like building and tinkering for hours and hours and hoping for the best.

I don't know why I keep using Matrix. Guess I like being hurt all the time.