* 185325d - (HEAD -> master) edge: Ban Alibaba (38 seconds ago) <James Mills>fark me 🤦♂️ Alibaba, CN has been hitting my Gopher proxy quite hard as well. Fuck'n hell! 🔥
* 185325d - (HEAD -> master) edge: Ban Alibaba (38 seconds ago) <James Mills>fark me 🤦♂️ Alibaba, CN has been hitting my Gopher proxy quite hard as well. Fuck'n hell! 🔥
* 8a77b64 - (HEAD -> master) edge: Ban Google's ASN (21 seconds ago) <James Mills>
* 8a77b64 - (HEAD -> master) edge: Ban Google's ASN (21 seconds ago) <James Mills>
robots.txt that I have on https://git.mills.io/robots.txt with content:
User-agent: *
Disallow: /
Evidence attached (_see screenshots_):
-- I _think_ its the the Small Web community band together and file a class action suit(s) against Microsoft.com Google.com and any other assholes out there (OpenAI?) that violate our rights and ignore requests to be "polite" on the web. Thoughts? 💭
robots.txt that I have on https://git.mills.io/robots.txt with content:
User-agent: *
Disallow: /
Evidence attached (_see screenshots_):
-- I _think_ its the the Small Web community band together and file a class action suit(s) against Microsoft.com Google.com and any other assholes out there (OpenAI?) that violate our rights and ignore requests to be "polite" on the web. Thoughts? 💭
\\t separator between <timestamp> and <content>. Let users use _any_ valid whitespace here that isn't a newline or carriage return.
\t separator between <timestamp> and <content>. Let users use _any_ valid whitespace here that isn't a newline or carriage return.
\t separator between <timestamp> and <content>. Let users use _any_ valid whitespace here that isn't a newline or carriage return.
Key Points:
1. Linear Feed Problem: Linear feeds present a long list of posts without prioritization, forcing users to scroll endlessly to catch up on friends' content. This can lead to addiction and disengagement.
2. Proposed Alternative (Tree Structure): The daily feed structure organizes posts by day, enabling users to prioritize updates from friends who post infrequently while reducing scrolling effort.
3. Mastodon Experience: The author's experience with Mastodon highlighted its effectiveness in allowing content prioritization and managing social media usage without dependency on algorithms.
4. Challenges and Considerations:
- Implementation Challenges: Creating a daily feed system involves organizing content effectively and ensuring users can prioritize posts.
- Platform Support: Current platforms may not have APIs conducive to such changes, making it difficult to implement without significant technical changes.
- Engagement Metrics: The impact on engagement metrics needs to be considered, as traditional metrics might be misinterpreted in a tree structure.
5. Potential Applications Beyond Social Media: This approach could empower users by giving control over content consumption and aiding in balancing social media use without overwhelming them with information.
6. Future Directions: The author hopes for improvements in alternative platforms' feed systems and engagement metrics, potentially through more interactive content models or changes in APIs.
In conclusion, the article emphasizes the importance of providing users with control over their content consumption, moving away from linear feed
Key Points:
1. Linear Feed Problem: Linear feeds present a long list of posts without prioritization, forcing users to scroll endlessly to catch up on friends' content. This can lead to addiction and disengagement.
2. Proposed Alternative (Tree Structure): The daily feed structure organizes posts by day, enabling users to prioritize updates from friends who post infrequently while reducing scrolling effort.
3. Mastodon Experience: The author's experience with Mastodon highlighted its effectiveness in allowing content prioritization and managing social media usage without dependency on algorithms.
4. Challenges and Considerations:
- Implementation Challenges: Creating a daily feed system involves organizing content effectively and ensuring users can prioritize posts.
- Platform Support: Current platforms may not have APIs conducive to such changes, making it difficult to implement without significant technical changes.
- Engagement Metrics: The impact on engagement metrics needs to be considered, as traditional metrics might be misinterpreted in a tree structure.
5. Potential Applications Beyond Social Media: This approach could empower users by giving control over content consumption and aiding in balancing social media use without overwhelming them with information.
6. Future Directions: The author hopes for improvements in alternative platforms' feed systems and engagement metrics, potentially through more interactive content models or changes in APIs.
In conclusion, the article emphasizes the importance of providing users with control over their content consumption, moving away from linear feed
2024-08-04T11:24:34Z was the last occurrence of this.
2024-08-04T11:24:34Z was the last occurrence of this.
yarnd here? Hmm? 🤔 I've _thought_ about a "read flag" but I just haven't bothered so far...
yarnd here? Hmm? 🤔 I've _thought_ about a "read flag" but I just haven't bothered so far...
CTRL+R on @mckinley's OP to get the _right_ subject reply after poking at the underlying HTML elements on the page.
CTRL+R on @mckinley's OP to get the _right_ subject reply after poking at the underlying HTML elements on the page.
root@vz3:~# free -h
total used free shared buff/cache available
Mem: 62Gi 10Gi 49Gi 72Mi 2.9Gi 51Gi
Swap: 0B 0B 0B
root@vz3:~# free -h
total used free shared buff/cache available
Mem: 62Gi 10Gi 49Gi 72Mi 2.9Gi 51Gi
Swap: 0B 0B 0B
The "Cloud" is just someone else's computer(s).
The "Cloud" is just someone else's computer(s).
> Please contact Microsoft at aks blah balh balh
> Please contact Microsoft at aks blah balh balh
9834_) where we went through the form together. Managed to get to the 3rd page, at which point the "Address" had an asterisk next to it (*) -- I advise operator #9834 that I was not comfortable handing out a specific address, at which point she responded:> Well the IC3 online form is the correct form. Thank you. Goodbye.
And hang up! Haha 🤣 wut da fuq?! 🤦♂️*