From: Ruben Beltran del Rio Date: Thu, 27 Apr 2023 00:00:17 +0000 (+0000) Subject: blog-sync-up-1682553617428 X-Git-Url: https://git.r.bdr.sh/rbdr/blog.unlimited.pizza/commitdiff_plain/dafcc98846e71e00678a8d0e922791fc76d565f0 blog-sync-up-1682553617428 --- diff --git a/archive/1682553617306/link-onbydefault-edge-feature-seems-to-be-sending-all-the-urls-you-visit-to-bing.gmi b/archive/1682553617306/link-onbydefault-edge-feature-seems-to-be-sending-all-the-urls-you-visit-to-bing.gmi new file mode 100644 index 0000000..b67c422 --- /dev/null +++ b/archive/1682553617306/link-onbydefault-edge-feature-seems-to-be-sending-all-the-urls-you-visit-to-bing.gmi @@ -0,0 +1,11 @@ +# Link: On-by-default Edge feature seems to be sending all the URLs you visit to Bing + +=> https://arstechnica.com/gadgets/2023/04/on-by-default-edge-feature-seems-to-be-sending-all-the-urls-you-visit-to-bing/ On-by-default Edge feature seems to be sending all the URLs you visit to Bing +> Microsoft's Edge browser has a relatively recent on-by-default feature that allows you to "follow content creators" in Edge itself. +> The problem is that this feature may be sending information about every single site you visit in Edge to Microsoft. + +I feel there’s been a lot of attempts to rehabilitate Microsoft recently, especially from tech people that are all in with Microsoft tooling, but it shouldn’t surprise anyone to see this behavior. + +> the feature intended to only notify Bing when you were on specific sites you had elected to follow but that "it doesn’t appear to be working correctly, instead sending nearly every domain you visit to Bing." + +sure, bugs happen, but just as well it might have been left there until someone called it out. I’d rather my browser not send *anything* without explicit consent \ No newline at end of file diff --git a/archive/1682553617306/metadata.json b/archive/1682553617306/metadata.json new file mode 100644 index 0000000..0a0578a --- /dev/null +++ b/archive/1682553617306/metadata.json @@ -0,0 +1,4 @@ +{ + "id": "1682553617306", + "createdOn": 1682553617306 +} \ No newline at end of file diff --git a/posts/0/link-onbydefault-edge-feature-seems-to-be-sending-all-the-urls-you-visit-to-bing.gmi b/posts/0/link-onbydefault-edge-feature-seems-to-be-sending-all-the-urls-you-visit-to-bing.gmi new file mode 100644 index 0000000..b67c422 --- /dev/null +++ b/posts/0/link-onbydefault-edge-feature-seems-to-be-sending-all-the-urls-you-visit-to-bing.gmi @@ -0,0 +1,11 @@ +# Link: On-by-default Edge feature seems to be sending all the URLs you visit to Bing + +=> https://arstechnica.com/gadgets/2023/04/on-by-default-edge-feature-seems-to-be-sending-all-the-urls-you-visit-to-bing/ On-by-default Edge feature seems to be sending all the URLs you visit to Bing +> Microsoft's Edge browser has a relatively recent on-by-default feature that allows you to "follow content creators" in Edge itself. +> The problem is that this feature may be sending information about every single site you visit in Edge to Microsoft. + +I feel there’s been a lot of attempts to rehabilitate Microsoft recently, especially from tech people that are all in with Microsoft tooling, but it shouldn’t surprise anyone to see this behavior. + +> the feature intended to only notify Bing when you were on specific sites you had elected to follow but that "it doesn’t appear to be working correctly, instead sending nearly every domain you visit to Bing." + +sure, bugs happen, but just as well it might have been left there until someone called it out. I’d rather my browser not send *anything* without explicit consent \ No newline at end of file diff --git a/posts/0/metadata.json b/posts/0/metadata.json index 8a8ad52..0a0578a 100644 --- a/posts/0/metadata.json +++ b/posts/0/metadata.json @@ -1,4 +1,4 @@ { - "id": "1682467222954", - "createdOn": 1682467222954 + "id": "1682553617306", + "createdOn": 1682553617306 } \ No newline at end of file diff --git a/posts/0/link-sourcehuts-2022-financial-report.gmi b/posts/1/link-sourcehuts-2022-financial-report.gmi similarity index 100% rename from posts/0/link-sourcehuts-2022-financial-report.gmi rename to posts/1/link-sourcehuts-2022-financial-report.gmi diff --git a/posts/1/metadata.json b/posts/1/metadata.json index 970e9b9..8a8ad52 100644 --- a/posts/1/metadata.json +++ b/posts/1/metadata.json @@ -1,4 +1,4 @@ { - "id": "1681911779300", - "createdOn": 1681911779300 + "id": "1682467222954", + "createdOn": 1682467222954 } \ No newline at end of file diff --git a/posts/1/incomplete-thoughts-on-cognitive-diversity.gmi b/posts/2/incomplete-thoughts-on-cognitive-diversity.gmi similarity index 100% rename from posts/1/incomplete-thoughts-on-cognitive-diversity.gmi rename to posts/2/incomplete-thoughts-on-cognitive-diversity.gmi diff --git a/posts/2/introducing-page.gmi b/posts/2/introducing-page.gmi deleted file mode 100644 index 1539a0b..0000000 --- a/posts/2/introducing-page.gmi +++ /dev/null @@ -1,33 +0,0 @@ -# Introducing Page, a website generator - -Do you have a static gemini website that you just wish was a static http website? run `page` on your gemini directory and see `page_html` emerge, rsync both to your static host and you're done! - -=> https://git.sr.ht/~rbdr/page Page is available for free on SourceHut™ - -If you're on mac you can install easily with: - -``` -$ brew tap rbdr/apps git@git.sr.ht:~rbdr/homebrew-apps -$ brew install rbdr/apps/page -``` - -## How we got here. - -I've gone through many variations of how I host my personal website, and since the apocalyptic year of 2012[1] I've been using jekyll to build it and nginx to serve it. - -=> https://www.nasa.gov/topics/earth/features/2012.html [1] in 2012 this sounded like a good idea, but go ask nasa why i kept this going for 10 more years. - -A couple of years ago, while learning how to use pulumi[2] and aws, I decided to migrate all of my personal infrastructure to s3 + cloudfront. While this was satisfying and edifying, it ended up being too much complexity for what now amounted to a bunch of html files with a shared layout. - -=> https://www.pulumi.com/ [2] pulumi, like terraform but nicer - -More recently than that, I discovered the joy of gemini[3] and started maintaining my website as a capsule instead. In fact, I spent more time tending to the gemtext than the htmls, so it seemed even worse to have to go back, update some HTMLs, sync the bucket, invalidate the cloudfront cache, ew. - -=> https://gemini.circumlunar.space/ [3] gemini, like http but nicer -=> gemini://gemini.unlimited.pizza/ [3b] if you're not already seeing this page in gemini, check it out. - -With all that going on, I decided it was time to let jekyll rest, learn some rust, and build a static site generator that takes a bunch of gmi files and a layout to create my website. After a few days of trial and error, here we are. - -## What happens next? - -Well, the odd one out is now my blog generator. So i'm pretty sure the next step will be to also replace blog with a rustier version that does much less. If it does come to that, you can read all about it in your favorite online publication: this here gemlog. diff --git a/posts/2/metadata.json b/posts/2/metadata.json index cbcaf3e..970e9b9 100644 --- a/posts/2/metadata.json +++ b/posts/2/metadata.json @@ -1,4 +1,4 @@ { - "id": "1681763713661", - "createdOn": 1681763713661 + "id": "1681911779300", + "createdOn": 1681911779300 } \ No newline at end of file