Topics created by rejzor

@rejzor said in Stop signing me out of forum ffs: Half of people have no clue what or why something is happening. I deal with such nonsense basically daily. This is why you don't see more reports, half of the people think it's because they did something. I know I didn't do anything here. Either Opera broke their own browser or they broke the forum. If it were true, there would have been lots of reports from the other half.

@burnout426 I managed to do some testing later, that is indeed the case. It's only sending referrer if link is clicked on the old page and you're transfered to new domain. With NoRef extension, even that is blocked if you set it to block only 3rd party ones.

better than nothing, certainly, but my opinion is that if we are doing it we should do it right from the beginning. also opera on phones should finally get the ability to work with encrypted sync data

If you look on https://blogs.opera.com/desktop/ for example, you'll now see an RSS icon for better discoverability.

In Chrome, if you have "Allow sites to save and read cookie data" enabled and "Block third-party cookies" enabled, when you visit a site, you can click the badge in the address field and click on "cookies". When you do, you can see what cookies have been blocked where you'll see all the 3rd-party cookies in there that are blocked. You then have the option to click "allow". When you do, [*.]foo.com for each of the 3rd parties is added to the cookie exceptions list and then those 3rd parties are allowed. Visiting those third-party domains directly would already be allowed via "Allow sites to save and read cookie data" as they'd be first-party in that case. The same thing is working in Opera for me too. Opera just doesn't have the UI for it. Now, in this case, when an exception is added, it allows 3rd party cookies for that domain when visiting any domain. *If* you want a domain to only be an allowed third party when visiting a specific domain, I don't know how to do that. Maybe an extension does that.

@rejzor You can always add/open/etc something directly from a site on a as long as the site allows it, at least on Windows.

Can someone tell me how to add BLOCK exception for all cookies that originate from: "ad" or "ads" subdmain? In most other apps, the syntax is simply "ad." or "ads.". But if I do this in Opera, it just makes the address red, meaning I'm trying to use illegal syntax. I want to globally block all cookies that originate from ad. subdomain so I don't have to manually block every single damn domain by hand. Can this be done? I've checked all documentation of Cookies exceptions manager and there is no info about it what so ever about allowed syntaxes for addresses in it which is ultra annoying...

Well, I don't want an external tool if Opera could have this out of the box. Besides, I hate external tools because they don't sync data between browsers. I don't want to keep doing same thing for all 3 systems that I run. Unless this tool you're mentioning controls cookies directly via Opera's controls. Then it might be interesting... EDIT: Great, this thing can add it to exclusions. And it does it in such a way that I now can't remove the damn thing from the exclusions list. WTF It has "i" in a circle instead of delete button. And extension has no control to remove it. Stupid.

@concretable I said this should be a profile/setting among existing ones, not default behavior. It's what majority could use to filter out junk cookies on a global scale while having all the pages that they use regularly working because they'd automatically be allowed since they are bookmarked. For those that aren't, users would add allowed exclusions. Which would be rare.

Confirmed.

@rejzor I've been thinking about something like this since a while and I guess it could be kinda helpful, specially for those users who don't read the blog and often are caught by some change that they don't know about. It could be a simple html or txt file, automatically opened after an update, listing in a user friendly language what was added, what was removed, what was changed and what was fixed that would be relevant for the users.

@sgunhouse Heh, and now it's working correctly. Almost as if someone changed it now that I complained over it...