0x4E4F

joined 1 year ago
MODERATOR OF
[–] 0x4E4F 1 points 18 hours ago

First, what distro? Second, what are the exact libs the package is looking for?

[–] 0x4E4F 0 points 18 hours ago* (last edited 18 hours ago)

See, this is one of the many reasons why people left Lemmy. Stuff normal people laugh at. Not that I like this stuff all the time, but it is funny seeing it from time to time.

I am a nerd, but I like my feed versatile. It was interesting at the start when the normies were here with the shitposts and all that, and they tried, they really did... now this place is just boring and stale AF.

[–] 0x4E4F -1 points 2 days ago (2 children)

I bet you're the life of the party.

[–] 0x4E4F 1 points 3 weeks ago

Yeah, good point 👍.

[–] 0x4E4F 2 points 3 weeks ago* (last edited 3 weeks ago)

I think .ml defederated from us, since I can see posts from .ml just fine, but there's radio silence when I reply. I have another account on sh.itjust.works, same thing happens with it.

And I don't think you can ban accounts on an instance basis, only on a community basis. And it's fairly clear when that happens, you can't post in that community, that's about it.

[–] 0x4E4F 2 points 4 weeks ago (2 children)

BTW, I didn't know we were being blocked by lemmy.ml, so basically just people from sh.itjust.works can see this.

 

Official statement regarding recent Greg' commit 6e90b675cf942e from Serge Semin

Hello Linux-kernel community,

I am sure you have already heard the news caused by the recent Greg' commit 6e90b675cf942e ("MAINTAINERS: Remove some entries due to various compliance requirements."). As you may have noticed the change concerned some of the Ru-related developers removal from the list of the official kernel maintainers, including me.

The community members rightly noted that the quite short commit log contained very vague terms with no explicit change justification. No matter how hard I tried to get more details about the reason, alas the senior maintainer I was discussing the matter with haven't given an explanation to what compliance requirements that was. I won't cite the exact emails text since it was a private messaging, but the key words are "sanctions", "sorry", "nothing I can do", "talk to your (company) lawyer"... I can't say for all the guys affected by the change, but my work for the community has been purely volunteer for more than a year now (and less than half of it had been payable before that). For that reason I have no any (company) lawyer to talk to, and honestly after the way the patch has been merged in I don't really want to now. Silently, behind everyone's back, bypassing the standard patch-review process, with no affected developers/subsystem notified - it's indeed the worse way to do what has been done. No gratitude, no credits to the developers for all these years of the devoted work for the community. No matter the reason of the situation but haven't we deserved more than that? Adding to the GREDITS file at least, no?..

I can't believe the kernel senior maintainers didn't consider that the patch wouldn't go unnoticed, and the situation might get out of control with unpredictable results for the community, if not straight away then in the middle or long term perspective. I am sure there have been plenty ways to solve the problem less harmfully, but they decided to take the easiest path. Alas what's done is done. A bifurcation point slightly initiated a year ago has just been fully implemented. The reason of the situation is obviously in the political ground which in this case surely shatters a basement the community has been built on in the first place. If so then God knows what might be next (who else might be sanctioned...), but the implemented move clearly sends a bad signal to the Linux community new comers, to the already working volunteers and hobbyists like me.

Thus even if it was still possible for me to send patches or perform some reviews, after what has been done my motivation to do that as a volunteer has simply vanished. (I might be doing a commercial upstreaming in future though). But before saying goodbye I'd like to express my gratitude to all the community members I have been lucky to work with during all these years.

[–] 0x4E4F 1 points 4 weeks ago

It's a well known facts, specifics are not necessary, I could list hundreds of other cases where I can prove that. I seriously doubt Finland would be an exception from that.

[–] 0x4E4F 1 points 4 weeks ago* (last edited 4 weeks ago) (2 children)

1st world countries profiting on the backs of 3rd world ones is a completely unknown concept for you I guess.

[–] 0x4E4F 2 points 4 weeks ago (1 children)

It's probably a proprietary connector made specifically for Yamaha, or Yamaha made it themselves. It's loosely based on car connectors from what I can see, but I don't think you're gonna find much info about it.

I'd just go in "guns blazing" with this thing. If there is a replacement for it and it's fairly cheap I mean. If not, I'd try and pry the silicon off with some of my DIY tools for these sorts of situations.

[–] 0x4E4F 2 points 4 weeks ago (3 children)

I wish to know how to open this socket to access the rubber/silicone seal inside, and to know that first I need to identify the name of this connector

What exactly do you mean by this, is the connector sealed?

[–] 0x4E4F 2 points 4 weeks ago

Yeah, that could actually be fun to be honest, lol 😂. But I just know the PR would be rejected, lol 😂.

[–] 0x4E4F 8 points 1 month ago

That is... brilliant! I love it!

 
53
Watching glue dry (self.parenting)
 

I was fixing some toys of my 5 year old and he asked me if he could watch the glue dry... I told him "son, that's like watching grass grow 😒"... his reaction, "really 😱... can I go in the backyard?", me "yeah, sure, I guess 🤦 😂".

He's still there... sitting on the ground, watching... asking every 2 minutes if the grass is any taller 🤣.

 
857
Oh, come on! (sh.itjust.works)
 
 
 
 
653
Damn Linux users! (sh.itjust.works)
 
 
77
ChatGPT as an Arch user (sh.itjust.works)
submitted 1 month ago by 0x4E4F to c/[email protected]
 
view more: next ›