photog.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A place for your photos and banter. Photog first is our motto Please refer to the site rules before posting.

Administered by:

Server stats:

238
active users

#lkml

1 post1 participant0 posts today
Replied in thread

@BrodieOnLinux @qdot I find it weird to see #FLOSS #devs use an #InformationBlackhole like #discord which combines all the disadvantages of #MailingList, #IRC, #XMPP, #Matrix and even #MicrosoftTeams and #Signal without any redeeming qualities of any of those, like a functioning search & logging.

  • Like the #LKML is kinda shit in terms of UX but at least there are searchable indexes for it so one can just point at a specific message & comment wthout having to be granted access to it.

Not to mention that discord is #ableist af by literally preventing the use of #Screenreader-friendly browsers such as #Lynx and #dillo to work, blocking @torproject / #Tor users and explicitly banning the use of it's #API to build better clients.

  • Not even a #paid-for exception is offered, thus making integration into even paid-for tools like #HootSuite not legally possible!

Linus Torvalds has proper motivated reasons for really disliking file systems without a case sensitivity.

Read this with me from the kernel lkml, regarding bcachefs.

Re: [GIT PULL] bcachefs fixes for 6.15-rc4 - Linus Torvalds
lore.kernel.org/lkml/CAHk-=wja

🖋️ #bash #sh #zsh #ksh #csh #tcsh #fish #git #Linux #lkml #POSIX #FOSS #100daysofCode #640DaysOfCode #coding #1024DaysOfCode #github #programming #Torvalds #filesystem

lore.kernel.orgMaking sure you're not a bot!
Replied in thread

@debby that assumes @protonprivacy actually cares about #Privacy, which they evidently don't, cuz otherwise they'd never even #log or #request any #PII to begin with and instead offer their Services via @torproject / #Tor as #OnionService

  • Not to mention they fuck around with customers' #eMails, thus having prevented people from contributing to the #LKML in the past...

To me this isn't a big loss, but a conditionless surrender in favour of better competitiors like @monocles and even @Stuxhost for that matter...

#discord IS LITERALLY THE PROBLEM!

I'm shure fecking #dread has better moderation and I'd rather use #MicrosoftTeams + #Slack cuz those at least have proper #moderation tools.

  • And I'd rather subscribe to the #LKML and see my inbox getting hosed than using any shitty #SaaS!

Case in point: I'd rather #SelfHost all my comms infrastructure than to ever use something like Discord or any other #GDPR-violating SaaS that is just enshittification.

I'd rather recommend people to instead choose a tool that does everything but horrible to go with multiple smaller & good tools

Check @alternativeto and @european_alternatives for options.

Continued thread

Wenn ihr ansonsten auf der #LKML schreibt, mein Rat: Nur über so was wie Firefox Relay schreiben / Adresse im Mailclient dahin modifizieren (bin mir gerade nicht sicher, ob das dann durchgeht), weil die Webscraper des Mailarchivs euch nachher Spam bescheren.

Wann man auf der #LKML beantragen, dass die eigene Mailadresse da rausgelöscht wird? Seit ich vor ~3 Jahren geschrieben habe, bekomme ich auf der Adresse Spam, es ist ärgerlich, weil ich auch sonst immer aufgepasst habe.

Continued thread

2/ For completeness, as it's easy to miss in Kent's long post:

Kent refuses to send a public apology for a remark to a mm developer that lead to the escalation to the COC. Search for "you should probably send him an apology" in his Patreon post to find a good place to start.

Also note that Kent resurrected the #LKML thread with the remark yesterday; new messages start here: lore.kernel.org/all/vvulqfvftc

Replied in thread

@bigolifacks and that makes it worse than #NSAbook or #Shitter because those can at least be scraped, archived, exported and somewhat transfered.

I'd rather #SelfHost @zulip, #JitsiMeet with a #VoIP-Bridge, @nextcloud + @collabora than use #Discord because those don't prevent one from sharing content or actually #archiving and #exporting conversations.

  • Thus Discord is objectively evidenced as irredeemably bad because it's worse than #ICQ - even in the #ToS!

#LKML QOTD from @torvalds:

"'[…] no [#Linux] #kernel developer should spend one single second worrying about out-of-tree modules.

It's simply not a concern - never has been, and never will be.

Now, if some out-of-tree module is on the cusp of being integrated, and is out-of-tree just because it's not quite ready yet, that would maybe be then a case of "hey, wait a second".

But no. We are not going to start any kind of feature test macros for external modules […]'"

lore.kernel.org/all/CAHk-%3Dwg

lore.kernel.orgRe: [GIT PULL] sysctl changes for v6.11-rc1 - Linus Torvalds

#LKML #QOTD from @torvalds:

```Case insensitivity is a subject near and dear to my heart.

And when I say "near and dear to my heart", I obviously mean "I despise it, and I have spent _decades_ ranting against it and trying to explain why it's a problem".```

lore.kernel.org/all/CAHk-%3Dwi

In the same thread:

```But then at some point, we failed at life, and started filling in the upper bit cases too.

Looking around, it was at Linux-2.0.1[…]```

lore.kernel.org/all/CAHk-=wiTy

lore.kernel.orgRe: [PATCHSET 0/3] xfs: fix ascii-ci problems with userspace - Linus Torvalds

@gregkh yesterday on #LKML:

```
> How's your effort to get device vendors/oems to use
> newer (major) kernels on their devices going?

Actually really well, with the new EU regulations and the reduced amount of support time for LTS kernels[1], new devices will soon be forced to update to move to newer kernel versions during the lifetime of the device. […]
```

lore.kernel.org/all/ZBtalAJ1z4

[1] fosstodon.org/@kernellogger/10 #Linux #kernel #LinuxKernel

lore.kernel.orgRe: 5.10 LTS - Request for inclusion of getsockopt(SO_NETNS_COOKIE) - Greg Kroah-Hartman