Skip to main content

LinkedIn & Gmail = Spam

Hello all

I've just registered with LinkedIn and it offered to invite people from my Gmail address book. I've used that feature and now regret it cause invitation email have been send out to all Launchpad bugs, questions, merge proposals, mailing lists and BTS bugs.....

I'm very sorry for all the spam! Please don't block me =(


  1. In fact I looked for you after receiving such an invitation :)

  2. Heya =)

    Nice to meet you. I have like 2500+ emails in my address book =)

  3. Hrmm, this might explain the reasons in the past for receiving Linked In emails via mailing lists. Interesting to know, thanks for the heads up on this.

  4. You .. gave them you email password?

  5. I saw your mail and was like "poor soul, I remember when that happened to me."

  6. @nixternal: Mailman / LP / BTS should filter those....

    @Zash: Well yeah, it used Google API and it wasn't faked up.

    @jcastro: thanks for your support.

    @Dennis: "DON'T PANIC" =) loved Hitchhikers Guide to Galaxy.

  7. It scares me how many people (with organisational power as well as those without) are more than happy to hand over the keys to their life to a frankly unknown entity.

    You might say "Oh everybody knows and trusts LinkedIn" but you have no idea what happens to your credentials once they're submitted.

  8. Ya know, there are checkboxes next to the names so you can decide who to invite and who not to. I usually go with only inviting people who are in the "already on LinkedIn" list, not the "doesn't have an account, can I email them now???" list.

  9. I have gotten several such emails on the GSoC mailing lists. For that reason, I refuse to use LinkedIn under any circumstances.

  10. This whole "web 2.0" or social web.. whatever its called scares me. Facebook scares me...

    Facebook's Eroding Privacy Policy: A Timeline

    "Since its incorporation just over five years ago, Facebook has undergone a remarkable transformation. When it started, it was a private space for communication with a group of your choice. Soon, it transformed into a platform where much of your information is public by default. Today, it has become a platform where you have no choice but to make certain information public..."

    Facebook Tries to Make Violations of Terms of Use Into Criminal Violations

    "Under Facebook's theory, millions of Californians who disregard or don't read terms of service on the websites they visit could face criminal liability."

    "Even the simple use of the automatic login feature of most browsers would constitute a violation under Facebook's theory, since those services are "automatic means" for logging in."

    "...users who shave a few years off their age in their profile, claim to be single when they are married, or change jobs or addresses without updating Facebook right away would also have violated the criminal law."


Post a Comment

Popular posts from this blog

How to disable TLS 1.0 and TLS 1.1 on Ubuntu

Example of website that only supports TLS v1.0, which is rejected by the client Overivew TLS v1.3 is the latest standard for secure communication over the internet. It is widely supported by desktops, servers and mobile phones. Recently Ubuntu 18.04 LTS received OpenSSL 1.1.1 update bringing the ability to potentially establish TLS v1.3 connections on the latest Ubuntu LTS release. Qualys SSL Labs Pulse report shows more than 15% adoption of TLS v1.3. It really is time to migrate from TLS v1.0 and TLS v1.1. As announced on the 15th of October 2018 Apple , Google , and Microsoft will disable TLS v1.0 and TLS v1.1 support by default and thus require TLS v1.2 to be supported by all clients and servers. Similarly, Ubuntu 20.04 LTS will also require TLS v1.2 as the minimum TLS version as well. To prepare for the move to TLS v1.2, it is a good idea to disable TLS v1.0 and TLS v1.1 on your local systems and start observing and reporting any websites, systems and applications that

Ubuntu 23.10 significantly reduces the installed kernel footprint

Photo by Pixabay Ubuntu systems typically have up to 3 kernels installed, before they are auto-removed by apt on classic installs. Historically the installation was optimized for metered download size only. However, kernel size growth and usage no longer warrant such optimizations. During the 23.10 Mantic Minatour cycle, I led a coordinated effort across multiple teams to implement lots of optimizations that together achieved unprecedented install footprint improvements. Given a typical install of 3 generic kernel ABIs in the default configuration on a regular-sized VM (2 CPU cores 8GB of RAM) the following metrics are achieved in Ubuntu 23.10 versus Ubuntu 22.04 LTS: 2x less disk space used (1,417MB vs 2,940MB, including initrd) 3x less peak RAM usage for the initrd boot (68MB vs 204MB) 0.5x increase in download size (949MB vs 600MB) 2.5x faster initrd generation (4.5s vs 11.3s) approximately the same total time (103s vs 98s, hardware dependent) For minimal cloud images that do not in

Ubuntu Livepatch service now supports over 60 different kernels

Linux kernel getting a livepatch whilst running a marathon. Generated with AI. Livepatch service eliminates the need for unplanned maintenance windows for high and critical severity kernel vulnerabilities by patching the Linux kernel while the system runs. Originally the service launched in 2016 with just a single kernel flavour supported. Over the years, additional kernels were added: new LTS releases, ESM kernels, Public Cloud kernels, and most recently HWE kernels too. Recently livepatch support was expanded for FIPS compliant kernels, Public cloud FIPS compliant kernels, and as well IBM Z (mainframe) kernels. Bringing the total of kernel flavours support to over 60 distinct kernel flavours supported in parallel. The table of supported kernels in the documentation lists the supported kernel flavours ABIs, the duration of individual build's support window, supported architectures, and the Ubuntu release. This work was only possible thanks to the collaboration with the Ubuntu C