Whats wrong here? It should always be ok to ask for sources!

In this case the research is significant and it is reasonable to assume that avid readers here know the sources and need less research to respond quickly.

Here a quick overview:

Minsk Protocol (Sept 5, 2014)

Early on both sides supported militant groups with arms (e.g. the far right right Azov group for Ukraine and DPR for Russia), the governments did agree to a ceasefire, the groups didn’t care and both sides violated it numerous times. Ukrainian supported troops were shelling near Donetsk (Sept 20, 2014) and the DPR executed full scale attacks. https://web.archive.org/web/20141023221330/http://www.skynews.com.au/news/world/mideast/2014/10/23/ukraine-rebels-vow-to-take-back-cities.html

Minsk II (Feb 12, 2015)

Ukraine did shell Horlivka (March 10, 2015) https://en.wikipedia.org/wiki/Battle_of_Horlivka , killed civilians; claimed retaliation. The DPR tried to capture Debaltseve right before the ceasefire and failed to do so completely before it came into effect. As a result fighting within the city continued and the DPR even claimed the ceasefire did not include Debaltseve. https://en.wikipedia.org/wiki/Battle_of_Debaltseve so this was also violated by Ukraine too, but now we see a shift towards more Russian violations.

Later violations

The last violations where Ukraine can be assigned any noticeable role in are around 2020. Now that the military is more organized the troops do follow ceasefire orders more strictly and violations for ceasefires after 2020 can be nearly unilaterally assigned to the Russian side. https://en.wikipedia.org/wiki/Minsk_agreements (follow the links from there to more recent ceasefires)

So the image/meme is mostly true but also propaganda (as to be expected). I also do not know where the number of 20 agreements comes from. I do know/find details of about 8. Maybe somebody else can provide a list?

So in summary: The message is true. Russia and mainly the DPR troops they support can not be trusted to follow ceasefires as long as the conditions at the front do not significantly change.

I like sticking to the facts and do not agree with the presentation in the image, but at least its still way way closer to the truth than Russian propaganda. In this case sticking to the facts would even have sent the same message and not give the Russians any point where they can base their counterpoint on. On the other side differentiated and detailed analysis is not that well suited to steer up emotions and support for the cause.

Not per month, it was a one time fee to lay FTTB (optical fiber to the building) which would have allowed individual apartment owners to choose higher internet speeds if they need.

Living in a house with 40 parties, city is subsidizing optical fiber, only 5000€ for the whole building to be connected. Majority said no. So 50MBit/s is here to stay.

It is quite a bit out of date luckily. Signal-Desktop already stores data encrypted for quite a while. However it used to store the decryption key right alongside it. Recently (a few month ago) Signal switched to storing the key within the systems keystore, greatly improving security. Also causing a flood of users complaining that the can’t just copy their .config to a new desktop and retain their chat history. This may have prompted the release of this new feature :)

https://www.tomshardware.com/pc-components/cpus/dev-reports-that-intels-laptop-cpus-are-also-crashing-several-laptops-have-suffered-similar-crashes-in-testing

Mind, that this is just the company which published the initial reports that the defects in desktop CPUs are systematic, so I can see why Toms Hardware deems their Post a reliable source.

I wouldn’t conclude that from an Intel Employee even if they did claim it because they(Intel) already lied multiple times in this afair.

But they didn’t even do that, they just said desktop processors are affected, this doesn’t say mobile ones are not.

Many companies have already reported that their telemetry records many crashes with the exact same symptoms and software on their laptops while AMD still isn’t affected.

With very little initial work, physical media is also very convenient.

I buy a disk, put it into a specific drive, get a instant message when its ripped, check its name and put it into a folder. From there my mediabox converts it to a managable size and adds it to the collection.

Whin I turn on my TV I see all these Movies and shows neatly presented by Kodi. I have a tiny Wireless keyboard and can start any in under a second. No buffering, no adds, no matter if the router is connected, and no fear of ever loosing access.

Its great.

Exeptions are there of couse, I would love to buy The Orville, but they just don’t want my money!

Because somebody has to create that media. And that person they have to live. (Or better that huge team when it comes to movies) So they have to earn money, so somebody has to pay them.

I also enjoy that today I can test if something fits me If I am skeptical. But I also always make sure to pay back creators for things I enjoy so that in the future there will be more things I enjoy.

Of course I understand anybody who can not afford media and am happy to subsidize them with the part I am paying for good shows. But if you have a Plex server, you can afford it. And If you say its close just start with things you like most and at least say “thank you” to them.

But in the details this attack is not that bad. E.g. NordVPN and I guess also other VPNs use firewall rules to drop traffic on normal network interfaces.

Their side channel is still routing traffic away from the VPN channel. Then they can observe that there is no traffic and guess that the user either didn’t make requests in that moment or that he wanted to visit a website in the range covered by the route. They can not spy on the traffic.

Also you can not quickly move into a network and apply this attack, as DHCP leases usually last 1 day or at least 1 hour. Only when they expire you can apply the attack (or you force the user to drop from the network, which is easy if they are using WPA2, but only possible by blocking the wifi signal if they are using WPA3)

It is a serious issue and should be mitigated, but not as huge as news articles make it.

Run sudo apt dist-upgrade -y right after an upgrade to the Kubuntu 24.04 beta on a semi production system.

This is right after the xz thing happened. Also while Ubuntu made the t64 migration (Replaced packages with a 32 time variable with a 64 bit one, the packages are renamed. E.g. lib2geom1.2.0 to lib2geom1.2.0t64)

Packages based on the compromised xz had been removed from the repositories, but I already had some newer ones installed which where dependent on them. Also they already wanted the packages with the t64 addition, which by now where nowhere present in the system.

So dist-upgrade did what it could to upgrade 5 packages and bring the system into a consistent state: It uninstalled half of the system including some somewhat essential packages.

I noticed one of them scrolling by and hit CTRL+C. Afterwards I had the choice of saving the data and restoring from a backup a few weeks ago, or to patch it up by hand. So I did the second and created transitional packages like an empty lib2geom1.2.0t64 which depends on lib2geom1.2.0 which was in the repositories back then. 20 of these later I could install packages to get the GUI somewhat working and now weeks later all the t64 migrations are back in the repos and the system is fully functional again :)

Lessons learned:

• Be very careful with dist-upgrade
• Manually trigger a backup before a release upgrade

In now upgrade with
sudo apt-get update && sudo apt-get upgrade -yV && read -p "Flatpak Update? (yj/n): " choice && [[ $choice = [YyJj] ]] && sudo flatpak update --noninteractive
and equivs-build ( sudo apt install equivs) came in really handy in building the transitional packages fast.