You'd download a mod that contained installation instructions like the above, fire up your code editor of choice and then would manually change the source code of phpBB.
Later on, automated mod installers started being somewhat reliable, but especially if you had multiple mods touching similar parts of the codebase you had to learn how to adjust the instructions.
I don't really miss these times, but I did learn a lot about PHP through it.
That's sort of similar to how modding in the Witcher 3 works. The scripting is distributed with the game itself and compiled during launch, which is great in terms of how much stuff is easily moddable, but a complete nightmare in terms of how the mods have to deal with conflicts. I had a double take when I saw that one of the common tools people use to deal with it literally bundles in kdiff3 and opens it up with merge conflicts to solve.
While not my technical first, it was the first of real consequence for me as well.
And then I got so frustrated that I went to write my own forum software! And showed it to my friend, who promptly showed me how badly I understood security by posting as me.
No no, not "mods". The phpbb people were always weirdly militant about calling them them MODS, uppercase.
Why, I'm not sure, because it's not an acronym. Eventually they decided to start calling them Extensions, which is probably a more apt term. Or maybe a more APT term.
At the discounted rates, upgrading from 3 Flash to 3.7 Flash is finally reasonable.
In my evals 3.6 Flash (pre price change) was usually a bit more token efficient than 3 Flash, so I‘m expecting same or even lower cost-per-task on 3.7.
The timeline OpenAI wants to present looks like this to me:
- Leaving employee (LE) needs a USB stick to copy data off their Mac to give to their Manager (MA) so someone at Apple still has access
- After LE left, MA has access to LE Mac and iCloud to still access some data
- At some point, LE asks MA to sign out off LE's iMessage account on that Mac as they suspect they'll get OpenAI-related messages soon and don't want Apple/MA to see them
- Eventually, MA deletes the Apple files in LE's iCloud
Granted, Apple does do this weird thing where you're invited to use your personal iCloud (/Apple) account for work-related things (I suspect because they're just bad at supporting multiple accounts simultaneously). As part of the deal, your iCloud account gets upgraded during your employment.
But they're also quite explicit and repeat the directive (including during the exit interview) about removing Apple files from your account when you leave, and logging out of iCloud from the Apple devices you leave behind.
Also:
> At some point, LE asks MA to sign out off LE's iMessage account
You can sign out remotely, so this would've been stupid of everyone involved.
Then again, this whole situation demonstrates a level of stupidity from supposedly competent people that I wish I could say was unbelievable. Add "Making a public post about a topic under litigation" under that category too.
From what I saw, it's been leapfrogging for the past few weeks. Even if Apple is currently behind them, I don't think it's particularly fair to say it's "fallen to" them.
Funny to hear that even Apple themself struggle with that. In the past it's been such a PITA for us to decide whether employees can use private account or shall use company apple ids. As we have a pretty lax policy, most of them use their private accounts to have iCloud sync or to simply access purchased apps but having a simple way for dual account usage would be too easy i guess.
I wonder how deep this integration goes. I’d never want to use my personal accounts for proprietary work items. Just seems like a recipe for disaster. Also, removing a latop from iCloud doesn’t delete the imessage data already on the device.
I am actually confused why creating an email john.doe@apple.com and separated employees work only iCloud on the email is such a problem and they want people to use personal iCloud? Not even corporate stuck in 90s does that.
You'd download a mod that contained installation instructions like the above, fire up your code editor of choice and then would manually change the source code of phpBB.
Later on, automated mod installers started being somewhat reliable, but especially if you had multiple mods touching similar parts of the codebase you had to learn how to adjust the instructions.
I don't really miss these times, but I did learn a lot about PHP through it.