An email @fellarequests request because like Enerico Toti when it comes to #NAFO
"Nun moro io!"
This Fella launches HIMARS crutches to bonk Vatniks
Hey #NAFO
Forgers get a lot of questions about NFTs, certs, or signing art.
Since a pfp is a thank you for donating there ain't no art to sign but if you want to create canonical proof of your #fella and their forgeday here is how with @internetarchive bit.ly/3wmbe7M
Been ages so I did a Q&A livestream! Let's eat TWO donuts and answer some questions. Sunday at 11:30 Pacific/2:30 Eastern youtu.be/oe_xk-ww05Y
My oven is fixed now which means I can make cinnamon rolls tomorrow! From the tube, not homemade, but still — cinnamon rolls!
We have a special #NAFO Road Trip for you.
@fabizimt, @koneko, and I heading to latest Crimean Beach Concert featuring the newest #fella @11_1VEmusICyyZ5
This #fella a photo journalist by day and rock star by night.
Joined the bill to go on bonking Vatniks from #Ukraine
The latest episode of The House Files is out and yes, myself and @aaronpk are weighing in on the Gas Stove Discourse youtu.be/StWc8Pt3DCQ
Are you aware of an emptiness during eternal Caturday?
Snooze buttons
breed
Lazy
Behavior
#smallpoems
Instead of posting on a personal #IndieWeb site (& POSSE copies), some post primarily to a #fediverse instance and syndicate to Twitter, or vice-versa. How to reply^1 to such posts, e.g.:
Reply to a toot (& POSSE tweet): tantek.com/2023/019/t4
* @-@ (...
tantek.com/t5Nw5
Instead of posting on a personal #IndieWeb site (& POSSE copies), some post primarily to a #fediverse instance and syndicate to Twitter, or vice-versa. How to reply^1 to such posts, e.g.:
Reply to a toot (& POSSE tweet): https://tantek.com/2023/019/t4
* @-@ (Twitter @-name)
This is a variant of case (2) in https://tantek.com/2023/018/t1/elevate-indieweb-above-silo.
We can update the directive and two questions in that post accordingly:
* Elevate #IndieWeb domains above @-@ addresses, and those above any silo identities
1. Do they have an #IndieWeb domain? Then @-domain mention them^2, like you are speaking to them at their domain identity. This will notify them there, or at least reinforce their domain’s importance.
2. Was their post only published on a #fediverse instance (and/or silo), or was it POSSEd to a fediverse instance (and/or silo) and do you plan to federate (and/or POSSE) your reply^3?
Then use their @-@ address or silo @-name, or @-@ (silo @-name) for both, or (@-@, silo @-name) parenthetically following their @-domain if (1). This will notify them on that instance (or silo), and may help thread your POSSE reply.
When posting a reply, you (or your CMS automatically) should explicitly link with u-in-reply-to markup^4 to the post your are replying to, and any of its syndicated copy permalinks on destinations you plan to POSSE your reply (see also multi-reply^5).
This is day 18 of #100DaysOfIndieWeb #100Days, written the day after.
← Day 17: https://tantek.com/2023/018/t1/elevate-indieweb-above-silo
→ 🔮
^1 https://tantek.com/2023/017/t1/socialweb-blogs-reply-comment-post
^2 https://tantek.com/2023/011/t1/indieweb-evolving-at-mention
^3 https://tantek.com/2023/015/t1/publish-indieweb-decide-distribute
^4 https://indieweb.org/in-reply-to
^5 https://indieweb.org/multiple-reply
Reply to a toot (& POSSE tweet): https://tantek.com/2023/019/t4
* @-@ (Twitter @-name)
This is a variant of case (2) in https://tantek.com/2023/018/t1/elevate-indieweb-above-silo.
We can update the directive and two questions in that post accordingly:
* Elevate #IndieWeb domains above @-@ addresses, and those above any silo identities
1. Do they have an #IndieWeb domain? Then @-domain mention them^2, like you are speaking to them at their domain identity. This will notify them there, or at least reinforce their domain’s importance.
2. Was their post only published on a #fediverse instance (and/or silo), or was it POSSEd to a fediverse instance (and/or silo) and do you plan to federate (and/or POSSE) your reply^3?
Then use their @-@ address or silo @-name, or @-@ (silo @-name) for both, or (@-@, silo @-name) parenthetically following their @-domain if (1). This will notify them on that instance (or silo), and may help thread your POSSE reply.
When posting a reply, you (or your CMS automatically) should explicitly link with u-in-reply-to markup^4 to the post your are replying to, and any of its syndicated copy permalinks on destinations you plan to POSSE your reply (see also multi-reply^5).
This is day 18 of #100DaysOfIndieWeb #100Days, written the day after.
← Day 17: https://tantek.com/2023/018/t1/elevate-indieweb-above-silo
→ 🔮
^1 https://tantek.com/2023/017/t1/socialweb-blogs-reply-comment-post
^2 https://tantek.com/2023/011/t1/indieweb-evolving-at-mention
^3 https://tantek.com/2023/015/t1/publish-indieweb-decide-distribute
^4 https://indieweb.org/in-reply-to
^5 https://indieweb.org/multiple-reply
A Special #fella for @thedavidcrosby
Heaven ain't as cloudy as you think
Enjoy the next season
Find a place inside to laugh
Separate the wheat from the chaff
#NAFO
There’s going to be a Tron 3 with Jared Leto. It’s Tronin’ time!
#NotExcited #UnlessDaftPunkDoesTheSoundtrackAgain
Want to try out Mastodon? Thinking about hosting your own? Or maybe you’re new to the experience and need some help or want tips for better connecting? Our kind friends at Reclaim Hosting and ALT are doing a 90 day Mastodon experiment/class/seminar series where you can sign up for an account on a server that will self-destruct at the end of their trial run. They’re doing three sessions (live with recordings after), have a Discord for discussion and questions, and a Google doc with details and tips.
- Session 1: Mission briefing: 19 January 2023 at 16:00 GMT (Watch Live)
- Session 2: Verifying your progress: 23 February 2023 at 16:00 GMT (Watch Live)
- Session 3: 30 days until self-destruct: 23 March 2023 at 16:00 GMT (Watch Live)
Sign up on their server today to try things out: https://thismastodonwillexplo.de/
#MissionMastodon @reclaimhosting@reclaim.rocks @jimgroom@social.ds106.us @marendeepwell@social.ds106.us
Currently reading: Lovestar by (ISBN 9781609804268)
The answer to “How should you @-mention someone you are replying to?”^1 can depend on many factors or a few. Context matters somewhat, sometimes.
We can simplify it to 2 questions, based on 1 directive:
* Elevate #IndieWeb domains, above any silo or @-@ identities
Two questions and answers:
1. Do they have an #IndieWeb domain? Then @-domain mention them^2, like you are speaking to them at their domain identity. This will notify them there, or at least reinforce their domain’s importance.
2. Was their post only published on a silo (or #fediverse instance), or was it POSSEd to a silo (or fediverse instance) and you plan to POSSE (or federate) your reply^3? Then @-mention their silo @-name (or @-@ address), in parentheses if (1). This will notify them on that silo (or instance), and may help thread your POSSE reply.
Examples:
If the author has their own domain:
Reply to an IndieWeb post (& POSSE toot): https://tantek.com/2023/008/t1/
* @-domain (@-@)
Reply to an IndieWeb post (& POSSE tweet): https://tantek.com/2023/016/t1/
* @-domain [that matches their Twitter @-name]
Reply to a toot: https://tantek.com/2023/008/t4/
* @-domain (@-@)
Reply to a tweet: https://tantek.com/2023/002/t2/
* @-domain (Twitter @-name)
If the author does not have their own domain:
Reply to a toot: https://tantek.com/2023/002/t4/
* @-@
Reply to a tweet: none since this series, though it would be of the form:
* Twitter @-name
This is day 17 of #100DaysOfIndieWeb #100Days, again finished the next day.
← Day 16: https://tantek.com/2023/015/t1/publish-indieweb-decide-distribute
→ 🔮
^1 https://tantek.com/2023/017/t1/socialweb-blogs-reply-comment-post
^2 https://tantek.com/2023/011/t1/indieweb-evolving-at-mention
^3 https://tantek.com/2023/015/t1/publish-indieweb-decide-distribute
We can simplify it to 2 questions, based on 1 directive:
* Elevate #IndieWeb domains, above any silo or @-@ identities
Two questions and answers:
1. Do they have an #IndieWeb domain? Then @-domain mention them^2, like you are speaking to them at their domain identity. This will notify them there, or at least reinforce their domain’s importance.
2. Was their post only published on a silo (or #fediverse instance), or was it POSSEd to a silo (or fediverse instance) and you plan to POSSE (or federate) your reply^3? Then @-mention their silo @-name (or @-@ address), in parentheses if (1). This will notify them on that silo (or instance), and may help thread your POSSE reply.
Examples:
If the author has their own domain:
Reply to an IndieWeb post (& POSSE toot): https://tantek.com/2023/008/t1/
* @-domain (@-@)
Reply to an IndieWeb post (& POSSE tweet): https://tantek.com/2023/016/t1/
* @-domain [that matches their Twitter @-name]
Reply to a toot: https://tantek.com/2023/008/t4/
* @-domain (@-@)
Reply to a tweet: https://tantek.com/2023/002/t2/
* @-domain (Twitter @-name)
If the author does not have their own domain:
Reply to a toot: https://tantek.com/2023/002/t4/
* @-@
Reply to a tweet: none since this series, though it would be of the form:
* Twitter @-name
This is day 17 of #100DaysOfIndieWeb #100Days, again finished the next day.
← Day 16: https://tantek.com/2023/015/t1/publish-indieweb-decide-distribute
→ 🔮
^1 https://tantek.com/2023/017/t1/socialweb-blogs-reply-comment-post
^2 https://tantek.com/2023/011/t1/indieweb-evolving-at-mention
^3 https://tantek.com/2023/015/t1/publish-indieweb-decide-distribute
The answer to “How should you @-mention someone you are replying to?”^1 can depend on many factors or a few. Context matters somewhat, sometimes.
We can simplify it to 2 questions, based on 1 directive:
* Elevate #IndieWeb domains, above any silo ...
tantek.com/t5Nv1
Is someone in your personal space during eternal Caturday?
Angles.
World Trade Center
#portland #oregonexplored #iPhonePro