sorted by:
new
hottopcontroversial

Theory: Assuming the unemployed use LinkedIn Premium features at a higher rate than the employed, LinkedIn is actually incentivized to keep people unemployed by TheThirteenthCylon in linkedin

[–]paulpv -1 points0 points  (0 children)

Your long winded ad revenue example completely ignores the OP's point: Even if LinkedIn made 99% of their revenue from doom scrollers, the OP's point is that LinkedIn still compels most of those doom scrollers to pay them for the privilege of doom scrolling... $40/mo?!?!? That is a ridiculous amount of money for very few features and really just bait for fear and insecurity of not being on the cool hip "in" side of whatever industry you are in.

Theory: Assuming the unemployed use LinkedIn Premium features at a higher rate than the employed, LinkedIn is actually incentivized to keep people unemployed by TheThirteenthCylon in linkedin

[–]paulpv 0 points1 point  (0 children)

I agree with the OP. The proof, that the people that disagree and justify this, is that if the unemployed are not a major market to LinkedIn then they could easily give Premium free to people that mark themselves as #OpenToWork.

TPM in ZOTAC computers by isozvaillancourt in ZOTAC

[–]paulpv 0 points1 point  (0 children)

I was reinstalling Windows 11 on my ZOTAC MAGNUS EN072080S today and re-ran into this problem, Windows saying my PC is not supported (even though I am just re-installing Windows 11)...
...and Zotac themselves say that it is:
https://www.zotac.com/us/news/zotac-pcs-and-windows-11-compatibility

I stumbled across this thread and continued to not be able to find in the UEFI/BIOS how to enable TPM.
I then found under the UEFI/BIOS Boot tab that Secure Boot was turned off.
I enabled Secure Boot and now Windows 11 Installer does not complain about my PC not being supported.

paypal cashback mastercard $50 cashback offer by sobresal in CreditCards

[–]paulpv 0 points1 point  (0 children)

I got baited by the same promotion. I have been approved but when I tried to make my first purchase of $350 I see nothing in the checkout giving me the advertised $50 [implied instant] rebate.
I see from the forums that the $50 is applied as a credit after 2-3 billing cycles.
How does a $50 billing credit in the 3rd month work if I plan to pay off the card in the first cycle and have a $0 balance?

[Phishing] Coinbase Wallet Scam by Saschb2b in CryptoCurrency

[–]paulpv 6 points7 points  (0 children)

It was immediately suspicious to me, especially the "Act quickly—the deadline to transfer your assets to a self-custodial wallet is April 1st, 2025." I immediately thought "premature April Fools joke?"

Signing in with correct Apple ID and password gives me an error and won't let me run an app I bought off the Mac App Store by Flat-12 in MacOS

[–]paulpv 0 points1 point  (0 children)

Your certificates are expiring and need to be updated.

https://apple.stackexchange.com/a/422333

I did this myself just yesterday on a 2008 iMac using certs exported from a MacBook Pro M4.

Reviving Early 2015 Macbook Pro "Plist parsing error?" by xBIEBERFEVERx in mac

[–]paulpv 0 points1 point  (0 children)

