@arch3rtemp said in Opera Linux browser - h.264 support (through x264 open source codec):

There are no chromium codecs in Ubuntu repositories anymore, neither in Snap

Still available in Snap as "chromium-ffmpeg". For me, it doesn't automatically work, but you can link directly from the snap and it works fine.

sudo mkdir -p /usr/lib/x86_64-linux-gnu/opera/lib_extra && \
sudo ln -fst /usr/lib/x86_64-linux-gnu/opera/lib_extra/ /snap/chromium-ffmpeg/current/chromium-ffmpeg-92972/chromium-ffmpeg/libffmpeg.so && \
echo -e "\n\nLink successful, restart Opera and it should work."

According to the docs, when you use a separate password for synchronization (instead of using your Opera account), ALL data including bookmarks and browsing history is encrypted.

However, if I go to sync.opera.com from a different browser and log in using only my Opera account information, I'm still able to see my data there. How is this possible? And, more importantly, how is this secure? The whole point of using my own password is so that no one, including Opera, can actually read that data.

@arch3rtemp said in Opera Linux browser - h.264 support (through x264 open source codec):

There are no chromium codecs in Ubuntu repositories anymore, neither in Snap

Still available in Snap as "chromium-ffmpeg". For me, it doesn't automatically work, but you can link directly from the snap and it works fine.

sudo mkdir -p /usr/lib/x86_64-linux-gnu/opera/lib_extra && \
sudo ln -fst /usr/lib/x86_64-linux-gnu/opera/lib_extra/ /snap/chromium-ffmpeg/current/chromium-ffmpeg-92972/chromium-ffmpeg/libffmpeg.so && \
echo -e "\n\nLink successful, restart Opera and it should work."

@curious273 said in Google Calendar won't let go.:

Worse is issue #2: There are only two options... close (the x on the left), and allow (the button on the right). There is no way to say "no, I don't want this." Meaning that, unless you click "allow," this alert will come up again every single time you go the calendar.

Just in case anyone else runs across this because they're having the same problem (like I just was), there is a way to fix this for a particular site yourself but it does require a fair bit of technical knowledge. If you don't know what a condensed JSON file is and how to edit one safely, you should just disable the option altogether as mentioned above.

If you do know what a condensed JSON file is and how to edit one, here's the rough outline. I'm intentionally leaving out a lot of details just in case someone is tempted to try this without knowing what they're doing and potentially corrupting their entire profile in the process.

1. Go to the site that's asking if you want to "Allow" it to be a protocol handler and click "Allow". I know this seems backwards but bear with me.
2. Completely close Opera. Otherwise the changes you're about to make will get lost.
3. Open up the "Preferences" file in your Opera profile directory. (preferably in an editor than can expand it to make it more readable. I used Atom with the pretty-json package.)
4. Search for "registered_protocol_handlers" and look for the one you just registered.
5. You should see the handler you just selected listed in that array. It should have 4 properties: default, last_modified, protocol, and url. Delete "default" (including the value and the trailing comma)
6. If you want to be extra thorough, move the entire block for that particular handler from the registered_protocol_handlers array into the ignored_protocol_handlers one. If you don't know what that means just skip this step.
7. Save the file and start Opera back up. Navigate to the site in question and you should find that it no longer prompts you. Note that when you accepted the handler earlier, you may have updated your system handler preferences as well (for mailto links for example). Remember to change that back after you're done, otherwise those links will still call Opera but it won't know what to do with them.

In my case it ended up just being a delay issue. This was the first time I'd set up syncing, so it took about 45 minutes before my data showed up as encrypted online.

The fact that the browser synced data before that, however, is a problem. When you first enable syncing it asks if you want to enable it or go to more settings. I would have thought that more settings meant "don't do anything until I finish adjusting settings", but data was obviously sent up to the server before I finished changing those settings since I immediately selected to use a passphrase.

According to the docs, when you use a separate password for synchronization (instead of using your Opera account), ALL data including bookmarks and browsing history is encrypted.

However, if I go to sync.opera.com from a different browser and log in using only my Opera account information, I'm still able to see my data there. How is this possible? And, more importantly, how is this secure? The whole point of using my own password is so that no one, including Opera, can actually read that data.