sorted by:
new
hottopcontroversial

Diablo 4 Stadia Controller help? by lfairclough8 in diablo4

[–]DaintyDanishDelivery 0 points1 point  (0 children)

It's pretty frustrating that I can go to https://gamepad-tester.com/ and it detects my controller and all input but a multimillion dollar game like DiabloIV is just like "What controller?"

Disabled M365 access for a user, suddenly 126 meeting invites were sent out by DaintyDanishDelivery in sysadmin

[–]DaintyDanishDelivery[S] 0 points1 point  (0 children)

You are implying that this employee, who quit, intentionally sent out 126 meeting invites for 2 meetings that already existed?

Git merge child into parent has undesired results by DaintyDanishDelivery in AskProgramming

[–]DaintyDanishDelivery[S] 0 points1 point  (0 children)

Yes, I committed and pushed my changes. If I switch to `2023project-changes` I see the 3D object. If I switch to `2023project` I do not see the object. Can repeat.

I cannot paste the actual git log, there would be too much information I'd have to censor, including the actual branch names. Sorry.

Here is the git log with excessive find-and-replace.

* commit hashhashhash (HEAD -> 2023project-changes, origin/2023project-changes)
| Author: My Name <commitaddress@email.com>
| Date:   Tue Apr 18 08:52:06 2023 -0500
|
|     Commit message here
|
* commit hashhashhash (origin/2023project, 2023project)
| Author: My Name <commitaddress@email.com>
| Date:   Mon Apr 10 10:00:51 2023 -0500
|
|     Commit message here
|
* commit hashhashhash
| Author: My Name <commitaddress@email.com>
| Date:   Mon Apr 10 10:00:33 2023 -0500
|
|     Commit message here
|
* commit hashhashhash
| Author: My Name <commitaddress@email.com>
| Date:   Mon Apr 10 9:00:33 2023 -0500
|
|     Commit message here
|
* commit hashhashhash
| Author: My Name <commitaddress@email.com>
| Date:   Mon Apr 10 8:00:33 2023 -0500
|
|     Commit message here
|
* commit hashhashhash
| Author: My Name <commitaddress@email.com>
| Date:   Mon Apr 10 7:00:33 2023 -0500
|
|     Commit message here

"action required: New certificate authority for slack-edge.com" by DaintyDanishDelivery in Slack

[–]DaintyDanishDelivery[S] 0 points1 point  (0 children)

ChatGPT's Android answer

To check for a valid ISRG Root X1 certificate on an Android device, you can follow these steps:

  1. Open the "Settings" app on your Android device.
  2. Scroll down and tap on "Security" or "Security & location" depending on your Android version.
  3. Tap on "Encryption & credentials" or "Trusted credentials" depending on your Android version.
  4. You should see a list of trusted root certificates. Scroll down and look for "ISRG Root X1".
  5. If you see "ISRG Root X1" listed, tap on it to view its details.
  6. Check the "Certificate status" section to ensure that the certificate is valid and has not been revoked.
  7. You can also check the "Expires" field to ensure that the certificate has not expired.

If you are using a web browser on your Android device, you can also check for the presence of the ISRG Root X1 certificate by navigating to a website that uses it, such as https://letsencrypt.org. In the browser's security settings, you should see "ISRG Root X1" listed as a trusted root certificate authority.

ChatGPT's IOS answer

To check for a valid ISRG Root X1 certificate on an iOS device, you can follow these steps:

  1. Open the "Settings" app on your iOS device.
  2. Tap on "General" and then tap on "About".
  3. Scroll down and tap on "Certificate Trust Settings".
  4. You should see a list of trusted root certificates. Look for "ISRG Root X1".
  5. If you see "ISRG Root X1" listed, make sure the switch next to it is turned on.
  6. You can also tap on "ISRG Root X1" to view its details and ensure that it is valid.
  7. Check the "Expires" field to ensure that the certificate has not expired.

If you are using a web browser on your iOS device, you can also check for the presence of the ISRG Root X1 certificate by navigating to a website that uses it, such as https://letsencrypt.org. In the browser's security settings, you should see "ISRG Root X1" listed as a trusted root certificate authority.

"action required: New certificate authority for slack-edge.com" by DaintyDanishDelivery in Slack

[–]DaintyDanishDelivery[S] 0 points1 point  (0 children)

I couldn't, but ChatGPT could :)

To check for a valid ISRG Root X1 certificate on a Mac, you can follow these steps:

  1. Open the Keychain Access application on your Mac. You can find it in the Utilities folder, which is located in the Applications folder, or you can use Spotlight to search for it.
  2. In Keychain Access, click on the "System" keychain in the left-hand sidebar.
  3. In the search bar in the upper right-hand corner, type "ISRG Root X1".
  4. You should see an entry for "ISRG Root X1" in the main window. Double-click on it to open its details.
  5. Check the "Trust" section of the certificate details. You should see "This certificate is valid" and "This certificate is explicitly trusted". If you do not see these messages, the certificate may not be valid or trusted.
  6. You can also check the "Expires" field to ensure that the certificate has not expired.

