![](https://lemmy.world/pictrs/image/8d1d3e42-ea60-490a-a485-c62b13c101dd.jpeg)
![](https://programming.dev/pictrs/image/170721ad-9010-470f-a4a4-ead95f51f13b.png)
It’s the API’s job to validate it either way. As it does that job, it may as well parse the string as an integer.
No gods, no masters.
It’s the API’s job to validate it either way. As it does that job, it may as well parse the string as an integer.
I’m not a solipsist.
I fucking hate timezones. Whatever it is, I’d rather read the current clock as 4 a.m. even if it’s noon than have timezones.
Squashing
The
s
“squash” command is where we see the true utility of rebase. Squash allows you to specify which commits you want to merge into the previous commits. This is what enables a “clean history.” During rebase playback, Git will execute the specified rebase command for each commit. In the case of squash commits, Git will open your configured text editor and prompt to combine the specified commit messages. This entire process can be visualized as follows:
Note that the commits modified with a rebase command have a different ID than either of the original commits. Commits marked with pick will have a new ID if the previous commits have been rewritten.
https://www.atlassian.com/git/tutorials/rewriting-history
You can also amend for a softer approach, which works better if you don’t push to remote after every commit.
The
git commit --amend
command is a convenient way to modify the most recent commit. It lets you combine staged changes with the previous commit instead of creating an entirely new commit. It can also be used to simply edit the previous commit message without changing its snapshot. But, amending does not just alter the most recent commit, it replaces it entirely, meaning the amended commit will be a new entity with its own ref. To Git, it will look like a brand new commit, which is visualized with an asterisk (*) in the diagram below.
You can keep amending commits and creating more chunky and meaningful ones in an incremental way. Think of it as converting baby steps into an adult step.
Who would use that kind of type coercion? Who? I want to see his face.
there’s no /c/veganpizza yet, but there is /r/veganpizza
There are too many blogs and posts.
simulAIcrum
I mean integrated directly into the interface of the apps. Example: they have an “Editor” tab for Word that can analyze and get into the document directly. I expect that this will be where the ChatGPT tools will be implemented. Or is there some professional version of ChatGPT that does that already? I have only tested the free one.
Wait, copilot and ChatGPT use are skills? Isn’t that a bit like how using a phone is a skill?
It’s about at the same level as “Microsoft Office” as a skill. They’re probably working on embedding ChatGPT and DALL-E in that suite. I’ve actually asked ChatGPT for some tips on using advanced features that I didn’t know about and it worked nicely.
What would even be the design solution without massive empty space? Add a lot of columns? Make the long content horizontal instead of vertical?
This is excellent
No. Users should be forced to install hundreds of apps, with two thirds of apps running simultaneously. And if they don’t have memory left on the device for that, they should uninstall apps and reinstall them when necessary.
/s
that’s some PTSD comment right there, I’m getting flashbacks.
I’m guessing that it’s a way for them to test if ads have been loaded after initial scripts have run, but I’m not going to dig into the code.
Honestly, the whole ads thing is missing the point. If you desired a public video hosting platform, that needs to be a tax-funded commons. Video hosting and streaming is very expensive. Similarly, users should be donating to keep Lemmy going:
Ah, yes, let’s have thousands of specialized apps, each with uniquely expiring dependencies and vulnerabilities, instead of one browser that can work with apps that are standardized for OSS, UI, accessibility, performance, inspection by humans and machines, and security.
Currently, it is likely that just your session cookie was stolen, with instance admins being targeted specifically by checking for navAdmin, an HTML element only instance admins had. I do not believe this to affect users across instances, but I have yet to confirm this.
Probably because the hackers used some http request to get the data and didn’t want to wade through thousands of rows of JWT strings.
https://www.geeksforgeeks.org/difference-between-put-and-patch-request/