[-] kevincox@lemmy.ml 2 points 5 days ago

Maybe in some areas. But in downtown Toronto tons of restaurants are super busy, and delivery orders seem through the roof. But this also doesn't really solve the tipping problem, it seems pretty orthogonal.

[-] kevincox@lemmy.ml 3 points 5 days ago

No, I don't mean a law. I don't even know how you would make this a law. You can already legally just walk away. Maybe you can have a law that the "no tip" option on card machines must be at least as easy as the tip option or something.

There is no such thing as "everyone", but you only need a tipping point. Maybe 1/3 of people or similar. You just need enough awareness so that it isn't considered incredibly rude or outrageous, that most retail workers will understand what is happening and the businesses will see it coming. It definitely wouldn't be easy, that is why I would put the target date far in advance (maybe next January is actually too close). So that cultural knowledge could slowly be built and enough people to make a difference would switch at the same time.

[-] kevincox@lemmy.ml 12 points 5 days ago

IMHO if we want to get rid of tips the way to go about it is to pick a date (for example January 1st 2026) then agree to stop tipping on that date. Hard and fast stop doing it. Stores can raise their prices to compensate.

The problem is that it is very hard to make this change incrementally. Because individuals are considered assholes if they don't tip enough. So we all sort of got to get together and agree to it. Of course it will be hard to publicize this because big media companies are all owned by the rich that benefit by paying minimum wage workers less with the excuse that they can get tips.

[-] kevincox@lemmy.ml 14 points 6 days ago

While I agree, I think that getting more games on Linux is far more useful. When Linux is almost 3% very few studios will care much. If they can do a small bit of testing on Proton and maybe work around a bug or two they are far more likely to do that then make and test a native build. If this then gets Linux usage to 5, 10 or 20% that will drive more native builds.

So I agree that it somewhat reduces the incentive to release a native build. But I think that is outweighed by the benefits of making the Linux gaming experience better today which will have a greater impact on availability of native builds in the future.

[-] kevincox@lemmy.ml 123 points 6 months ago

which is supposed to enforce to run apps in secured phones

The point of the Google Play Integrity API is to ensure that the user is not in control of their phone, but that one of a small number of megacorps are in control.

Can the user pull their data out of apps? Not acceptable. Can the user access the app file itself? Not acceptable. Can the user modify apps? Not acceptable.

Basically it ensures that the user has no control over their own computing.

20
submitted 10 months ago by kevincox@lemmy.ml to c/selfhosted@lemmy.world

Is there any service that will speak LDAP but just respond with the local UNIX users?

Right now I have good management for local UNIX users but every service wants to do its own auth. This means that it is a pain of remembering different passwords, configuring passwords on setting up a new service and whatnot.

I noticed that a lot of services support LDAP auth, but I don't want to make my UNIX user accounts depend on LDAP for simplicity. So I was wondering if there was some sort of shim that will talk the LDAP protocol but just do authentication against the regular user database (PAM).

The closest I have seen is the services.openldap.declarativeContents NixOS option which I can probably use by transforming my regular UNIX settings into an LDAP config at build time, but I was wondering if there was anything simpler.

(Related note: I really wish that services would let you specify the user via HTTP header, then I could just manage auth at the reverse-proxy without worrying about bugs in the service)

[-] kevincox@lemmy.ml 141 points 11 months ago

Allowing showing different domains than the actual click target is wildly reckless and should be punishable.

"Oh but our poor advertisers want to use click tracking and it is too hard to set up on their main domain". Oh boo hoo, I'm sure if it is important to them they will figure it out.

[-] kevincox@lemmy.ml 131 points 1 year ago

Because people don't understand how copyright works.

In most countries any copyrightable work that you produce is automatically covered by copyright. You don't need to do anything additional to gain that protection.

Most Lemmy instances don't have any sort of licensing grant in their terms of service. So that means that the original author maintains all ownership of their work.

So technically what these people are doing is granting a license to their comment that allows it to be used for more than would otherwise be allowed by the default copyright protections.

What they are probably trying to accomplish is to revoke the ability for commercial enterprises to use their comments. However that is already the default state so it is pretty irrelevant. Basically any company that cares about copyright and thinks that what they are doing isn't allowed as fair use already wouldn't be able to use their comments without the license note. So by adding the license note all they are doing is allowing non-commercial AI to scrape it (which is probably not what was intended). Of course most AI scraping companies don't care about copyright or think that their use is not protected under copyright. So it is again irrelevant.