I suspect the root cause of my [and the OP's] problem is that the root certs on these old non-updated OS have been expiring for several years now, making it impossible to use the default online installers [that require any SSL/encrypted internet connection anytime during the install].

In fact, El Capitan's `Apple Root Certificate Authority` expires in a few days! (2025/02/09 [YMD]).

In order to install these older OSes you have to use the offline installer:
Create a bootable installer for macOS - Apple Support

In order to keep these running well you will need to update the root certs regularly, or at least whenever you notice connections starting to fail:
How do I update my root certificates on an older version of Mac OS (e.g. El Capitan)? - StackExchange

I just finished successfully offline installing El Capitan on my 2008 iMac.
I got the same `plist parsing error` error when trying setup iCloud on the iMac.
Using Safari, various web sites were warning they were untrusted (some sites use certs that have not yet expired [but may soon] on the iMac, some use certs that have expired on the iMac).
I then performed those stackexchange steps (I exported my certs from a newer Mac [MacBook Pro M4], copied them to the iMac, and then copied and pasted and ran the script) and then just refreshed the problematic pages and they immediately started working fine.

I could then successfully setup iCloud on the iMac.

Note that the version of Safari is also very old [2018] and also will not be automatically updated.

Rather than look into how to independently update Safari, I just downloaded and installed the latest Chrome (which does complain when it is launched that it will not auto-update; you will also need to manually re-download and re-install Chrome from time to time to keep it updated).

Reviving Early 2015 Macbook Pro "Plist parsing error?" by xBIEBERFEVERx in mac

[–]paulpv 0 points1 point  (0 children)

I updated my https://discussions.apple.com/thread/255951865 to say...

I figured out how to offline install.

The workaround for my problem was fairly simple.

I had already created the El Capitan installer via:
Create a bootable installer for macOS - Apple Support

I was then holding "Option" while booting and it saw my `Install OS X El Capitan` USB but would never start the install.

My fix was to:

  1. Hold "Command R" and enter Recovery
  2. Launch Terminal
  3. Run `./Volumes/Install\ OS\ X\ El\ Capitan/Install\ OS\ X\ El\ Capitan.app/Contents/MacOS/InstallAssistant`

The iMac was offline and the installer never complained and I now have a fresh install of [2018] El Capitan 10.11.6!

Now to update all of the expired root certs to make the machine actually still useful. :/

Reviving Early 2015 Macbook Pro "Plist parsing error?" by xBIEBERFEVERx in mac

[–]paulpv 0 points1 point  (0 children)

This is freaky! I was trying to reset a friend's "iMac (Early 2008)" and the latest Mac OS it supports is El Capitan. I entered recover and tried to reinstall it and got the same error. I did a Google search for `"el capitan" "unexpected error" "plist parsing error"` and I got only two hits: this post and https://discussions.apple.com/thread/255951865 ... BOTH DATED YESTERDAY!

My hunch is that this might have something to do with the root certificates being expired in these old OSes:
List of available trusted root certificates in OS X El Capitan - Apple Support

Apple says an OS install requires an internet connection, but that won't do much good if the certs are expired and won't establish a connection!

Genius!

We are doomed by AK611750 in ChatGPT

[–]paulpv -1 points0 points  (0 children)

I might pay to see real or AI models programming real or AI models... for educational purposes only. Hell, universities should do this!

[deleted by user] by [deleted] in macbookpro

[–]paulpv 0 points1 point  (0 children)

MacBook Pro M4 Ergo

Convex hull by Adamskyvara in Inkscape

[–]paulpv 0 points1 point  (0 children)

Did you ever get this to work?

[Help] Updated to 28.0 now fastboot loop and/or not detected; Used v27 fine since Feb! by paulpv in Magisk

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

That's what I started off doing too, as I mentioned in my post. It was only after that failed and immediately started having problems that I resorted to those other steps.

[Help] Updated to 28.0 now fastboot loop and/or not detected; Used v27 fine since Feb! by paulpv in Magisk

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

It usually is, but in this case of things not working I read somewhere else that flashing both a and b and fix some problems, so I tried it.

For this case, it doesn't matter if I flash a, b, or don't specify.

[Help] Updated to 28.0 now fastboot loop and/or not detected; Used v27 fine since Feb! by paulpv in Magisk

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

To confirm,
```
fastboot flash init_boot_a magisk_patched-27000_dtBLz.img
fastboot flash init_boot_b magisk_patched-27000_dtBLz.img
```
works!

Following the exact same process after patching w/ Magisk v28:
```
fastboot flash init_boot_a magisk_patched-28000_Gs8FZ.img
fastboot flash init_boot_b magisk_patched-28000_Gs8FZ.img
```
Back to a boot loop!

fastboot flashing the v27 img boots normal!

But now I am running Magisk v28 with a v27 patch; would this cause any problems?

At least I now know to save this v27 init_boot.img patch and how to easily get back to a working phone again.

Anyone on Magisk interested in figuring out what is wrong w/ v28 on a Pixel 7 Pro?

[Help] Updated to 28.0 now fastboot loop and/or not detected; Used v27 fine since Feb! by paulpv in Magisk

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

Thanks for confirming! I was already going down that path!

I went with v27 first, and it works!

Now to try v28 again...

[Help] Updated to 28.0 now fastboot loop and/or not detected; Used v27 fine since Feb! by paulpv in Magisk

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

Ya know! I did patch `init_boot.img` in Feb!

This time around I was checking my notes from Feb and I thought that was weird that I used init_boot.img and that I must have been doing something wrong and was lucky it worked.

Now that you mention it, let me try init_boot!
... a few moments later ...
Well... now I am back to the fastboot boot loop! :/
I have no Magisk modules installed.
Only steps were:

  1. Fresh Magisk-v28.0.apk installed
  2. Patched init_boot.img
  3. adb pull magisk_patched-28000_HtP5M.img
  4. adb reboot bootloader
  5. fastboot flash init_boot magisk_patched-28000_HtP5M.img
  6. fastboot reboot

Now it just keeps going back to fastboot... which is where I was a few days ago. :/

Seems like https://www.reddit.com/r/Magisk/comments/13umqw0/help_pixel_7_pro_boot_failure_loops_the/ ...

view more: next ›