Usually you just see LibreOffice and nothing else, so it’s fine, I guess. Not a web-based editor, but usable.
Somewhere between Linux woes, gaming, open source, 3D printing, recreational coding, and occasional ranting.
🇬🇧 / 🇩🇪
Usually you just see LibreOffice and nothing else, so it’s fine, I guess. Not a web-based editor, but usable.
Ah, I see. Not as native web application, though.
They’re using Alpine Linux, install X and Openbox and Xvnc and serve KasmVNC via Nginx and connect via KasmVNC to that X instance. LibreOffice is started in fullscreen and looks like a slightly blurry web application.
But in reality it is just a regular desktop installation with some extra things.
@fikran@lemm.ee, maybe this is a solution? I wouldn’t recommend it because it’s not really a web-based document editor.
So, LibreOffice can be used over the Internet in a web browser?
Ca. 20 years ago I worked for a company that used X forwarding for their backup management system (a Java application running on one of the servers) which somewhat worked on their wired LAN (at least most some of the time).
This was just unreliable and slow and had issues left and right.
Back than I tried this. The performance was horrible, even on a good connection. It was barely tolerable on LAN, but over the Internet … no. Just no. There were and are better solution for accessing a remote machine.
That sounds great!
Mmh, okay. Is it fully featured? If so, then this instead of PuTTY (just to reduce the amount of extra tools needed).
If you use it as Server it likely won’t have a graphics server installed, so why not simply use SSH?
A common tool for using SSH on Windows is PuTTY.
Ubuntu uses Snap as first-class method to install software. So if a piece of software is available as DEB or Snap, Ubuntu will always use Snap.
I can’t wait for Brodie to report on this!
Exactly. With directly using certbot handling all and everything fully automatically I ran my old setup with a free dyndns subdomain for quite some time without any issues.
Since Let’s encrypt nowadays is basically implemented in every reverse proxy: certificates are an absolute no-brainer.
If someone manages to buy and configure a domain to serve selfhosted content, this person will also be able to either set up certbot or use the built-in functionality of their reverse proxy.
It’s 2025. Not having “real certificates” is something admins intentionally do. Since there is Let’s Encrypt available, all other solutions for non-paid certificates are obsolete.
Keep them memorized. The old tools just work, even if MICROS~1 tries to hide them and replace them with useless crap apps.
There – of course – won’t be a singular official source stating “Hey guys, we’re open core now”. You need to put this together bit-by-bit.
Here are some links for research
It falls under self hosted, at least. If it is still truly open source is highly debatable.
Never heard of 99% in that list.
Also, Gitea should not be there. It is a corporate -owned open core project that was hostilely taken away from the community.
That would be a wild experiment.
Dillo is 25 years old
Yeah, I can tell from the look and features. *scnr*
What’s the use case for that browser? Daily-driving it to browser the web likely not, right?
Exactly. Your KVM switch need to support it, or your clients will always act like you unplugged the screen when you switch between them.
So we’ll see a release in November this year?