@praveen Encryption in matrix is more what I'd call an absolute cluster fuck. Inevitably you end up with failures to decrypt messages all the time. It's virtually unusable.
My Boeing 747-8 flight had a loose inner window glass and what seemed like a hole on the outside glass. It was loudly vibrating, pressing down on it with a finger made it stop.
Wealth taxes are inherently undemocratic and amount to illegal double taxation. They are not a reasonable subject for discussion.
They also impose a significant threat to social justice, as wealth doesn't get adjusted and eventually covers the top 50% and the top 1% is excluded anyway thanks to loopholes only they can exploit.
In order to create a fair taxation regime, first you need to link all tax caps and limits to indexes such that they automatically adjust wrt to their peers.
A free and fair market with equal opportunities for everyone is the cornerstone of our democracies and it is under constant attack from the extreme left, who want everyone to be poor and dependent on the state for all needs, and the extreme right, who want to exploit us all in a fascist neoliberal hellhole.
We need to defend it with all we've got, to the extent it doesn't negatively impact our fight against fascism.
It's not perfect but it's the best we've ever had.
Then you need to address the issue of generational wealth by fixing inheritance taxation and removing loop holes.
Then you need to start taxing people for fictional income, if they own their space of living, that amounts to the rent they save, such that you do not systematically undertax home owners.
This will likely be much more than a wealth tax but it is fair and reasonable.
@vv221 Well the key difference is that it's a license whereas I'm saying let's limit who we directly grant access to the software while anyone we do grant access to still gets it under the GPL (same works for anything).
Whether that's putting all your GPL repos behind a paywall with a free "I am an individual" option, or modifying the license grant.
I bought new ThinkPads in 2012 (well 2013), 2018, and 2023 (could have been 2021). 2012 to 2018 (i5-320M to 8250U) doubled performance, and 2018 to 2023 (to Ryzen 7650U Pro) doubled performance again.
That is, 2012 to 2021 quadrupled performance, and it about halved the power consumption, at light use anyway. Batteries can now last more than 3 hours, it's amazing.
but postfix is manually installed, postfix Conflicts mail-transport-agent, exim4 Provides mail-transport-agent.
Instead of
Error: Conflict: postfix:amd64 -> postfix:amd64=3.8.6-1build2 -> not exim4-daemon-heavy:amd64=4.97-4ubuntu4 -> not exim4:amd64=4.97-4ubuntu4 but exim4:amd64=4.97-4ubuntu4
The next step is to actually make this work correctly - right now the API isn't actually exposed from libapt-private.
And then rewrite the reporting. For each step of the implication graph, we need to look back up the original Dependency in the cache and then render one per line.
And this will become the error reporting format too so you get error messages like
As for the direction of the trixie transitional package, maybe that is the best. We'll certainly kill it after Trixie, then apt install keepassxc tells you the two choices and you can decide for yourself.
@debacle@nekohayo@keepassxc People are free to run upstream provided packages whether it be flatpak, snaps, or appimages to get the upstream experience.
It's not the Debian maintainer's job to implement the wishes of the upstream authors but to ensure that the software as delivered by Debian is not in conflict with Debian's values.
This includes patching out online functionality, dangerous IPC, pregenerated code, even the JavaScript shipped or referenced from external servers in html pages.