Angles.
World Trade Center
#portland #oregonexplored #iPhonePro
I just made a list of all my expected flights in 2023 and I am just *barely* going to hit @AlaskaAir MVP Gold status (40K) by the very end of the year.
How did I fly so much in 2019?? I hit Gold 75K status by April in 2019! 🤯
I just made a list of all my expected flights in 2023 and I am just *barely* going to hit @AlaskaAir MVP Gold status (40K) by the very end of the year.
How did I fly so much in 2019?? I hit Gold 75K status by April in 2019! 🤯
How did I fly so much in 2019?? I hit Gold 75K status by April in 2019! 🤯
I’ve been thinking a lot about nostalgia lately. As an artist, to a certain extent you don’t want to lean on nostalgia. It feels lazy. You should always be pushing the envelope, trying to be edgy and provocative. Original in some sense.
But nostalgia can be a worthy muse if you let it. The moment you cross over from old & tired to retro & vibrant isn’t always easy to pin down, but it’s absolutely real. And to master the subtle art of the throwback, the revival, the clever pastiche…well, there’s nothing lazy about that. #creativity
Now #Putin and #Lavrov try to justify killing Ukrainians because NATO wants a "Final Solution to the Russian Question"
....Like Hitler's "Final Solution to the Jewish Problem"
Nobody wants to kill all the Russians.
We want Russia to stop killing children in Ukraine
#NAFO
A poem for #NAFO and all the #fellas of the #forge whose artistry and dedication inspire me
#smallpoems
Fellas
develop
medicinal plates
of ceramic pfp
enhancements to allow
minimal enchantments
of liminal
distaste
in fates of info
spaces dripped
in
subliminal
hymnals
#clmooc #ncte #engchat & #NAFO looking for few volunteer poets. Help raise $$ for @U24_gov_ua to get kids in #ukraine tablets for remote and bomb shelter learning
Do something like our poetry port: bit.ly/3CZ3lsm
Make a donation, get a poem and fella with day's word
Are you watching from above during eternal Caturday?
★★★★★Stories of Your Life and Others
Mike McHargue recommended this book on his podcast years ago and I didn’t realize until I checked it out that the title short story was adapted into the film Arrival, which is one of my favorites. Based on that, I had high hopes of it being a good collection and it did not disappoint. Highly recommended — both the film and this collection.
Tiny scoop: We learned today that Twitter’s revenue is down 40 percent year over year (& Musk’s first giant interest payment on the company is due at the end of the month):
twitter.com/nymag/status/1…
Twitter’s staff spent years trying to protect the platform against impulsive billionaires who wanted to use it for their own ends — then one made himself the CEO. @Zo...
Replying to people on the social web used to be “simple” before #socialMedia, when we used blogs. You would either write:
1. a short reply — directly on someone’s blog post comment form, OR
2. a longer reply — on your own blog, in-reply-to ...
tantek.com/t5Nu1
Replying to people on the social web used to be “simple” before #socialMedia, when we used blogs. You would either write:
1. a short reply — directly on someone’s blog post comment form, OR
2. a longer reply — on your own blog, in-reply-to & linking to the other post and send a Pingback, expecting at least the other post’s author to see your reply, or you would also write a short comment in their blog post comment form with a brief summary & link to your longer reply post
Aside: web forums^1 at the time were proto-silos^2, and replies/threads were generally self-contained therein.
Then social media exploded and eventually everybody was replying everywhere all at once.
This was so burdensome that some even hired social media managers to perform the labor of how (and if) to reply on each silo, and attempt to keep up with every new silo that popped up.
After a few years of this mid-to-late-2000s social web chaos, in the early 2010s many of us went back to option 2. above from the pre-social-media era, and as part of owning our data^3, started posting our replies in general on our own #IndieWeb sites:
1. Regardless of brevity or length, we resumed posting peer-to-peer replies on our personal sites (now sent site-to-site with Webmentions^4), watched destinations retrieve & display our comments, and were pleased that our peer-to-peer comments looked like any other comments (except with permalinks back to our originals).
2. We also started posting replies to tweets, GitHub issues^5, etc. on our own sites, and automatically POSSE-threading them into their sites of origin.
3. When we wrote site-to-site replies where the original post had itself been syndicated to social media^6, we did both 1 & 2. This let readers follow the conversation in either place, providing an #IndieWeb record for if/when the social media thread was taken down, or disappeared along with another silo shutdown^7.
Following this 1,2,3 approach helped conceptually simplify replying on the social web, and worked well except for a couple of interesting ongoing challenges:
* What is the most efficient user interface path from viewing someone else’s post to writing a reply from your own site?
* How should you @-mention someone you are replying to? (and how can our tools write or pre-fill that for us?)
Regarding the latter, on day 14 I wrote a bit about how should we @-mention in general https://tantek.com/2023/014/t4/domain-first-federated-atmention though that was more of a general @-mention exploration.
As a follow-up to day 14, it’s worth looking into @-reply mentions in particular, specifically for each of the above 1,2,3 contexts, analyzing examples of each, and looking for patterns of @-reply mentions best practices that we can document & recommend.
This is day 16 of #100DaysOfIndieWeb #100Days, except I didn’t finish writing it (mostly) til the morning after, and editing later that afternoon.
← Day 15: https://tantek.com/2023/015/t1/publish-indieweb-decide-distribute
→ 🔮
^1 https://en.wikipedia.org/wiki/Internet_forum
^2 https://indieweb.org/silo
^3 https://indieweb.org/own_your_data
^4 https://tantek.com/2023/012/t1/six-years-webmention-w3c
^5 https://indieweb.org/GitHub#POSSE_to_GitHub
^6 https://tantek.com/2023/015/t1/publish-indieweb-decide-distribute
^7 https://indieweb.org/site-deaths
1. a short reply — directly on someone’s blog post comment form, OR
2. a longer reply — on your own blog, in-reply-to & linking to the other post and send a Pingback, expecting at least the other post’s author to see your reply, or you would also write a short comment in their blog post comment form with a brief summary & link to your longer reply post
Aside: web forums^1 at the time were proto-silos^2, and replies/threads were generally self-contained therein.
Then social media exploded and eventually everybody was replying everywhere all at once.
This was so burdensome that some even hired social media managers to perform the labor of how (and if) to reply on each silo, and attempt to keep up with every new silo that popped up.
After a few years of this mid-to-late-2000s social web chaos, in the early 2010s many of us went back to option 2. above from the pre-social-media era, and as part of owning our data^3, started posting our replies in general on our own #IndieWeb sites:
1. Regardless of brevity or length, we resumed posting peer-to-peer replies on our personal sites (now sent site-to-site with Webmentions^4), watched destinations retrieve & display our comments, and were pleased that our peer-to-peer comments looked like any other comments (except with permalinks back to our originals).
2. We also started posting replies to tweets, GitHub issues^5, etc. on our own sites, and automatically POSSE-threading them into their sites of origin.
3. When we wrote site-to-site replies where the original post had itself been syndicated to social media^6, we did both 1 & 2. This let readers follow the conversation in either place, providing an #IndieWeb record for if/when the social media thread was taken down, or disappeared along with another silo shutdown^7.
Following this 1,2,3 approach helped conceptually simplify replying on the social web, and worked well except for a couple of interesting ongoing challenges:
* What is the most efficient user interface path from viewing someone else’s post to writing a reply from your own site?
* How should you @-mention someone you are replying to? (and how can our tools write or pre-fill that for us?)
Regarding the latter, on day 14 I wrote a bit about how should we @-mention in general https://tantek.com/2023/014/t4/domain-first-federated-atmention though that was more of a general @-mention exploration.
As a follow-up to day 14, it’s worth looking into @-reply mentions in particular, specifically for each of the above 1,2,3 contexts, analyzing examples of each, and looking for patterns of @-reply mentions best practices that we can document & recommend.
This is day 16 of #100DaysOfIndieWeb #100Days, except I didn’t finish writing it (mostly) til the morning after, and editing later that afternoon.
← Day 15: https://tantek.com/2023/015/t1/publish-indieweb-decide-distribute
→ 🔮
^1 https://en.wikipedia.org/wiki/Internet_forum
^2 https://indieweb.org/silo
^3 https://indieweb.org/own_your_data
^4 https://tantek.com/2023/012/t1/six-years-webmention-w3c
^5 https://indieweb.org/GitHub#POSSE_to_GitHub
^6 https://tantek.com/2023/015/t1/publish-indieweb-decide-distribute
^7 https://indieweb.org/site-deaths
We talked to more than two dozen Twitter employees about how Elon Musk’s takeover at the company upended their lives and the culture they knew. This is their story:
twitter.com/nymag/status/1…
Twitter’s staff spent years trying to protect the platform against impulsive billionaires who wanted to use it for their own ends — then one made himself the CEO. @Zo...
Finished reading: Stories of Your Life and Others by (ISBN 9781931520898)
Have you found a good fit during eternal Caturday?
Why yes I did just paint my blank electrical plates to match the wall color because I didn't like how they stood out in white
Why yes I did just paint my blank electrical plates to match the wall color because I didn't like how they stood out in white
Protect your neck!!
What an awesome forge.
@Kolya728 @fellarequests @Official_NAFO @goblin__soup @Kama_Kamilia @BravoKilo6464 With his .50 Desert Eagle... your Wu-Tang Clan Fella can protect his neck while gettin'...
Welcome to #NAFO @DJfromAnnapolis and here is your @fellarequests thank you for your long term support of #Ukraine, the numerous donations, and bringing the struggle to freedom to your radio show
