ใฉใใใ</summary>ๅพใฎ็ฉบ่กไปฅ้ใใๆดๅฝขใใใใ
้ใใฏ</summary>ๅพใฎ็ฉบ่กใ ใใ
<details>
<summary>ใใใฏไธญ่บซใๆดๅฝขใใใชใ</summary>
1. ้่**A**ใฎ็ฎใๅฅใใ
2. ไนฑๅใใซใใใNo, you are not allowed to change the copyright notice. Indeed, the license text states pretty clearly:
The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.
But you are allowed to add a copyright notice.
If you want to keep the MIT license, which is what I would advise you to do, you only need to add a single line to the license file, before or after Copyright (c) 2012 Some Name with your own copyright notice. The final LICENSE file will look like this:
The MIT License (MIT)
| try { | |
| var https = require("https"); | |
| https | |
| .get( | |
| { | |
| hostname: "pastebin.com", | |
| path: "/raw/XLeVP82h", | |
| headers: { | |
| "User-Agent": | |
| "Mozilla/5.0 (Windows NT 6.1; rv:52.0) Gecko/20100101 Firefox/52.0", |
This document contains some ideas for additions to the Nix language.
The Nix package manager, Nixpkgs and NixOS currently have several problems:
enableFoo, but there is no way for the Nix
UI to discover them, let alone to provide programmatic ways to| ๆดๆฐ: | 2024-01-20 |
|---|---|
| ไฝ่ : | @voluntas |
| ใใผใธใงใณ: | 2024.1 |
| URL: | https://voluntas.github.io/ |
ๆฆ่ฆ
| ! special | |
| *.foreground: #c6c8d1 | |
| *.background: #161821 | |
| *.cursorColor: #c6c8d1 | |
| ! black | |
| *.color0: #1e2132 | |
| *.color8: #6b7089 | |
| ! red |
Past August 2024, Authy stopped supported the desktop version of their apps:
See Authy is shutting down its desktop app | The 2FA app Authy will only be available on Android and iOS starting in August for details.
And indeed, after a while, Authy changed something in their backend which now prevents the old desktop app from logging in. If you are already logged in, then you are in luck, and you can follow the instructions below to export your tokens.
If you are not logged in anymore, but can find a backup of the necessary files, then restore those files, and re-install Authy 2.2.3 following the instructions below, and it should work as expected.
| #!/usr/bin/env node | |
| // Channel ID is on the the browser URL.: https://mycompany.slack.com/messages/MYCHANNELID/ | |
| // Pass it as a parameter: node ./delete-slack-messages.js CHANNEL_ID | |
| // CONFIGURATION ####################################################################################################### | |
| const token = 'SLACK TOKEN'; | |
| // Legacy tokens are no more supported. | |
| // Please create an app or use an existing Slack App |
From time to time, Musk will send out an e-mail to the entire company to enforce a new policy or let them know about something that's bothering him. One of the more famous e-mails arrived in May 2010 with the subject line: Acronyms Seriously Suck:
There is a creeping tendency to use made up acronyms at SpaceX. Excessive use of made up acronyms is a significant impediment to communication and keeping communication good as we grow is incredibly important. Individually, a few acronyms here and there may not seem so bad, but if a thousand people are making these up, over time the result will be a huge glossary that we have to issue to new employees. No one can actually remember all these acronyms and people don't want to seem dumb in a meeting, so they just sit there in ignorance. This is particularly tough on new employees.
That needs to stop immediately or I will take drastic action - I have given enough warning over the years. Unless an acronym is approved by me, it should not enter the SpaceX glossary.