simpss

yes, exactly, thank you. Not as powerful as a specific wildcard, but good enough.

sadly, it doesn't work with .something, so 'inurl:.co.uk' doesn't seem to work. Works with 'co.uk' but that's only valuable with longer suffixes. something like 'uk' is a bit too common.

sorry, just checked, it's the wildcard that isn't working. So 'site:*.co.uk'

the only gripe i have with DDG is missing 'site: "somewebsite.com"' option. Is there a way to achieve it?

I mainly use it for '*.countrydomain' to get results for a specific country.

All EU citizens have access to public sector datasets. If you know who is gathering/organizing the data, shoot them an e-mail and they should give you the data.

This right comes from the "European Code of Good Administrative Behaviour" Article 22.

https://www.ombudsman.europa.eu/et/publication/en/3510

about:config dom.event.clipboardevents.enabled = false and you're good.

i'm not 100% sure how it works, but it seems to sync some messages. Not working perfectly as my desktop client does not have the full history from a chat, even though my phone does. It only has some of the messages from where the desktop client was first started.

I have not had an issue buying a prepaid sim in eastern europe AND EU is a "free roaming" zone, so if it works in the Eastern parts, it's going to work everywhere else as well.

I've found that unless you use some of the big-name e-mail providers, there's a high chance your letter wasn't even seen.

Companies tend to use some providers e-mail solutions and some of them are way too trigger-happy for spam.

It's gotten so bad, that before applying, I look at their MX records and if it's gmail, I won't even bother unless i really-really want the job. In that case I follow up with a phone-call.

we compete on the same market, so we have the same salaries.

But the rest of the country doesn't, so we have the lower COL.

Give me a private contact and I can give you some concrete answers and tips regarding the area.

software engineer/manager with (bigger) international projects. This is on the high end for such positions.

I can't complain :)

Not sure how it works in Australia, but if i break down my salary by taxes in Eastern Europe, I'm paying 33% "social tax" which comes out to around 1900€/month. This breaks down further to 2 groups. One for pension and the other for healthcare.

Pension is 20% from the total. (used to pay the current pensions)

Healthchare is 13% from the total.

This comes out at around 990€/month for "health insurance". There are advantages and disadvantages to both systems, but I'm pretty sure you're paying something as a tax for you health insurance and it's probably similar to what they're paying.

To be fair, i'm well paid and a person with an average salary would pay around 250€ monthly. It's just the way our system is setup with a fixed % which automatically creates tax brackets.

Let me introduce you to the lada 4x4(previously known as the lada niva all over the ex-soviet countries).

https://www.lada.ru/en/cars/4x4/3dv/about.html

it hasn't changed much, it's still serviceable with a hammer and a couple of pulleys and wrenches. Not sure if it's available in Belgium(it is in eastern europe) and it sure as hell isn't as comfy as a BMW or a MB, but it's cheap to buy and maintain.

yes, the first example I know from the top of my head is all the sonoff stuff.

They run a popular ESP8266 chip which people reflash.

https://duckduckgo.com/?q=sonoff+reflash&t=canonical&ia=web

because this is a different law and the penalties are (much much) lower. They could just pay the fine daily, it's better to sort out the actual issue.

us-based tech companies have been getting fines for GDPR(data privacy) violations, not false advertising.

On another topic, someone recently posted this youtube video of a Norwegian engineer explaining her views on tech worker ethics, how we've got here and maybe a way to fix it or atleast improve on the current situation. I'd recommend showing it to your commute buddies.

It really resonated with my thoughts, how I've viewed the tech world and my (tiny) part in it.

https://www.youtube.com/watch?v=HfNIiitVFtc

the original solution was probably just brought over from ESP8266 with little or no modifications. The 8266 had less resources then ESP32.

that would only be valid if crash support is requested and provided. As far as I know ubiquiti is pretty hands-off in terms of support, so the case isn't too valid.

