• 0 Posts
  • 29 Comments
Joined 2 years ago
cake
Cake day: July 1st, 2023

help-circle
  • arc@lemm.eetoLemmy Shitpost@lemmy.worldCommon British L
    link
    fedilink
    arrow-up
    4
    ·
    edit-2
    14 days ago

    Stole it? I think adopted is more apt. And curry isn’t one thing and varies from region to region in India. But Britain loved it so much that there is an Indian (or Pakistani) restaurant practically everywhere. And while Indian / Pakistani chefs have invented new dishes (e.g. chicken chasni is the best goddamned curry ever), I wouldn’t call it cultural appropriation.


  • arc@lemm.eetoLemmy Shitpost@lemmy.worldCommon British L
    link
    fedilink
    arrow-up
    12
    arrow-down
    1
    ·
    14 days ago

    British people love curries and other spicy things. For most people curries, biriyanis are going to be in the rotation. Even “traditional” British food will usually have things like black pepper, nutmeg, mace, ginger, cumin, cloves, mustard, bay leaves, juniper berries in it. More recently cumin, paprika, tumeric, coriander, curry powder might be thrown into dishes.


  • Actually what would happen is dem support would crash even more because the GOP playbook works. AOC will be branded a socialist, a communist, ready to sell out, to take people’s property etc. Doesn’t matter if it’s true or not, the electorate will believe it. If the dems want to win they need to lose the haughtiness and a projecting an air of superiority that they know what’s right for people and appeal to blue collar workers again. i.e. messaging needs to change. That might make people more receptive to left wing / progressive views. They also need to read the GOP playbook and create some divisive issues for the right to deal with. But expecting people to accept/embrace/own socialism is a joke. It won’t happen. Think smart.







  • arc@lemm.eetoComic Strips@lemmy.worldISO 8601
    link
    fedilink
    arrow-up
    30
    ·
    1 month ago

    The sane way of dealing with it is to use UTC everywhere internally and push local time and local formatting up to the user facing bits. And if you move time around as a string (e.g. JSON) then use ISO 8601 since most languages have time / cron APIs that can process it. Often doesn’t happen that way though…



  • arc@lemm.eetoLinux@lemmy.ml*Permanently Deleted*
    link
    fedilink
    arrow-up
    5
    ·
    2 months ago

    Depends what you mean by bloat. It has a very large repo, but it compiles into little commands with least privilege execution. A lot of those commands are specifically there so someone doesn’t have to pull in other repos with a larger attack surface. e.g. there is a time sync daemon to replace having to pull in ntp which is a lot more complex and fraught and the one thing most desktops need of NTP which is to set the clock.


  • arc@lemm.eetoLinux@lemmy.ml*Permanently Deleted*
    link
    fedilink
    arrow-up
    2
    arrow-down
    1
    ·
    edit-2
    2 months ago

    Why do you still exist? I try understanding what the purpose of your reply could be? Screenrecords do not work. For plenty of people. Google it. Yet you feel entitled to share you smalldick energy wisdom of “proper way”. That is exactly the vibe of the shit ppl. You do not help Wayland or x11 or anything, you just fap into your own mouth because nobody can ever love you like that. Go get help.

    Wow, someone needs to grow up. You laid into Wayland when screen recording doesn’t even go through Wayland. The app asks the WM to screen record via DBus. A more constructive response would have been “thanks I didn’t know that”, or perhaps “oh it’s a driver issue”, or “it’s an issue with that WM/ffmpeg/pipewire or whatever”, or anything else likely to be the underlying cause. But it’s not Wayland. Have you got that? Not Wayland. There is no need to be sore and immature about it.


  • arc@lemm.eetoLinux@lemmy.ml*Permanently Deleted*
    link
    fedilink
    arrow-up
    4
    arrow-down
    1
    ·
    edit-2
    2 months ago

    Screen records do work providing the app asks for a screen cast in the proper way (which BTW is not via Wayland but through a message to a DBus service). The service and the desktop then ask permission from the user if necessary. X11 didn’t give a damn about protecting the contents of your screen and any app whether it was beneficial or malicious could do it with impunity. So you should see this as a major security improvement - you can screen record but only if permission is granted.


  • arc@lemm.eetoLinux@lemmy.ml*Permanently Deleted*
    link
    fedilink
    arrow-up
    6
    ·
    2 months ago

    Yes it’s been stable for some time with a couple of caveats - you need a decent graphics driver and not be using apps with edge cases.

    Here is a simple example of an edge case and it’s not hard to find people blaming Wayland even though with some thought this was a security issue - apps like Zoom, Discord, MS Teams want to do screen sharing which is easy in X11 because it has non existent security - just steal the screen bitmap. That’s a problem.

    Wayland (the protocol) provides no means for one app to grab the screen, or other apps. This is by design for security. Instead the app must be a good citizen and send a “i want to screen cast” message to the xdg-desktop-portal (a service provider implemented by GNOME, KDE etc.), the desktop asks for user consent and then the app gets a video stream. So it’s a lot more secure but it requires the app and the WM do things properly.

    Desktops and apps have matured and these issues are thankfully going away. I think the biggest hurdle left is proper graphics drivers, especially the problem of getting NVidia drivers working.