> bmallred may not follow you
I _assume_ you share your followings publicly, I see them on your feed, so I _assume_ so. I was going to debug this on my side too today to see if.I goofed something up but my pod is rather busy so I hadn't done that yet π (_actually working again finally on search_)
> bmallred may not follow you
I _assume_ you share your followings publicly, I see them on your feed, so I _assume_ so. I was going to debug this on my side too today to see if.I goofed something up but my pod is rather busy so I hadn't done that yet π (_actually working again finally on search_)
Alternative message me on Salty IM (https://salty.im) at
prologic@mills.io
Alternative message me on Salty IM (https://salty.im) at
prologic@mills.io
>(..) π§
>(..) π§
> Deeply questionable legality aside, do any of you use Copilot? Has it had any material impact on your programming work? Is its use allowed by your employer, or do you only use it for personal projects at home?
No never and I never will!
> Deeply questionable legality aside, do any of you use Copilot? Has it had any material impact on your programming work? Is its use allowed by your employer, or do you only use it for personal projects at home?
No never and I never will!
> As an aside, my opinion on GitHub Copilot is clear β itβs quite possibly the largest case of copyright infringement in human history, and in its current incarnation it should not be allowed to continue to operate. As I wrote over a year ago:
I wrote about this three years ag! https://www.prologic.blog/2021/07/11/why-i-no.html
> As an aside, my opinion on GitHub Copilot is clear β itβs quite possibly the largest case of copyright infringement in human history, and in its current incarnation it should not be allowed to continue to operate. As I wrote over a year ago:
I wrote about this three years ag! https://www.prologic.blog/2021/07/11/why-i-no.html
What do we call it when you get to engage in discussion over topics you find in these "filter bubbles" with a different viewpoint, only to be shot down, overridden, or met with other arguments that support the existing "filter bubble"'s state?
What do we call it when you get to engage in discussion over topics you find in these "filter bubbles" with a different viewpoint, only to be shot down, overridden, or met with other arguments that support the existing "filter bubble"'s state?
> Consequently, users become separated from information that disagrees with their viewpoints, effectively isolating them in their own cultural or ideological bubbles, resulting in a limited and customized view of the world.
> Consequently, users become separated from information that disagrees with their viewpoints, effectively isolating them in their own cultural or ideological bubbles, resulting in a limited and customized view of the world.
#rafgment π€¦ββοΈ
#fragment π€¦ββοΈ
#fragment π€¦ββοΈ
- Event: Yarn.social Online Meetup
- When: 25th May 2024 at 12:00pm UTC (midday)
- Where: Mills Meet : Yarn.social
- Cadence: 4th Saturday of every Month
Agenda:
> Anything we want to talk about. Twtxt, Yarn, self hosting, cool stuff you've been working on. chit-chat, whatever π
#Yarn.social #Meetup
- Event: Yarn.social Online Meetup
- When: 25th May 2024 at 12:00pm UTC (midday)
- Where: Mills Meet : Yarn.social
- Cadence: 4th Saturday of every Month
#Yarn.social #Meetup
- Event: Yarn.social Online Meetup
- When: 25th May 2024 at 12:00pm UTC (midday)
- Where: Mills Meet : Yarn.social
- Cadence: 4th Saturday of every Month
Agenda:
> Anything we want to talk about. Twtxt, Yarn, self hosting, cool stuff you've been working on. chit-chat, whatever π
#Yarn.social #Meetup
https://calendar.google.com/calendar/event?action=TEMPLATE&tmeid=MDJuM2hzNThvaWsydTdoa3B2ODl0dGxlZzFfMjAyNDA1MjVUMTIwMDAwWiBwcm9sb2dpY0BzaG9ydGNpcmN1aXQubmV0LmF1&tmsrc=prologic%40shortcircuit.net.au&scp=ALL">
$ curl -qssL https://twtxt.net/ | grep -E 'In-reply-to' | head
<a href="https://twtxt.net/conv/2tjsjuq?p=1#rlsxhsq" title="Show conversation for #2tjsjuq">In-reply-to</a>
<a href="https://twtxt.net/conv/bghmkra?p=1#dfnrbyq" title="Show conversation for #bghmkra">In-reply-to</a>
<a href="https://twtxt.net/conv/e24exeq?p=1#itft6wa" title="Show conversation for #e24exeq">In-reply-to</a>
For some reason the latest version of Chrome is stripped
#fragment(s) from the HTML body being served.da fuq?! When did this change, in what version? Did we (W3C and the community) agree that this behavior should change?! π± Fark'n hell Googleβ’ Chrome π€¬
$ curl -qssL https://twtxt.net/ | grep -E 'In-reply-to' | head
<a href="https://twtxt.net/conv/2tjsjuq?p=1#rlsxhsq" title="Show conversation for #2tjsjuq">In-reply-to</a>
<a href="https://twtxt.net/conv/bghmkra?p=1#dfnrbyq" title="Show conversation for #bghmkra">In-reply-to</a>
<a href="https://twtxt.net/conv/e24exeq?p=1#itft6wa" title="Show conversation for #e24exeq">In-reply-to</a>
For some reason the latest version of Chrome is stripped
#fragment(s) from the HTML body being served.da fuq?! When did this change, in what version? Did we (W3C and the community) agree that this behavior should change?! π± Fark'n hell Googleβ’ Chrome π€¬