contact your local DPA[1] and file a complaint. There's plenty of info on the original thread[2] on what they're doing wrong.

[1] - https://ec.europa.eu/info/law/law-topic/data-protection/refo...

[2] - https://community.ui.com/questions/UI-official-urgent-please...

given that there are very little references to GDPR in their ToS and privacy policy I'd say they haven't even thought of it properly.

Also in the original thread someone quoted this cool tidbit from their ToS .[1]

> Special Note to International Users. If You are accessing the Services from the European Union, Asia or any other region with laws or regulations governing personal data collection and disclosure that differ from United States laws, please be advised that Your continued use of the Services will be governed by United States law

this makes it seem even more likely.

[1] - https://www.ui.com/legal/termsofservice/

in such case, it might be pseudonymous, but to make it pseudonymous specific effort is required. I'll copy an old comment which explains the terms. ID in this case could be the IP address, device identifier etc...

--------------------------

A person is identified, if the ID references only one user in the whole dataset[1]. This also makes any information linked to the ID PII.

the ID would be pseudo-anonymous if one would need some extra data, to which they don't have access to, for linking the ID to one specific user in the whole dataset[2].

So to answer your question, RTB ID is not pseudo-anonymous as it only references a single user out of all of them.

[1] It's also important to understand the definition of PII in GDPR context. Which is any data that relates to an identified or identifiable person. Identifiable is the same as distinguishable. Knowing this helps to understand where the line is. https://www.lexico.com/en/definition/identifiable

[2] Definition of pseudonymisation, 5'th bullet-point: https://gdpr-info.eu/art-4-gdpr/ sheds some light on this.

in their privacy policy. Section 1b.

The Usage Data that we collect may include information such as ...... Internet Protocol address ......

https://www.ui.com/legal/privacypolicy/

the thing is, it's pretty difficult to guarantee the data is indeed anonymous. In this specific case, as they are not willing to explain what data is actually processed and say it's somewhere in the Tos, privacy policy[1] etc... we'll take that as the gospel.

----------------

The Usage Data that we collect may include information such as your device data, including your mobile devices, sensor data, device signals, device parameters, device identifiers that may uniquely identify your devices, including your mobile device, web request, Internet Protocol address, browser type, browser language, referring/exit pages and URLs, platform type, the date and time of your request, and one or more cookies that may uniquely identify your devices or browser.[1]

----------------

This data is certainly not anonymous by GDPR standards. Identifiers that uniquely identify a device will in some cases(ex, single-user devices) also be unique identifiers to a single person. That is enough for the data to be considered Personal Data in the context of GDPR.

‘personal data’ means any information relating to an identified or identifiable natural person (‘data subject’); an identifiable natural person is one who can be identified, directly or indirectly, in particular by reference to an identifier such as a name, an identification number, location data, an online identifier or to one or more factors specific to the physical, physiological, genetic, mental, economic, cultural or social identity of that natural person[2]

[1] - https://www.ui.com/legal/privacypolicy/

[2] - https://gdpr-info.eu/art-4-gdpr/

fingerprintjs readme does a good job of explaining it: https://github.com/Valve/fingerprintjs2

as their official response[1] was pretty much "it's outlined in our policies and ToS" then here is what their privacy policy[2] says they collect:

-------------------

Usage Data. As described in this section, we may automatically collect information when you use the Services ("Usage Data"). The Usage Data that we collect may include information such as your device data, including your mobile devices, sensor data, device signals, device parameters, device identifiers that may uniquely identify your devices, including your mobile device, web request, Internet Protocol address, browser type, browser language, referring/exit pages and URLs, platform type, the date and time of your request, and one or more cookies that may uniquely identify your devices or browser. IN ADDITION, WE MAY AUTOMATICALLY COLLECT LOCATION INFORMATION (INCLUDING LATITUDE AND LONGITUDE), PERFORMANCE DATA, MOTION DATA, TEMPERATURE DATA, POWER USAGE DATA, AND ANY DATA OR SIGNALS COLLECTED BY THE DEVICES AS PART OF THE USAGE DATA. WE DO NOT COLLECT THE CONTENTS OF ANY COMMUNICATIONS THAT PASS THROUGH OUR DEVICES OR SERVICES.

