Severity: 8192
Message: Return type of CI_Session_files_driver::open($save_path, $name) should either be compatible with SessionHandlerInterface::open(string $path, string $name): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
Filename: drivers/Session_files_driver.php
Line Number: 132
Backtrace:
File: /home/thetechminers/public_html/application/controllers/Blog.php
Line: 8
Function: __construct
File: /home/thetechminers/public_html/index.php
Line: 321
Function: require_once
Severity: 8192
Message: Return type of CI_Session_files_driver::close() should either be compatible with SessionHandlerInterface::close(): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
Filename: drivers/Session_files_driver.php
Line Number: 290
Backtrace:
File: /home/thetechminers/public_html/application/controllers/Blog.php
Line: 8
Function: __construct
File: /home/thetechminers/public_html/index.php
Line: 321
Function: require_once
Severity: 8192
Message: Return type of CI_Session_files_driver::read($session_id) should either be compatible with SessionHandlerInterface::read(string $id): string|false, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
Filename: drivers/Session_files_driver.php
Line Number: 164
Backtrace:
File: /home/thetechminers/public_html/application/controllers/Blog.php
Line: 8
Function: __construct
File: /home/thetechminers/public_html/index.php
Line: 321
Function: require_once
Severity: 8192
Message: Return type of CI_Session_files_driver::write($session_id, $session_data) should either be compatible with SessionHandlerInterface::write(string $id, string $data): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
Filename: drivers/Session_files_driver.php
Line Number: 233
Backtrace:
File: /home/thetechminers/public_html/application/controllers/Blog.php
Line: 8
Function: __construct
File: /home/thetechminers/public_html/index.php
Line: 321
Function: require_once
Severity: 8192
Message: Return type of CI_Session_files_driver::destroy($session_id) should either be compatible with SessionHandlerInterface::destroy(string $id): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
Filename: drivers/Session_files_driver.php
Line Number: 313
Backtrace:
File: /home/thetechminers/public_html/application/controllers/Blog.php
Line: 8
Function: __construct
File: /home/thetechminers/public_html/index.php
Line: 321
Function: require_once
Severity: 8192
Message: Return type of CI_Session_files_driver::gc($maxlifetime) should either be compatible with SessionHandlerInterface::gc(int $max_lifetime): int|false, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
Filename: drivers/Session_files_driver.php
Line Number: 354
Backtrace:
File: /home/thetechminers/public_html/application/controllers/Blog.php
Line: 8
Function: __construct
File: /home/thetechminers/public_html/index.php
Line: 321
Function: require_once
Severity: Warning
Message: ini_set(): Session ini settings cannot be changed after headers have already been sent
Filename: Session/Session.php
Line Number: 284
Backtrace:
File: /home/thetechminers/public_html/application/controllers/Blog.php
Line: 8
Function: __construct
File: /home/thetechminers/public_html/index.php
Line: 321
Function: require_once
Severity: Warning
Message: session_set_cookie_params(): Session cookie parameters cannot be changed after headers have already been sent
Filename: Session/Session.php
Line Number: 296
Backtrace:
File: /home/thetechminers/public_html/application/controllers/Blog.php
Line: 8
Function: __construct
File: /home/thetechminers/public_html/index.php
Line: 321
Function: require_once
Severity: Warning
Message: ini_set(): Session ini settings cannot be changed after headers have already been sent
Filename: Session/Session.php
Line Number: 306
Backtrace:
File: /home/thetechminers/public_html/application/controllers/Blog.php
Line: 8
Function: __construct
File: /home/thetechminers/public_html/index.php
Line: 321
Function: require_once
Severity: Warning
Message: ini_set(): Session ini settings cannot be changed after headers have already been sent
Filename: Session/Session.php
Line Number: 316
Backtrace:
File: /home/thetechminers/public_html/application/controllers/Blog.php
Line: 8
Function: __construct
File: /home/thetechminers/public_html/index.php
Line: 321
Function: require_once
Severity: Warning
Message: ini_set(): Session ini settings cannot be changed after headers have already been sent
Filename: Session/Session.php
Line Number: 317
Backtrace:
File: /home/thetechminers/public_html/application/controllers/Blog.php
Line: 8
Function: __construct
File: /home/thetechminers/public_html/index.php
Line: 321
Function: require_once
Severity: Warning
Message: ini_set(): Session ini settings cannot be changed after headers have already been sent
Filename: Session/Session.php
Line Number: 318
Backtrace:
File: /home/thetechminers/public_html/application/controllers/Blog.php
Line: 8
Function: __construct
File: /home/thetechminers/public_html/index.php
Line: 321
Function: require_once
Severity: Warning
Message: ini_set(): Session ini settings cannot be changed after headers have already been sent
Filename: Session/Session.php
Line Number: 319
Backtrace:
File: /home/thetechminers/public_html/application/controllers/Blog.php
Line: 8
Function: __construct
File: /home/thetechminers/public_html/index.php
Line: 321
Function: require_once
Severity: Warning
Message: ini_set(): Session ini settings cannot be changed after headers have already been sent
Filename: Session/Session.php
Line Number: 377
Backtrace:
File: /home/thetechminers/public_html/application/controllers/Blog.php
Line: 8
Function: __construct
File: /home/thetechminers/public_html/index.php
Line: 321
Function: require_once
Severity: Warning
Message: session_set_save_handler(): Session save handler cannot be changed after headers have already been sent
Filename: Session/Session.php
Line Number: 110
Backtrace:
File: /home/thetechminers/public_html/application/controllers/Blog.php
Line: 8
Function: __construct
File: /home/thetechminers/public_html/index.php
Line: 321
Function: require_once
Severity: Warning
Message: session_start(): Session cannot be started after headers have already been sent
Filename: Session/Session.php
Line Number: 143
Backtrace:
File: /home/thetechminers/public_html/application/controllers/Blog.php
Line: 8
Function: __construct
File: /home/thetechminers/public_html/index.php
Line: 321
Function: require_once
After reading Facebook CEO Mark Zuckerberg's testimony, and viewing some video clips of his appearances before Senate and House committee hearings last week, it became very clear to me -- and I expect many in Congress (these were unprecedented events, and it's an election year) -- that social media companies need to be regulated.
However, I think this is only a step in the path that governments -- and I do mean more than the U.S. -- will take to ensure their effectiveness and protect their people. I'm not suggesting the U.S. Congress, whose members currently appear to be woefully out of step, could run these companies better.
What I can see easily, though, is that as technology evolves, the need for national security will drive Congress to take control of the digital identities of citizens, both to protect the people better and to ensure that the government and country survive.
If we think in terms of ordnance, the nuclear bomb is the most powerful, and no government would be willing to allow a company to amass any of those things -- let alone enough to overthrow the government. Yet all a bomb can do is intimidate and destroy. It doesn't really control.
Were a firm to acquire a critical mass of nuclear weapons, it is likely more than one government would work inordinately hard to remove the threat to ensure the sovereignty of that government. (I'm thinking there would be a crater where that company used to be.)
What the various world governments are coming around to understanding is that deep data on individuals can be far more powerful than a bomb. Deep data can be used to overthrow governments without the government even knowing it is at risk. The citizens are the real power behind a government. If you can control them, you effectively can control a nation -- the government becomes both redundant and subordinate.
We are currently dealing with the fact that Facebook, which clearly now has that power, sold it to a third party, potentially aiding a foreign government's efforts to control a national U.S. election. Attempting to influence an election isn't new -- governments have done it to one other for centuries. However, this may very well be the first time that a large company has had this power and made it available to a hostile nation for use against its own country.
This kind of control and really bad decision making used to exist only in the public sector. Based on investigations in the U.S. and in the EU, the public sector appears to be coming around, slowly, to the idea that something on a national level -- if not world level -- needs to be done.
It is interesting to note that traditional media outlets, which were hurt massively when both Google and Facebook emerged, seem to be on the front lines in this effort.
Current discussions suggest the plan is to do something far less severe than that -- but do realize that if you or I were facing this situation after committing a crime, the fact that we couldn't pay the fine likely would be our problem to solve.
I doubt the government actually will take over Facebook at this point. However, the lack of control over user data and the fact that a second company apparently has misused it suggest that we probably haven't seen the last of these disclosures. (You may recall how the information about the extent of the Yahoo breaches kept getting worse over time.) It's possible that the Facebook scandal still could escalate to a level even Facebook couldn't survive.
I'm not expecting a near-term fix, but what I do foresee is that with 44 senators attending the Zuckerberg hearing, "fixing Facebook," or possibly eventually nationalizing it, will become a common political goal. That goal should mature to action around the time of the next presidential election -- thus the five- to 10-year range of my prediction.