1. 0

    Please tell me this is a parody.

    1. 1

      Kinda, as it is a small side project that I build to experiment with various tech, however, I am glad it cheered up your day. :D

      If you could be more specific, what is not likable I’d be grateful.

    1. 32

      It took until I reached the end of the article for me to realize that the title wasn’t sarcastic. It’s not the first time I’ve seen it but it’s a reminder that this feature is simultaneously fantastic and horrifying.

      1. 5

        I didn’t even realize until I read your comment. I skimmed it, saw the screenshot of Takeout, and was like “ah yes, another guide for moving off of Google services…” and closed the tab.

        1. 2

          Not sure why are you calling this as horrifying. Is it because google have access to all your data? In Btwn I’m the author of this blog.

          1. 5

            Is it because google have access to all your data

            Yes but in particular the location history is an extremely detailed log of your activity. You could imagine a dishonest corporation or government misusing this data to suppress dissidents or manipulate individuals.

            1. 4

              Mobile phone companies had that data for a decade longer than Google. Don’t think that if we got Google to stop collecting it somehow the problem of tracking has been solved.

              1. 2

                Regarding the detailed log of your activity, have a look at this video from Forbrukerrådet Norge:

                “Google manipulates users into constant tracking” https://www.youtube.com/watch?v=qIq17DeAc1M

              2. 3

                A more accurate title would have been “Thank you Google for sharing some of my data with me.” It’s horrifying because it gives a glimpse of how much power they hold over their users, and how easily this power can be abused.

            1. 2

              Working on a tool which is effectively a layer on top of an Amazon service feels like a risky business. If you demonstrate that the need exists, what’s to stop them waking up tomorrow to quickly build an in-house duplicate?

              1. 2

                Nothing. ;) If AWS will build something better, that’s a great thing - way to go!

                It’s not our primary business. We would love to have such facilities in place already. We build that tool in order to ease the pain regarding maintaining a pile of templates - for our convenience.

              1. 2

                Endless repetitions – we need to repeat constantly when writing it. It is error-prone as well as hard to maintain. YAML and JSON flavors do not support any fragments or smaller templating engine, so it is difficult to reuse and work in line with DRY (don’t repeat yourself) principle.

                Is this something you can get with node anchors?

                1. 1

                  Great question! I believe you can’t, I’ve tried while ago.

                  TL;DR: CloudFormation does not support that, see here: https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/template-formats.html - it does not support hash merges, effectively you cannot use anchors.