ISO/OSI is a neatly separated model mostly used on theory.

In practice, actual network stacks are often modeled after a simpler model that is called TCP/IP. Which despite the name is not actually TCP specific.

Here’s the general description and correspondence to ISO/OSI:

1. Host to network / network access layer: it’s mostly the nic and nic driver. It’s sometimes numbered as 0 because some don’t consider it part of the TCP/IP stack, but simply the nic driver. Corresponds to:
   1. Physical
   2. Datalink
2. Network layer: Corresponds to: 3. Network
3. Transport layer: Corresponds to: 4. Transport
4. Application layer: everything that’s part of the application and not the network stack. Corresponds to: 5. Session 6. Presentation 7. Application

Or, you can just not care about how the actual software stack is separated, and continue to use the most complete model, knowing that everyone will understand what you when you say “layer 2/3/4” anyway.

Plus, some could say that the TCP/IP model is equally unfit because the Linux network subsystem doesn’t care about layers.

Edit: I hope the formatting of that table isn’t broken on your client, because it is on mine

It places you one year ago before they rebranded in rocq (obviously to stop the puns)

Then, the year of the freebsd desktop came many years ago when apple released MacOS

What disconnecting problem?

My system should be fully updated, I will try an Xbox 360 cabled controller

That’s a flattering thought, but I think that kind of improvement is a pipedream.

The os shenanigans might be the reason tho

You are correct, it also lacks a decorative groove that the “one” one has near the top.

I think the “series” d-pad is the best modern d-pad, especially since Nintendo forgot how to make them just before releasing the Wii u. I’d say on par with classic Nintendo d-pads, maybe a bit less comfortable for platformers though.

On the other hand, the 360 d-pad is the worst most horrible piece of crap ever devised.

I am seeing higher latency even plugged via cable though, even if less so

No, kde on amd

yeah, but the point of a platform are the applications it supports, you don’t want to be The King of Nothing. If even after buying into wayland, applications still work bad on gnome because they expect to get support for X, than gnome needs X or to give a better option (better for the applications, not just according to themselves).

PING. Commenting just for the notification. I edited to respond to the other points but in the meantime you had already answered.

The point 2.1 “less to implement in the compositor” doesn’t apply, because for xwayland go work (which is intended to stay around for the foreseeable future) mutter still needs to implement SSD, it’s only skipping on implementing the Wayland SSD protocols.

Points 1 and 2.2 are not strong points. “We do <thing > because we always did before <thing 2>” is not a good point. For example, after all, we always used X10 before Wayland, and we always did implicit sync before last year. And compositor shouldn’t limit programming styles, they should support as many things as possible, and let the application decide their programming design. Plus, most modern applications on windows and macos embed a copy of chrome to display a single offline Web page, but I don’t see you suggesting we replace compositors with browsers.

Point 2.3 is also weak because most of the things a compositor does are already hard, but they implement them because it makes the experience better. If something is hard, it just means it will be worked on more. Take a look at explicit sync, it took like 4 years to be rolled out, but it was necessary and got implemented.

I’ll give you point 2.3.1… in general I think KDE looks pretty bad, and gnome is really more polished in many aspects. Unfortunately I really prefer the KDE workflow on big screens (but gnome on laptops).

You mean about adding SSD to gnome, which will not happen?

As an argument in favour, I see:

• Support for more applications that “don’t want” to implement CSD (i.e. foot terminal, davinci resolve, that one archive manager I can’t remember)
• Lifting burden for applications that don’t need custom decoration buttons, and so don’t care about implementing their own decorations
• Making the decorations on those applications consistent with the theming of the system

As an argument against, I personally don’t see any. Sure, most gtk apps are designed for CSD and will not translate well to SSD, but I just don’t see why that should stop gnome from implementing SSD. I remember the gnome maintainers were strongly convinced against SSD, but I don’t remember their argument

If you are writing a parser in haskell just use Happy and get it over with

I experience something similar on a vega56, but it doesn’t happen on generic high loads, it happens only

• in some specific loads (for me it was mainly A Plague Tale: Requiem)
• when something touches the grounding of my monitor (the display port of the GPU is faulty, it seems)

I would like to interject for a moment. This statement is technically true but disingenuous and facetious.

While it’s true that Linux is just the kernel, what most people refer to as Linux is actually the Operating System GNU/Linux, or, as RMS would now call it, GNU plus Linux, or sometimes, a less GNU depended, but mostly GNU/Linux compatible OS, or, as I have literally just now come to call it */Linux.

Moreover, a modern */Linux system is expected to be based on SystemD, unless explicitly avoiding it due to some technical constraint or some desired feature of another init system. One could come to call this SystemD/Linux.

And lastly, this kind of use case would be the perfect match for a Wayland shell, as opposed to an X11 shell. Which would be more efficient, and would give the shell more freedom in the management of windows.

As a result, when asking about a Linux phone, we could expect one is talking about a phone running a SystemD+Wayland/Linux OS, or at least a mobile-focused */Linux OS.

The Android kernel is a, largely downstream, fork of the Linux kernel, but the Android OS is in almost no way compatible with any */Linux OS, and it’s instead its own completely different OS.

The server in question is a raspberry with 4 gigabytes of ram, so I will need to use containers very sparingly. Basically I’m using podman quadlets only for those services that really only comes in containers (which for now means only codimd, overleaf, and zigbee2mqtt), and I’m running everything else on metal. But even with containers, I would still need to manage container configurations, network, firewall, file sharing permissions, etc. just like I did without containers.

I think that someone already tried (and failed) to make a wrist band thingy in the past, so they probably can’t patent it. That is, unless they went out of their way to patent the sensor technology itself, or the UX, instead of the concept of a wristband thingy

Well, I don’t use most of their stuff because I mostly run self hosted stuff that either don’t need their proxy stuff or violate their content policies (you can’t serve movies/video over their proxy, which is reasonable). But if I wanted to I already have all of that at my disposal, without any extra money.

I haven’t read the article yet, but I just wanted to say a couple of things.

First of all, I keep noticing people around me with bulky glasses that look like they came out of the DEVO peek a Boo video, and all I can think is that if I where Facebook I would use my power to influence fashion towards bulky glasses and make my glasses look sleek by comparison.

Second, it sucks that the wrist band thing is being tied with bullshit ai glasses. I would love to see that as a regular input device for PCs and smartphones.