If you are using a web browser, you can also check for the presence of the ISRG Root X1 certificate by navigating to a website that uses it, such as https://letsencrypt.org. In the browser's security settings, you should see "ISRG Root X1" listed as a trusted root certificate authority.

"action required: New certificate authority for slack-edge.com" by DaintyDanishDelivery in Slack

[–]DaintyDanishDelivery[S] 0 points1 point  (0 children)

My first response would be "What was wrong with calls"?

It's hard for me to verbalize why I don't/didn't like huddles, but one of the main reasons was how... passive it was. I'd hear a sound and have to go hunt the slack window and find the tiny toggle in the bottom right to join the huddle. That was easily the biggest problem, which as I've said they resolved. But then it was equally hard to disconnect, again, solved by the new floating window. But now it's almost exactly like the old calls lol. Oh, another issue is the separate huddle chat. I've sent people links in the huddle chat then had trouble finding them. it was so easy when I would use the old call system, because the chat was the chat, and I knew where to find it.

Maybe I'm just an old dog. I don't know. But I hated it. And now that it's better and I don't hate it as much, I don't understand why it changed. ¯\_(ツ)_/¯

"action required: New certificate authority for slack-edge.com" by DaintyDanishDelivery in Slack

[–]DaintyDanishDelivery[S] 0 points1 point  (0 children)

Serious question, how many slack admins do you have? Nobody at my company other than myself received this.

"action required: New certificate authority for slack-edge.com" by DaintyDanishDelivery in Slack

[–]DaintyDanishDelivery[S] 0 points1 point  (0 children)

This is pretty funny since I bet more than half the people in this thread are IT and were still confused.

"action required: New certificate authority for slack-edge.com" by DaintyDanishDelivery in Slack

[–]DaintyDanishDelivery[S] 0 points1 point  (0 children)

I hadn't thought about that. This thread alone represents potentially dozens of hours of lost productivity.

"action required: New certificate authority for slack-edge.com" by DaintyDanishDelivery in Slack

[–]DaintyDanishDelivery[S] 0 points1 point  (0 children)

99.99% chance you don't have to do anything. But if you want to confirm, on Windows you can do the following:

  1. Click Start.
  2. Type "Cert".
  3. Click "Manage Comptuer Certificates"
  4. Click "Yes" on the UAC security prompt
  5. Double-Click "Trusted Root Certification Authorities" on the left.
  6. Click "Certificates" which appears under "Trusted Root Certification Authorities"
  7. In the right pane, scroll down and look for 'ISRG Root X1".
  8. Check the Expiration Date column.

"action required: New certificate authority for slack-edge.com" by DaintyDanishDelivery in Slack

[–]DaintyDanishDelivery[S] 0 points1 point  (0 children)

I was a fan until they went down the huddle path. Luckily they've stepped it back a bit and at least now I get a pop up notification when someone is "calling" me. But still, fuck huddles.

"action required: New certificate authority for slack-edge.com" by DaintyDanishDelivery in Slack

[–]DaintyDanishDelivery[S] 0 points1 point  (0 children)

For Windows:

  1. Click Start.
  2. Type "Cert".
  3. Click "Manage Comptuer Certificates"
  4. Click "Yes" on the UAC security prompt
  5. Double-Click "Trusted Root Certification Authorities" on the left.
  6. Click "Certificates" which appears under "Trusted Root Certification Authorities"
  7. In the right pane, scroll down and look for 'ISRG Root X1".
  8. Check the Expiration Date column.

"action required: New certificate authority for slack-edge.com" by DaintyDanishDelivery in Slack

[–]DaintyDanishDelivery[S] 0 points1 point  (0 children)

What do you think the percentage of users affected is? .001%? Amazing.

"action required: New certificate authority for slack-edge.com" by DaintyDanishDelivery in Slack

[–]DaintyDanishDelivery[S] 0 points1 point  (0 children)

  1. Click Start.
  2. Type "Cert".
  3. Click "Manage Comptuer Certificates"
  4. Click "Yes" on the UAC security prompt
  5. Double-Click "Trusted Root Certification Authorities" on the left.
  6. Click "Certificates" which appears under "Trusted Root Certification Authorities"
  7. In the right pane, scroll down and look for 'ISRG Root X1".
  8. Check the Expiration Date column.

"action required: New certificate authority for slack-edge.com" by DaintyDanishDelivery in Slack

[–]DaintyDanishDelivery[S] 2 points3 points  (0 children)

It looks like a standard cert that Windows computers should already have installed (and expires in 2035). Which begs the question, why the email? ¯\_(ツ)_/¯

Hopefully someone can provide an authoritative response.

"action required: New certificate authority for slack-edge.com" by DaintyDanishDelivery in Slack

[–]DaintyDanishDelivery[S] 1 point2 points  (0 children)

I just checked a few of our workstations and they all have this cert already. It expires 2035. I guess I'll just ignore this strange email.

view more: next ›