There is also the risk of homograph attacks. The link below is for domain name encoding via IDN, but the same applies to usernames. You could easily impersonate another user by having chars that look similar.
There is also the risk of homograph attacks. The link below is for domain name encoding via IDN, but the same applies to usernames. You could easily impersonate another user by having chars that look similar.
Sure, but even if they started tomorrow it would probably be years before it even could be considered experimental outside of the most daring early adaptors.
Having a combability layer is not ideal but it would mean they could have something worker for more users faster and at the same time see which modules/drivers they should focus on.
What I meant was that if you are returning 404 for example when a user doesn’t exist. You can’t tell if the user doesn’t exist or someone changed the API to remove the endpoint.
But forcing HTTP codes without a moment to think it through seems to be the new fad.
The clown, but flipped with a success
field. If it is true then command succeeded, if it false something was wrong and there should be an error
field as well.
HTTP codes should be used for the actual transport, not shoe-horned to fit the data. I know not everyone will agree with this, but we don’t have to.
Rounded corners tho… <shudder>
Just a small gif (as png didn’t exist/widely supported) that had the rounded corner. Then if someone wanted to change the color or background you would have to redo all the images. Fun fun.
Sometimes they can be challenging or overgrown, so you have to know what you’re doing and be prepared to turn back if necessary, but I owe a lot of truly incredible experiences to this app.
Since it uses OpenStreetMap you should consider updating it for others later. Don’t think you can do it in Organic, but it can be as simple as in a browser adding a note to a trail about what state it is in.
And ethernet port!
…and it drives me insane when it is not real links but some javascript/button/div-with-onclick/etc and middle click won’t work
Most of those cookie banners are not even needed, you only need them for tracking cookie, not login and session cookies. But of course everyone decided it is just easier to nag all the users with a big splash screen.
A lot of them are not even doing it right, you are not allowed to hint the user that accept all is the “correct” choice by having it in a different color than the others. And being able to say no to all shouls be as easy as accepting all, often it isn’t.
Basically, cookie banners are usually not needed and when they are they are most often incorrectlt designed (not by accident).
…and when they don’t pay Discord under the table. Discord wouldn’t be unique if this was the case either.
I don’t know where you are getting those numbers from. Most put chrome in around 78%, edge at 10% and then everything else. And all chrome re-skins are just that, google still controls it. There is a reason one of the biggest software companies in the world just gave up their own browser engine and runs a competitor’s with some face paint.
Google are in a far better position to push something like this through than Microsoft ever where, due to their near monopoly on searches. Any site not using it would be more or less dead. Just going from number 1 to 2 on a google search can mean a huge drop in traffic, and then imagine not even being on it at all.
now it is mostly written for web browsers (between which there are no longer any significant differences in terms of standards compatibility).
At this point I think it is just a matter of time until Google (most likely due to their near monopoly with Chrome), will push for some new standard that they own and control and must be used everywhere. For some handwaving combination of security and protect the kids, etc. And google are in a great position to make it happen, don’t support it? Oh noes, your site is no longer listed in google searches.
And that will be the end of the open web, you can only use one browser that totally controls what you can and cannot do. Ad blocking is just the start, saving websites or images? Nah. We don’t allow that. Copy the url? No, you need to use this share button that has embedded tracking links in it, etc.
It also means that they can freeze separately
Pretty good summary of Microsoft’s “innovations” the last decade or so
The problem is that it is almost always just one lf them. Let’s say that v0.20 is called “Fuck Spez” and v0.21 is called “YouKnowWhatFuckMuskToo”.
Most people are going to refer to them by either the number or the name, almost never are both used. The biggest problem with names is that they are rarely sortable (google did it with android, for a bit but not anymore), so in the future it is hard to know which is which without resorting to looking at a list of releases.
For example, in the future when we are on v0.30 someone might say “ah, but this has been an issue since “Fuck Spez”.” And then most likely you have to look it up to know what they are talking about. If we coulld force everyone to alwaya write “version “Fuck Spez” (v0.20)” then it would be great, but that never happens.
I personally prefer just semantic versioning for this reason.
The original idea was to take back control of our money from greedy and corrupt banks and politicians. Very very very few people use it as that now though. Most just see it as a get rich quick scheme.
As we are in the privacy sublemmy: All of the privacy issues have already been solved, those that keep saying that it is a log of everyone you ever paid kept forever have no idea what they are talking about. Just simple thing like that you should (almost) never use an address twice removes a lot of the privacy concerns. There are also other ways to obfuscate and stay anonymous.
Then the bot would be useful, now it is just spam. If you want to watch it somewhere else: Use a browser plugin for it, don’t spam every thread.
Different workflows.
Just the ads, and you can’t turn them off. Ever.
There are quite a lot of quirks with how browser (or rather rendering engines) interpret CSS, and in quite a few places the spec is ambiguous. So there is no “correct” way of implementing it.
But, this is either just them being lazy or bad mangement.
It is usually not a good idea to specify what your exact metrics are for a ban. A bad actor could see that and then get around it by randomly upvoting something every now and then.