- Microsoft
- Alibaba
- Open AI
- _more to come..._
> I donβt think it will have any impact
$ jq -r --arg host "gopher.mills.io" '. | select(.request.host==$host) | "\\(.request.client_ip) \\(.request.uri) \\(.request.headers["User-Agent"])"' mills.io.log-au | while IFS=$' ' read -r ip uri ua; do asn="$(geoip -a "$ip")"; echo "$asn $ip $uri $ua"; done | grep -E '^45102.*' | sort | head
45102 47.251.70.245 /gopher.floodgap.com/0/feeds/democracynow/2015/Oct/14/0 ["Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/119.0.0.0 Safari/537.36"]
45102 47.251.84.25 /gopher.floodgap.com/0/feeds/voaheadlines/2014/Mar/09/voanews.com-content-article-1867433.html ["Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36"]
45102 47.82.10.106 /gopher.viste.fr/1/OnlineTools/hangman.cgi%3F0692937396569A52972EB2 ["Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/114.0.0.0 Safari/537.36 Edg/114.0.1823.43"]
45102 47.82.10.106 /gopher.viste.fr/1/OnlineTools/hangman.cgi%3F9657307A96569A52974634 ["Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/114.0.0.0 Safari/537.36 Edg/114.0.1823.43"]
45102 47.82.10.106 /gopher.viste.fr/1/OnlineTools/hangman.cgi%3FB7571C7896569A529E6603 ["Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/114.0.0.0 Safari/537.36 Edg/114.0.1823.43"]
45102 47.82.10.106 /gopher.viste.fr/1/OnlineTools/hangman.cgi%3FB75EF81296569A529E6617 ["Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/114.0.0.0 Safari/537.36 Edg/114.0.1823.43"]
45102 47.82.10.106 /gopher.viste.fr/1/OnlineTools/hangman.cgi%3FC6564ADB96569A5A9E660C ["Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/114.0.0.0 Safari/537.36 Edg/114.0.1823.43"]
$ jq -r --arg host "gopher.mills.io" '. | select(.request.host==$host) | "\(.request.client_ip) \(.request.uri) \(.request.headers["User-Agent"])"' mills.io.log-au | while IFS=$' ' read -r ip uri ua; do asn="$(geoip -a "$ip")"; echo "$asn $ip $uri $ua"; done | grep -E '^45102.*' | sort | head
45102 47.251.70.245 /gopher.floodgap.com/0/feeds/democracynow/2015/Oct/14/0 ["Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/119.0.0.0 Safari/537.36"]
45102 47.251.84.25 /gopher.floodgap.com/0/feeds/voaheadlines/2014/Mar/09/voanews.com-content-article-1867433.html ["Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36"]
45102 47.82.10.106 /gopher.viste.fr/1/OnlineTools/hangman.cgi%3F0692937396569A52972EB2 ["Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/114.0.0.0 Safari/537.36 Edg/114.0.1823.43"]
45102 47.82.10.106 /gopher.viste.fr/1/OnlineTools/hangman.cgi%3F9657307A96569A52974634 ["Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/114.0.0.0 Safari/537.36 Edg/114.0.1823.43"]
45102 47.82.10.106 /gopher.viste.fr/1/OnlineTools/hangman.cgi%3FB7571C7896569A529E6603 ["Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/114.0.0.0 Safari/537.36 Edg/114.0.1823.43"]
45102 47.82.10.106 /gopher.viste.fr/1/OnlineTools/hangman.cgi%3FB75EF81296569A529E6617 ["Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/114.0.0.0 Safari/537.36 Edg/114.0.1823.43"]
45102 47.82.10.106 /gopher.viste.fr/1/OnlineTools/hangman.cgi%3FC6564ADB96569A5A9E660C ["Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/114.0.0.0 Safari/537.36 Edg/114.0.1823.43"]
* 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_):


robots.txt
that I have on https://git.mills.io/robots.txt with content:
User-agent: *
Disallow: /
Evidence attached (_see screenshots_):


\\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).