Olissipo

joined 2 years ago
[–] Olissipo@programming.dev 13 points 1 month ago (1 children)

The OP on Mastodon shared screenshots of the replies (can't tell if they were originally in the forum post, or if it's a DM):

https://nextcloud.aztinet.eus/s/sxqEDJDZGp7a9rx

[–] Olissipo@programming.dev 57 points 1 month ago (26 children)

The post on Mastodon has a screenshot of the post edit history:

Screenshot of a forum post, showing the versions before and after an edit. The sentence "I am queer, I am technically a furry too" was edited into "I am technically a furry too"

And a copy-pasted response from a moderator (the most relevant bit):

So in my opinion, if your intention was to show political support for diversity, you should avoid using this flag. This will allow us to refuse the use of a flag for instance saying 'non-queer', If we allow your flag, then we have to admit also other similar political flags, both supporting and opposing diversity.

[–] Olissipo@programming.dev 6 points 1 year ago* (last edited 1 year ago)

This one in South Korea is pretty recent (October 2022).

A special police team conducted an investigation of the disaster within a few days of it occurring, and concluded on 13 January 2023 that the police and governments' failure to adequately prepare for the crowds, despite a number of ignored warnings, was the cause of the incident.

[–] Olissipo@programming.dev 3 points 1 year ago (1 children)

Ok, I understand what you meant, thanks.

Basically, after I’ve read all of that, it’s clear as day that security is not a priority on Testing. And while band-aid solutions do exist, it’s simply not designed to be secure.

Yeah, I wouldn't run it in a production environment.

[–] Olissipo@programming.dev 1 points 1 year ago (3 children)

Sure, but even in those "few cases" Testing will get them soon.

I did read at some point that Testing may receive security updates later than stable, might be in those cases in which backports come straight from unstable.

[–] Olissipo@programming.dev 1 points 1 year ago (5 children)

I don’t recommend going for (Debian’s/Devuan’s) testing (branch) as it targets a peculiar niche that I fail to understand; e.g. it doesn’t receive the security backports like Stable does nor does it receive them as soon as Unstable/Sid does. Unstable/Sid could work, but I would definitely setup (GRUB-)Btrfs + Timeshift/Snapper to retain my sanity.

From https://backports.debian.org/ :

Backports are packages taken from the next Debian release (called "testing"), adjusted and recompiled for usage on Debian stable

So by definition, security backports in stable are present in Testing in the form of regular packages, right?

[–] Olissipo@programming.dev 3 points 1 year ago* (last edited 1 year ago) (1 children)

I remember having some issue like that, but I'm not sure if this was the fix.

Try unchecking "Show desktop notifications when the song changes" on Spotify's settings (right now it's under the Display section).

[–] Olissipo@programming.dev 2 points 1 year ago

Makes sense, thanks.

[–] Olissipo@programming.dev 5 points 1 year ago* (last edited 1 year ago) (6 children)

New to Linux: in which case would you stick with an "old-old-stable" release?

Software incompatibility?

54
submitted 1 year ago* (last edited 1 year ago) by Olissipo@programming.dev to c/linux@programming.dev
 

The Debian Long Term Support (LTS) Team hereby announces that Debian 10 "buster" support will reach its end-of-life on June 30, 2024, nearly five years after its initial release on July 6th, 2019.

Starting in July, Debian will not provide further security updates for Debian 10. A subset of "buster" packages will be supported by external parties. Detailed information can be found at Extended LTS.

The Debian LTS Team will prepare afterwards the transition to Debian 11 "bullseye", the current oldstable release. Thanks to the combined effort of different teams including the Security Team, the Release Team, and the LTS Team, the Debian 11 life cycle will also encompass five years. To make the life cycle of Debian releases easier to follow, the related Debian teams have agreed on the following schedule: three years of regular support plus two years of Long Term Support. The LTS Team will take over support from the Security and the Release Teams on August 14, 2024, three years after the initial release on August 14, 2021. The final point update release for "bullseye" will be published soon after the final Debian 11 Security Advisory (DSA) will be issued.

Debian 11 will receive Long Term Support until August 31, 2026. The supported architectures remain amd64, i386, arm64 and armhf.

1
submitted 2 years ago* (last edited 2 years ago) by Olissipo@programming.dev to c/wordpress@lemmy.world
 

This might not be new, I hadn't dealt with WordPress/WooCommerce in a while.

Currently (v8.8.2) in a new WooCommerce installation the "Checkout" page is created using blocks, like so:

<!-- wp:woocommerce/checkout-payment-block -->
<div class="wp-block-woocommerce-checkout-payment-block"></div>
<!-- /wp:woocommerce/checkout-payment-block -->

(...)

The problem

This might introduce breaking changes to the plugins and themes you normally use. For example, I couldn't add a new field - programatically or using a plugin.

The fix

Remove the blocks and revert to using the shortcode:

[woocommerce_checkout]

[–] Olissipo@programming.dev 2 points 2 years ago* (last edited 2 years ago)

Fellow PT-PT ISO user here. And although I use PT-PT in the OS, both my mechanical keyboards' physical layout is DE ISO, which has most special symbols in the same place. (finding DE keyboards is easier)

I've considered switching to UK ISO before. Typing brackets "[] {}" and a semicolon ";" is harder in PT-PT. Especially the curly brackets {}, which are really awkward to type with my small hands.

[–] Olissipo@programming.dev 1 points 2 years ago

One that is written in C and also has a Python module: https://aubio.org/

[–] Olissipo@programming.dev 11 points 2 years ago

I don't agree with the problem they aim to solve with those goals.

But today it takes several years of mastering tools and frameworks to get to that stage. HTML First principles should allow people to unlock that feeling, and level of mastery, much earlier on in their coding journey.

The onboarding process can be made easier for devs new to the project (junior or senior) with decent documentation. Just enough install/build the project in their local machine and understand the gist of the technologies.

view more: next ›