I have a mobile 4g router from them and it supports physical esim. I even managed to get their suggested card for cheap. They have some support in their firmware to set it up, so you can do that fully on the router.
oh, I didn't noticed that at first, but you are right.
What I did noticed is so many fast videos right next to text. I didn't even bother to read it (without firefox read mode) because it makes me a bit dizzy.
I use it since the fork and love their energy and tempo. It's amazing when you take into account it's history, that it was closed source at some point (maps.me), opensourced, forked...
It's not always better. Docker on lxc has a lot of advantages. I would rather use plain lxc on production systems, but I've been homelabbing on lxc+docker for years.
It's blazing fast and I cut down around 60% of my RAM consumption. It's easy to manage, boots instantly, allows for more elastic separation while still using docker and/or k8s. I love that it allows me to keep using Proxmox Backup Server.
I'm postponing homelab upgrade for a few years thanks to that.
I struggle to find out who is this aimed at, really.
It's clear there is a lot of drama in Opensource projects lately, but there are countless projects where the maintainer would be thrilled to have one or two people that would actually want to invest their time into reviewing some code with him. Day they find others pumped by their work and willing to invest some time would be celebrated with cake each year.
Just because someone else's broken CI pipeline does "Several thousands of downloads of NPM package per day" should not make you feel bad that you have not "Build an organisation which won't crumble" yet.
That's backwards. You want to help those people? Create that organization. Create another Apache org and take over important projects that need that.
It really feels like banging the wrong drum. Just another person having a broken curl setup and blaming Daniel Stenberg for it.
Serious people like to look at things through a magnifying glass. Which makes them miss a lot.
I've seen printed books checked by paid professionals that consisted a "replace all" populated without context. Creating a grammar error on every single page. Or ones where everyone just forgot to add page numbers. Or a large cook book where index and page numbers didn't mach, making it almost impossible to navigate.
I'm talking of pre-AI work, with publisher. Apparently it wasn't obvious for them.
It appears to me that the rationale was clearly stated in GP:
> resulting in missing upstream features and decreased security
I.e. it's a matter of technical superiority, which, to me, how the decisions should be made. Not by having friends in the community and all of us being Europeans and so on. (But, of course, I would be glad to hear more particular details/examples of Forgejo lagging behind.)
You should simply compare release notes over the same time period for both projects, what's been done and how much. There's lots of nonsense repeated on this site and others, just do the research yourself, it won't take long. They both have very predictable release schedules.
We've stuck with Gitea, after not being impressed by the extremely FUDish behavior of the main driver of the fork, and this has proven to be the right choice so far. In spite of what some people claim, all of the major contributors to Gitea have continued developing it, none of the "heavy hitters" have left. It shows.
The database can be downgraded anyway. I've been doing backwards migrations for each new version all the way back to 1.22 (which is the last Gitea version that is "side-gradable" to Forgejo).
i dont get this blindspot by lots of developers parroting this uber technocratic nonsense.
There's no such thing as some apolitical, objectively best approach to a technical problem. Instead of arguing about specific merits about specific issues people throw out this big wide handwave about how "idea X is simply technically the wrong choice", as if this is a legit position to have.
Take a philosophy course for god's sake before you engineer us all to death.
Transition to Wayland opened so many user experience regressions. Many are solved today, or at least partially solved but...
There is still no possibility to have proper remote sessions when using Wayland. On any Window Manager and any distro. It's such a shitshow when you go into details. Nothing works, including third party tools (like NoMachine) and I could find no real hope for actual solutions being designed.
The best you can go with "remote session" on Wayland is viewing a desktop session that was already opened by someone directly on the computer. You can partially work around this by... setting your account to be automatically logged in with no password :D And even then it's a crippled experience.
A basic feature I used for the past 25 years and helped me to learn linux and offer safe space for others to learn it as well. To work around work computer limitations. To use your best hardware wherever and whenever you want.
I currently had to ditch both my favorite distro and WM because of that. But at least we can make screenshots nowadays, so I guess it could be worse.
The "Transition to Wayland" from a user experience pov is the slowest car crash of all time. We are like 1.5 DECADES in at this point.
I have a simple application written in QT6. It works on Windows, macOS, and X11/Linux. On Wayland/Linux, applications cannot move their own windows anymore, because "security". Good luck finding this in the QT documentation, it is there, but only at 3/dozens of places were it would be necessary, and 2/3 of those dont mention the word "Wayland". Great fun.
Kde's new Plasma Login Manager / Plasma Login (backend/frontend) have been coming along nicely (replacing sddm), and include remote login support. Just announced this past spring but very active. https://blog.davidedmundson.co.uk/blog/a-roadmap-for-a-moder...
That's exactly what I was talking about before. Tried on newest fedora but that simply isn't it. It's remote support to an existing session. Names are misleading.
> There is still no possibility to have proper remote sessions when using Wayland. On any Window Manager and any distro. It's such a shitshow when you go into details. Nothing works, including third party tools (like NoMachine) and I could find no real hope for actual solutions being designed.
Gnome has had remote desktop sharing I think since 46.
Settings --> System --> Remote Desktop
The "desktop sharing" tab is for setting credentials to share your logged in screen.
The "Remote Login" tab is for setting credentials to access GDM and login as any user (i.e. headless).
Remote assistance, NOT remote logins. It can be used as support when someone is already went to that computer, authenticated and has a full gnome session opened.
So you literally CANNOT log in remotely :) If you are lucky, you can assist remotely to a session someone opened locally on that machine.
And it's like that on any other WM. KDE also has a deceiving option in settings that suggests full remote desktop, while it doesn't allow that.
I don't want to argue on semantics. Currently you can't start a graphical session completely remotely using any protocol (RDP, VNC, no machine, whatever).
> GNOME Remote Desktop supports integrating with the GNOME Display Manager (GDM)
to achieve remote login functionality. This feature is only available via the
RDP protocol. It works by the remote user first authenticating via a system
wide password, which gives access to the graphical login screen, where they can
login using their user specific credentials.
And then it seems to describe a pure-cli config process that you could set up once over SSH and then be able to RDP to the box thereafter.
There are no headless sessions on Wayland. At all.
You want proper headless session, set up X11 distro and use xrdp - it's really easy. But on wayland "remote support" to something that is already displayed on screen is all you can get now.
What I want is to be able to start a session remotely after a reboot, and continue that same session when I get back home. And conversely start a session while at my desk at home and resume that same session remotely. Without any weird limitations.
In other words, how RDP works on Windows.
So you're saying that is still not possible I take it.