-------------------

[1] - https://community.ui.com/questions/UI-official-urgent-please...

[2] - https://www.ui.com/legal/privacypolicy/#c1

it's impossible to verify as we don't know what data is actually being sent. But there's a hint in the ToS and that doesn't sound very anonymized.

-----------------------

From their privacy policy: https://www.ui.com/legal/privacypolicy/#c1

The Usage Data that we collect may include information such as your device data, including your mobile devices, sensor data, device signals, device parameters, device identifiers that may uniquely identify your devices, including your mobile device, web request, Internet Protocol address, browser type, browser language, referring/exit pages and URLs, platform type, the date and time of your request, and one or more cookies that may uniquely identify your devices or browser. IN ADDITION, WE MAY AUTOMATICALLY COLLECT LOCATION INFORMATION (INCLUDING LATITUDE AND LONGITUDE), PERFORMANCE DATA, MOTION DATA, TEMPERATURE DATA, POWER USAGE DATA, AND ANY DATA OR SIGNALS COLLECTED BY THE DEVICES AS PART OF THE USAGE DATA. WE DO NOT COLLECT THE CONTENTS OF ANY COMMUNICATIONS THAT PASS THROUGH OUR DEVICES OR SERVICES.

-----------------------

By this desription, it certainly isn't GDPR compliant. device identifiers/data etc.. is PII in GDPR context and requires a legal basis for processing.

no such thing as implied consent in GDPR.

Here are the conditions for consent: https://gdpr-info.eu/art-7-gdpr/

Most sites don't adhere to that at all as there's pretty much no way to "not agree", which means they can not rely on consent as a legal basis for processing PII.

GDPR does not require "cookie consents forms" and neither do the EU e-privacy rules. There are clear exemptions for authentication and other technical cookies.

Basically, the form is only required if you're doing something nastier, like tracking.

I've never understood why sites just run with the concept and implement the "permission form" when it really isn't required for good actors.

https://wikis.ec.europa.eu/display/WEBGUIDE/04.+Cookies#sect...

ps: for firefox I use "cookie autodelete" extension https://addons.mozilla.org/en-US/firefox/addon/cookie-autode...

A while later, they did pump the breaks completely by reversing the ToS changes.

This means they would have to change the ToS before trying to implement it again, which means the current result isn't moving the goalposts at all and is not a step forwards to the original solution.

See: https://gitlab.com/gitlab-com/www-gitlab-com/merge_requests/... and https://gitlab.com/gitlab-com/www-gitlab-com/merge_requests/...

no concrete answer regarding that yet. I don't think the new ToS was published on gitlab.com already, so this might not be necessary.

I asked the question to get a clear answer, probably won't hear anything back regarding this.

edit: ToS has been rolled back as well: https://gitlab.com/gitlab-org/gitlab/issues/34833#note_23522...

from gitlab:

https://gitlab.com/gitlab-org/gitlab/issues/34833#note_23515...

------------------

We've heard your concerns and questions. There were many more concerns than we expected. We’re going to process the feedback and rethink our plan. We will not activate product usage tracking on GitLab.com or GitLab self-managed before we address the feedback and re-evaluate our plan. We will make sure to communicate our proposed changes prior to any changes to GitLab.com or self-managed instances, and give sufficient time for people to provide feedback for a new proposal. We'll work in this issue.[1]

Here's an MR updating our blog post accordingly: gitlab-com/www-gitlab-com!33289 (diffs, comment 235139590)[2]

-------------------------

1 - https://gitlab.com/gitlab-com/www-gitlab-com/issues/5672 2 - https://gitlab.com/gitlab-com/www-gitlab-com/merge_requests/...