* 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? 💭
tt rewrite in Go and quickly implemented a stack widget for tview. The builtin Pages is similar but way too complicated for my use case. I would have to specify a mandatory name and some additional options for each page. Also, it allows me to randomly jump around between pages using names, but only gives me direct access the first, however, not the last page. Weird. I don't wanna remember names. All I really need is a classic stack. You open a new fullscreen dialog and maybe another one on top of that. Closing the upper most brings you back to the previous one and so on.The very first dialog I added is viewing the raw message text. Unlike in @arne's TwtxtReader, I'm not able to include the original timestamp, though. I don't have it in its original form in the database. :-/
Next up is a URL view.
September 21st.—Am struck, not for the first time, by extraordinary way in which final arrangements never are final, but continue to lead on to still further activities until parallel with eternity suggests itself, and brain in danger of reeling.
September 21st.—Am struck, not for the first time, by extraordinary way in which final arrangements never are final, but continue to lead on to still further activities until parallel with eternity suggests itself, and brain in danger of reeling.
a quick morning run (not at pace) with my sister before the wedding shenanigans.
#running
a quick morning run (not at pace) with my sister before the wedding shenanigans.
#running
a quick morning run (not at pace) with my sister before the wedding shenanigans.
#running
You can type 3 and 0 for 30 seconds, 100 for a minute (shown as 1:00), or 200 for two minutes (2:00).
What would happen if you type 777 and Start?
A) Nothing
B) Self-destruction
C) Will run for 7 minutes and 77 seconds (boring!)
What about 7777 ?
Right now you need to copy the markdown code yourself, but next up would be to lean some JS or use HTMX to make the process more smooth.
Right now you need to copy the markdown code yourself, but next up would be to lean some JS or use HTMX to make the process more smooth.
Right now you need to copy the markdown code yourself, but next up would be to lean some JS or use HTMX to make the process more smooth.
Right now you need to copy the markdown code yourself, but next up would be to lean some JS or use HTMX to make the process more smooth.
][) you will find a bunch more of these. It goes without question he never typed that in his feed. My client saves each twt hash I've explicitly marked read. A few days ago, I got plenty of apparently years old, yet suddenly unread messages. Each and every single one of them containing this repeated bracketed text thing. The only conclusion is that something messed up the feed again.
][) you will find a bunch more of these. It goes without question he never typed that in his feed. My client saves each twt hash I've explicitly marked read. A few days ago, I got plenty of apparently years old, yet suddenly unread messages. Each and every single one of them containing this repeated bracketed text thing. The only conclusion is that something messed up the feed again.
\\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