At least where I work, the developers who actually wrote the code would probably never see it. We have service staff that deal with an initial problems reported from customers. They’d likely figure out someone actually entered those values.
They are quite well seasoned. But it’s also worth noting they are developers as well because the job usually has you debugging things or writing code that needs to be run for the specific customer. Not a large amount of code, but just things that end up being specific to a customer.
And if they have to come to a developer that actually works on the product, it’s usually a pain to try and figure out what is going on. Thankfully, this is very uncommon.
And the practice. In most cases are doctors are now essentially hair stylists working for some larger entity. A larger entity with shareholders. If you want somebody that cares you probably need to go see a family practice with only one or two doctors. The problem is places like that run out of spaces to see people quickly.
Corporations, now. Can’t even really call it a practice. They are businesses that employ doctors. In law, most civilized places, you can’t own stake in a law firm unless you are a member of the bar. Makes for a more service focused industry.
Another thing I haven’t seen mentioned is the way people find doctors now has changed. People look online, and there are plenty of sites that are just aggregators for data about doctors. Anyone can scrape that info and then setup a webpage to rate doctors. So now doctors are finding that they aren’t getting patients if they aren’t getting good ratings, so now we have doctors just telling patients what they want to hear, prescribing what they want to be prescribed. Gotta keep up that 9.8/10 rating to keep patients coming in.
Find people with similar hobbies as you on a particular community online. Back when I was active on Reddit, I had made two friends this way. Unfortunately, after the whole API shaboink, I left Reddit, and lost contact with one of them.
Doctors are not individual practitioners and cannot normally decide to go off on their own doing a procedure that they were not specifically trained to do (doctors are trained in procedures during their residency and in CTE). Unless they are offered a course in this new method, the hospital would not authorize them to perform that new procedure. The best way to get this care would be to travel or to lobby the hospital to train staff on this new methodology.
Most people never become auto-didacts. Most auto-didacts still benefit from formal training because above average gross performance can mask subtle mistakes until the mistake becomes root cause for a significant error.
Under significant pressure (like a well-written dramatic fiction, but almost never IRL), most doctors will be willing to perform a procedure without formal training, but under normal conditions, they know it is not worth the additional risk.
I was fortunate to not only have a typing class in school, but also the only computer game my grandma had was Mavis Beacon Teaches Typing. Now I type for a living, so hey, I guess it must have paid off.
If you’re already a hunt and peck typer, your brain wants to look at the keyboard to confirm where the key is before you press it. When learning touch typing, you’ll want to shift your focus from the keyboard to the screen.
There are formal methodologies for learning where the keys are in relation to your fingers, but imo the most important thing is to not look at the keyboard. No matter what you end up typing, it’s pretty easy to find backspace and try again. Your eyes verify on the screen if your fingers are giving the correct output, and your fingers find their way eventually.
Many students did benefit from having their hands visually obscured from them when typing. If you find you keep looking at the keyboard then you might want to look into that.
Obviously you can’t lump them all into one category, but the majority of them seem to be willing to cause chaos on other instances for a laugh. Doesn’t sit right with me, so i blocked them
ActivityPub users need to be identified by some identifier in the URL, and Lemmy chose the user name to be that identifier. As a result, non-Latin usernames become… complicated. Just the right-to-left nature of scripts like Arabic alone would break UI design. Technically you could hex encode usernames and assume them to be UTF-8, but it’d be a massive pain that’ll undoubtedly break compatibility with other services.
You can use your display name to freely enter just about any name. Usernames are almost entirely irrelevant to Lemmy as far as I’m aware; I think they only matter in mentions (although that’s a choice as well, on the ActivityPub level there’s no need to do that). The display name should cover the “it looks really cool” component. As you’ve maybe seen already, you can include names, flags, and emoji in there as well!
With the current username system, there are more possible usernames than there are grains of sand on earth, per server. I don’t think we need a bigger username pool. We may need a better way to tag people, though, but that’s also true without different character sets.
ActivityPub users need to be identified by some identifier in the URL, and Lemmy chose the user name to be that identifier. As a result, non-Latin usernames become… complicated.
Sorry but this is just false. URIs can easily encode UTF-8 characters and it’s perfectly standard to do so via percent-encoding. Example: en.wikipedia.org/wiki/😂. Your browser will even automatically convert that 😂 into the appropriate percent-encoding and will even display the emoji in the address bar, even if that is not the “true” URI.
This is, if you ask me, an unnecessary limitation in Lemmy.
Using ASCII in URLs is simple and is less error prone than “supporting” unicode via percent encoding. It is also just a convention to use ASCII for usernames in many platforms. ASCII is also supported out of the box in major OSes while some unicode characters might not. What about impersonation? And what about people trying to type in the username of someone that uses unicode? It is not logical to use unicode in this case.
Punycode is not solving the same problem. Punycode solves Unicode in domain names. Percent encoding is for Unicode in URL paths. Lemmy only needs to worry about the paths, Punycode should be “supported” out of the box without any special handling
Link is detected without the emoji in my app. You might wanna hardcode the link as https://en.wikipedia.org/wiki/😂 [https://en.wikipedia.org/wiki/😂](https://en.wikipedia.org/wiki/😂)
Link detection is flaky as hell, especially for special characters. They rarely work reliably. URLs themselves don’t contain unicode. They use basic ASCII and anything beyond that needs to be encoded in some form. The link you posted isn’t a spec-compliant link, it only works because Lemmy apps and browsers are nice and do the conversion to the real URL for you. According to the spec:
When a new URI scheme defines a component that represents textual data consisting of characters from the Universal Character Set [UCS], the data should first be encoded as octets according to the UTF-8 character encoding [STD63]; then only those octets that do not correspond to characters in the unreserved set should be percent- encoded. For example, the character A would be represented as “A”, the character LATIN CAPITAL LETTER A WITH GRAVE would be represented as “%C3%80”, and the character KATAKANA LETTER A would be represented as “%E3%82%A2”.
If you use usernames as identifiers (which, again, are optional) like Lemmy does, databases and external entities will use the percentage URLs, not the readable ones. Unicode domains will have their xn-- form stored as well. It’s up to apps and browsers to decide those and turn them back into unicode. It’s not really relevant what apps and browsers show you when it comes to the technical interoperability of users.
ActivityPub itself has wide support for various languages, including having different names and content for different languages. The username (actually preferredUsername) is transmitted through JSON, which is by definition UTF-8, so most encodings in use today (not that weird Japanese one and that other Asian encoding that’s not UTF compatible) will Just Work™ assuming the necessary URL encoding and decoding logic is added in the right places.
I think Lemmy can be patched to accept unicode characters as usernames, as the current limitations in code and in the UI are just choices made during development. I don’t think it’ll add much, though.
kbin.life
Newest