[-] kevincox@lemmy.ml 153 points 1 year ago

Death to HDMI. DisplayPort is the superior port.

17
submitted 1 year ago by kevincox@lemmy.ml to c/rssfeeds@lemmy.world
[-] kevincox@lemmy.ml 64 points 1 year ago

if staying outside EU

I'm pretty sure this is explicitly not allowed because most of the EU laws apply to EU citizens and residents. So if an EU citizen stays outside the EU they aren't allowed to stop following the EU rules.

[-] kevincox@lemmy.ml 246 points 1 year ago

This is why DisplayPort is the better connector. Because they don't have their thumbs up their asses.

It always saddens me how much user pain has been caused and money wasted in implementing DRM which as far as I can tell hasn't succeeded in preventing a single movie or TV show from being available on torrent sites.

[-] kevincox@lemmy.ml 146 points 1 year ago

Back in the day X was a great protocol that reflected the needs of the time.

  1. Applications asked it to draw some lines and text.
  2. It sent input events to applications.

People also wanted to customize how their windows were laid out more flexibly. So the window manager appeared. This would move all of your windows around for you and provide some global shortcuts for things.

Then graphics got more complicated. All of a sudden the simple drawing primitives of X weren't sufficient. Other than lines, text and rectangles applications wanted gradients, rounded corners and to display rich graphics. So now instead of using all of these fancy drawing APIs they were just uploading big bitmaps to the X server. At this point 1/3 of what the X server was previously doing became obsolete.

Next people wanted fancy effects and transparency (like drop shadows). So window managers started compositing the display. This is great but now they need more control than just moving windows around on the display in case they are warped, rendered somewhere slightly differently or on a different workspace. So now all input events go first from X to the window manager, then back to X, then to the application. Also output needs to be processed by the window manager, so it is sent from the client to X, then to the window manager, then the composited output is sent to X. So another 1/3 of what X was doing became obsolete.

So now what is the X server doing:

  1. Outputting the composited image to the display.
  2. Receiving input from input devices.
  3. Shuffling messages and graphics between the window manager and applications.

It turns out that 1 and 2 have got vastly simpler over the years, and can now basically be solved by a few libraries. 3 is just overhead (especially if you are trying to use X over a network because input and output need to make multiple round-trips each).

So 1 and 2 turned into libraries and 3 was just removed. Basically this made the X server disappear. Now the window manager just directly read input and displayed output usually using some common libraries.

Now removing the X server is a breaking change, so it was a great time to rethink a lot of decisions. Some of the highlights are:

  1. Accessing other applications information (output and input capture) requires explicit permission. This is a key piece to sandboxing applications.
  2. Organize the system around frames to avoid tearing except for when desired (X doesn't really have the concept of a frame).
  3. Remove lots of basically unused APIs like fonts, drawing and many others.

So the future is great. Simpler, faster, more secure and more extensible. However getting there takes time.

This was also slowed down by some people trying to resist some features that X had (such as applications being able to position themselves). And with a few examples like that it can be impossible to make a nice port of an application to Wayland. However over time these features are being added and these days most applications have good Wayland support.

362
Haunted House (xkcd.com)
134
submitted 2 years ago by kevincox@lemmy.ml to c/linux@lemmy.ml

I'm reconsidering my terminal emulator and was curious what everyone was using.

35
submitted 2 years ago by kevincox@lemmy.ml to c/lemmy@lemmy.ml
[-] kevincox@lemmy.ml 134 points 2 years ago

People are getting all upset at Facebook/Meta here but they were served a valid warrant. I don't think there is much to get mad about them here. The takeaway I get is this:

Avoid giving data to others. No matter how trustworthy they are (not that Meta is) they can be legally compelled to release it. Trust only in cryptography.

There is of course the other question of if abortion being illegal is a policy that most people agree with...but that is a whole different kettle of fish that I won't get into here.

2
submitted 2 years ago by kevincox@lemmy.ml to c/fediverse@lemmy.ml
2
submitted 2 years ago by kevincox@lemmy.ml to c/linux@lemmy.ml
view more: next ›

kevincox

joined 4 years ago
MODERATOR OF