Vigge93 @ Vigge93 @lemmy.world

Posts

0

Comments

49

Joined

2 yr. ago

Emily the engineer - https://youtube.com/@emilytheengineer - Does fun projects with 3d-printing

Evan and Katelyn - https://youtube.com/@evanandkatelyn - Does a lot of DIY/arts&crafts

Nerdforge - https://youtube.com/@nerdforge - Maker/Arts&Crafts, does a lot fantasy based stuff

Physics girl - https://youtube.com/@physicsgirl - Physics stuff, she has struggled with health issues the last couple of years, but her old stuff is still very good

Laura Kampf - https://youtube.com/@laurakampf - Maker, does a lot of woodworking and upcycling

Thanks! Don't know how I missed the Authentik docs for this.

How did you set up Jellyfin with Authentik? Are you using SSO or is it only through LDAP?

That's why you always have the same number of digits. 01 < 05 < 10

That's when you get into more of the nuance with tokenization. It's not a simple lookup table, and the AI does not have access to the original definitions of the tokens. Also, tokens do not map 1:1 onto words, and a word might be broken into several tokens. For example "There's" might be broken into "There" + "'s", and "strawberry" might be broken into "straw" + "berry".

The reason we often simplify it as token = words is that it is the case for most of the common words.

Each word gets converted to a number before it is processed, so asking how many "how many r are there in strawberry" could be converted to "how many 7 are there in 13", for example.

(Very simplified)

I think it does make sense, it's a "did this loop exit naturally? If so, do x". This makes a lot of sense if you, for example, have a loop that checks a condition and breaks if that condition is met, e.g. finding the next item in a list. This allows for the else statement to set some default value to indicate that no match was found.

Imo, the feature can be very useful under certain circumstances, but the syntax is very confusing, and thus it's almost never a good idea to actually use it in code, since it decreases readability a lot for people not intimately familiar with the language.

Edit: Now, this is just guessing, but what I assume happens under the hood is that the else statement is executed when the StopIteration exception is recieved, which happens when next() is called on an exhausted iterator (either empty or fully consumed)

Your point about it not running when there is nothing to iterate over is incorrect. The else-statement runs when the iterator is exhausted; if the iterator empty, it is exhausted immediately and the else-statement is executed.

Which makes it easier to keep up the momentum

The answer says "any character" not "any characters", so it is still correct.

You are ignoring ALL of the of the positive applications of AI from several decades of development, and only focusing on the negative aspects of generative AI.

Here is a non-exhaustive list of some applications:

• In healthcare as a tool for earlier detection and prevention of certain diseases
• For anomaly detection in intrusion detection system, protecting web servers
• Disaster relief for identifying the affected areas and aiding in planning the rescue effort
• Fall detection in e.g. phones and smartwatches that can alert medical services, especially useful for the elderly.
• Various forecasting applications that can help plan e.g. production to reduce waste. Etc...

There have even been a lot of good applications of generative AI, e.g. in production, especially for construction, where a generative AI can the functionally same product but with less material, while still maintaining the strength. This reduces cost of manufacturing, and also the environmental impact due to the reduced material usage.

Does AI have its problems? Sure. Is generative AI being misused and abused? Definitely. But just because some applications are useless it doesn't mean that the whole field is.

A hammer can be used to murder someone, that does not mean that all hammers are murder weapons.

I disagree, and would argue that both are about equally frequent. For example, my phone shows °C in the weather widget, while the weather app only uses °. That does not change the fact that the actual unit is °C, and that would not change even if the whole world switched away from °F, and your original comment about the display having °C implying that °F still exists is therefore incorrect.

No, even if you only had one unit for a physical quantity, you would still need to specify that unit to know which physical quantity you are describing. E.g. "That object over there is 15" vs "That object over there is 15 kg".

The symbol for temperature, measured in Celsius, is "°C". It's atomic and can't be separated, since that would result in °, which represents the angle of something, not the temperature, and C, which is the symbol for Coulomb, which measures electric charge.

If it's like the system in Sweden, it's actually ~$400 straight up benefit, and ~$800 in a very favourable (optional) loan with very low interest that is paid back over 25 years.

The source paper is available online, is published in a peer reviewed journal, and has over 600 citations. I'm inclined to believe it.

That's why these systems should never be used as the sole decision makers, but instead work as a tool to help the professionals make better decisions.

Keep the human in the loop!

While there might be some truth to that, I don't think MS 365 would qualify as "developed for the government."

1. I imagine that the company would have the burden of proof that any of these criteria are fulfilled.
2. Third-party rights most likely refers to the use of third-party libraries, where the source code for those isn't open source, and therefore can't be disclosed, since they aren't part of the government contract. Security concerns are probably things along the line of "Making this code open source would disclose classified information about our military capabilities" and such.

Switzerland are very good bureaucracy and I trust that they know how to make policies that actually stick.

As long as it's maintained. Wrong documentation can often be worse than no documentation.

I was making that reference