Notices tagged with socialmedia

Tantek ()'s status on Sunday, 13-Oct-2024 16:37:00 EDT

Tantek

No I did not block you on the #fediverse / #Mastodon / #Misskey etc.

If you were following me @tantek.com on your client/server/instance of choice but noticed you were no longer doing so, that was due to a recent software bug in my fediverse provider which accidentally caused everyone’s #ActivityPub servers to unfollow me (bug details below).

No it’s absolutely not your fault, you did nothing wrong.

We need a variant of Hanlon’s Razor¹ like:

“Never attribute to malice that which is adequately explained by a software bug.”

Take another look at my posts if you want (directly on @tantek.com or try searching for that on your instance) and if you like what you see or find them otherwise informative and useful, feel free to refollow. If not, no worries!

Also no worries if you ever unfollow/refollow for any reason. I mean that.

I always assume people know best how to manage their online reader/reading experiences, everyone’s priorities and likes/dislikes change over time, and encourage everyone to make choices that are best for their mental health and overall joy online.

Bug details:

This was due to a #BridgyFed bug² that deleted my profile (“ActivityPub actor”) from (nearly?) all instances, making everyone’s accounts automatically unfollow me, as well as remove any of my posts from your likes and reposts (boosts) collections. It also removed my posts from any of your replies to my posts, leaving your replies dangling without reply-contexts. Apologies!

The bug was introduced accidentally as part of another fix about a month ago³, and was triggered within the following week⁴.

Anyone following me before ~2024-09-22 was no longer following me. A few folks have noticed and refollowed. Any likes or reposts of my posts before that date were also undone (removed).

Ryan (@snarfed.org) has been really good about giving folks a heads-up, and apologizing, and quickly doing what he can to fix things.

Bugs happen, yes even in production code, so please do not post/send any hate.

I’d rather be one of the folks helping with improving BridgyFed, and temporary setbacks like this are part of being an early / eager #IndieWeb adopter.

This bug has also revealed some potential weaknesses in other ActivityPub implementations. E.g. deleting an “actor” should be undoable, and undoing a delete should reconnect everything, from follows to likes & reposts collections, to reply-contexts. Perhaps the ActivityPub specification could be updated with such guidance (if it hasn’t been already, I need to double-check).

To be clear, I’m still a big supporter of #BridgyFed, #ActivityPub, #Webmention, and everyone who chooses to implement these and other #IndieWeb related and adjacent protocols as best fits their products and services.

All of these are a part of our broader open #socialWeb, and making all these #openStandards work well together (including handling edge-cases and mistakes!) is essential for providing #socialMedia alternatives that put users first.

References:

¹ https://en.wikipedia.org/wiki/Hanlon%27s_razor
² https://github.com/snarfed/bridgy-fed/issues/1379
³ https://github.com/snarfed/bridgy-fed/commit/4df76d0db7b87cabbd714039546c05b3221169be
⁴ https://chat.indieweb.org/dev/2024-09-22#t1727028174623700

This is post 26 of #100PostsOfIndieWeb. #100Posts

← https://tantek.com/2024/285/t1/io-domain-suggested-steps
→ 🔮

Tantek ()'s status on Saturday, 24-Aug-2024 19:56:00 EDT

Tantek

People over protocols over platforms.

inspired by today’s #indieweb #fediverse #ActivityPub #decentralized #socialMedia lunch meetup at #XOXO #XOXOConf (@xoxo@xoxo.zone)

This is post 16 of #100PostsOfIndieWeb. #100Posts

← https://tantek.com/2024/173/t1/years-posse-microformats-adoption
→ 🔮

Tantek ()'s status on Friday, 29-Mar-2024 00:58:00 EDT

Tantek

Happy World Piano Day¹!

Because there are 88 keys on a standard piano, the 88th day of the year was established as a day to “celebrate the piano and everything around it: performers, composers, piano builders, tuners, movers and most important, the listener”.

There are multiple websites about Piano Day:
* https://www.pianoday.org/
* https://www.worldpianoday.com/

And related #socialMedia and other profiles:
* https://www.instagram.com/pianodayofficial/
* https://linktr.ee/PianoDay
* Spotify playlist: https://open.spotify.com/playlist/2v022joEJ1ZUPi99NHDVNm?si=mmT4rDchTzW60KC3lsTksQ&nd=1&dlsi=2a348a57822c4217

I appreciate that Piano Day is on an ordinal day of the year (88th) rather than a Gregorian date (e.g. 8/8 or August 8th) which is subject to leap year variances. The 88th day of the year is the 88th day regardless whether it is a leap year or not.

From a standards perspective, we can express today’s Piano Day as 2024-088, an ISO ordinal date², however there is no standard date format for just "the 88th day of a year" without specifying a year (yearless).

There is (was) a way to specify a yearless month and day, like you might see as a birthday displayed on a social media site, without disclosing the year, or an annual holiday like May Day³, that is May 1st, without a specific year:

--05-01

This yearless date format (--MM-DD or shorthand --MMDD) was supported in the ISO 8601:2000 standard, but then dropped in the 2004 revision. This omission or deliberate removal was an error, because there are both obvious human visible use-cases (communicating holidays, and yearless birthdays as noted above), and other standards already depended on this yearless date format syntax (e.g. vCard⁴ and specs that refer to it like hCard and h-card).

Every version of ISO 8601 since 2000 has this flaw. Fixing (or patching) #ISO8601 is worth a separate post.

Returning to yearless ordinal dates, since they lack an interchange syntax, we can define one resembling the yearless month day format, yet unambiguously parseable as a yearless ordinal date:

---DDD

e.g. Piano Day would be represented as:

---088

We have to use three explicit digits because there's also pre-existing "day of the month" and "month of the year" syntaxes which are very similar, but with two digits:

--MM
---DD

This yearless #ordinalDate syntax (---DDD) is worth proposing as a delta "repair" spec to ISO 8601 (use-cases: Piano Day and others like Programmer’s Day⁵), alongside at least a restoration of the --MM-DD yearless month day syntax (use-cases: publishing holidays and yearless birthdays), perhaps also the ---DD day of the month and --MM month of the year syntaxes (use-case: language independent numerical publishing of Gregorian months and days of months), and propose adding a NewCal bim of the year syntax --B (numerically superior replacement for Gregorian months and quarters).

Glossary:

hCard
https://microformats.org/wiki/hcard
h-card
https://microformats.org/wiki/h-card
NewCal
http://newcal.org/

References:

¹ https://en.wikipedia.org/wiki/Piano_Day
² https://en.wikipedia.org/wiki/Ordinal_date
³ https://en.wikipedia.org/wiki/May_Day
⁴ https://www.rfc-editor.org/rfc/rfc6350#section-6.2.5
⁵ https://en.wikipedia.org/wiki/Programmer%27s_Day

Tantek ()'s status on Tuesday, 12-Mar-2024 22:19:00 EDT

Tantek

What I created while remotely participating at #IndieWebCamp Brighton 2024: wiki-gardened day 1’s BarCamp sessions notes pages, and documented my @-mention @-@-mention autolinking coding improvements I built the Sunday before.

Day 2 of IndieWebCamps is Create Day, where everyone is encouraged to create, make, or build something for their personal website, or the IndieWeb community, or both.

At the start of day 2, everyone is encourage to pick things to make¹. What to make at an IndieWebCamp² can be anything from setting up your personal website, to writing a blog post, redesigning your styling, building new features, helping other participants, or contributing to shared IndieWeb community resources, whether code or content.

Everyone is encouraged to at least pick something they consider easy, that they can do in less than an hour, then a more bold goal, and then perhaps a stretch goal, something challenging that may require collaboration, asking for help, or breaking into smaller steps.

For my "easy" task, I built on what another remote participant, @gregorlove.com completed the night before. gRegor had archived all the IndieWebCamp Brighton Sessions Etherpads onto the wiki, linked from the Schedule page³. gRegor had noted that he didn’t have time to clean-up the pages, e.g. convert and fix Markdown links.

I went through the 13 Session Notes archives and did the following:
* converted Markdown links to MediaWiki links
* converted indieweb.org (and some services) links to local wiki page links
* fixed (some) typos

With some help from @alexsirac.com (@alexture@todo.eu), I figured out how to create a MediaWiki Contributions summary link of my edits:
* https://indieweb.org/wiki/index.php?title=Special:Contributions&target=Tantek.com&namespace=all&start=2024-03-10&end=2024-03-10&offset=20240310143900&limit=25

I point this out to provide an example of an IndieWeb Create Day project that is:
* incremental on top of someone else’s work
* community contribution rather a personal-focused project
* editing and wiki-gardening as valid contributions, not just creating new content

I point this out to illustrate some of the IndieWeb community's recognitions & values in contrast to typical corporate cultures and incentive systems which often only reward:
* new innovations (not incremental improvements)
* solo (or maybe jointly in a small team) inventions, designs, specs, or implementations
* something large, a new service or a big feature, not numerous small edits & fixes

In this regard, the IndieWeb community shares more in common with Wikipedia and similar collaborative communities (despite the #Indie in #IndieWeb), than any corporation.

For my "more bold" goal, I wrote a medium-sized post about the auto-linking improvements I made the Sunday before the IndieWebCamp to my personal website with examples and brief descriptions of the coding changes & improvements.
* https://tantek.com/2024/070/t1/updated-auto-linking-mention-use-cases

My stretch goal was to write up a more complete auto-linking specification, based on the research I have done into @-mention @-@-mention user practices (on #Mastodon, other #ActivityPub or #fediverse implementations, and even across #socialMedia silos), as well as how implementations link URLs, domains, and paths.

That stretch goal remains a goal, however I did collect a handful of prior posts on @-mentions which I plan to source for specifying auto-linking and @-mentioning:
* https://tantek.com/2023/011/t1/indieweb-evolving-at-mention
* https://tantek.com/2023/014/t4/domain-first-federated-atmention
* https://tantek.com/2023/018/t1/elevate-indieweb-above-silo
* https://tantek.com/2023/019/t5/reply-domain-above-address-and-silo
* https://tantek.com/2023/109/t2/years-ago-first-federated-indieweb-thread
#autoLink #atDomain #atPath #atMention #atMentions #atat #atAtMention

I was one of a few remote participants in addition to ~18 in-person participants, the overwhelming majority of overall attendees, who demonstrated something at the end of IndieWebCamp Brighton 2024 day 2. See what everyone else made & demonstrated on Create Day:
* https://indieweb.org/2024/Brighton/Demos

This is post 13 of #100PostsOfIndieWeb. #100Posts

← https://tantek.com/2024/070/t1/updated-auto-linking-mention-use-cases
→ 🔮

Glossary:

Create Day
https://indieweb.org/Create_Day
IndieWebCamp Brighton 2024
https://indieweb.org/2024/Brighton

References:

¹ https://indieweb.org/IndieWebCamps/Attending#Day_Two
² https://indieweb.org/what_to_make_at_IndieWebCamp
³ https://indieweb.org/2024/Brighton/Schedule#Saturday

Tantek ()'s status on Friday, 02-Feb-2024 16:49:00 EST

Tantek

I felt the #earthquake here in #SanFrancisco. A single quick sharp jolt with rapid decay, duration less than 2s, meaning it was relatively nearby and small in magnitude

I was about to say, perhaps #earthquakes are the last use-case for #Twitter because yes I reflexively checked it and did see posts about it from folks, including a few friends.

Then I checked https://indieweb.social/tags/earthquake and it has plenty of recent #fediverse posts about the earthquake, several @sfba.social.

Feels like something big has shifted.

The #federated #IndieWeb has replaced another #socialMedia silo use-case.

This is post 7 of #100PostsOfIndieWeb. #100Posts

← https://tantek.com/2024/027/t1/indieweb-ideals-systems-swappable
→ 🔮

Post glossary:

silo
https://indieweb.org/silo
social media
https://indieweb.org/social_media
use-case
https://indieweb.org/use_case

Tantek ()'s status on Sunday, 31-Dec-2023 17:04:00 EST

Tantek

Writing about writing: capture first, edit & publish later.

Braindump timely thoughts & experiences into as many draft notes as it takes, while ideas & memories are fresh.

Collecting higher fidelity memories seems more important than editing past writings or finishing/polishing a post for publishing, which can be done at a later time.

Sometimes the passage of time helps provide insights and broader understandings that can help with writing more effective posts, from better summaries to narratives that help sense-making.

Bits of even this minor post sat for weeks, and only today did I add a summary and related thoughts.

Similarly, it makes sense to edit and publish small notes on a subject, without feeling compelled to turn them into a larger blog post, or a longer list of points.

This is a key advantage to publishing on your own #indieweb site, you decide on the granularity of your posts, small, medium or large, instead of being constrained, burdened, or pressured by any particular #socialMedia user interface, character count limitation, or audience expectation.

Like Twitter before it, even the default #Mastodon user interface has limitations, and the #fediverse itself as a whole has audience/cultural expectations (certainly quite a few articles have been written about that).

On your own site you decide if you want to publish a post to make one point, or mention a related point or two, or collect things into a list or longer article, or eventually all of the above.

On your own site you feel more free to prioritize and share what is on your mind, instead of feeling compelled to first respond to whatever topics are trending, or to whatever you happen to read in your algorithmic feed.

#writingAboutWriting

This is day 47 of #100DaysOfIndieWeb. #100Days

← Day 46: https://tantek.com/2023/289/t1/bridgyfed-webmention-like-fediverse
→ Day 48: https://tantek.com/2023/365/t2/no-large-language-model-llm-used

Related:
* “More Thoughtful Reading & Writing on the Web” (https://tantek.com/2023/277/b1/thoughtful-reading-writing-web)

Post glossary:

algorithmic feed
https://indieweb.org/algorithmic_feed
article
https://indieweb.org/article
note
https://indieweb.org/note
post
https://indieweb.org/post
sense-making
https://en.wikipedia.org/wiki/Sensemaking_(information_science)
social media
https://indieweb.org/social_media

Tantek ()'s status on Monday, 23-Oct-2023 20:30:00 EDT

Tantek

Great article on #POSSE by David Pierce (@davidpierce@mastodon.social @pierce) @Verge:

https://www.theverge.com/2023/10/23/23928550/posse-posting-activitypub-standard-twitter-tumblr-mastodon

Several key points of POSSE explained in the article:

First, post on your own site:

“In a POSSE world, everybody owns a domain name, and everybody has a blog. (… a place on the internet where you post your stuff and others consume it.)”

Second, syndicate elsewhere, appropriately for each destination:

“Then, your long blog post might be broken into chunks and posted as a thread on X and Mastodon and Threads. The whole thing might go to your Medium page and your Tumblr and your LinkedIn profile, too. If you post a photo, it might go straight to Instagram, and a vertical video would whoosh straight to TikTok, Reels, and Shorts. Your post appears natively on all of those platforms,”

You can use Bridgy Publish (https://brid.gy/) to POSSE to many destinations, and Bridgy Fed (https://fed.brid.gy/) to #federate to #Mastodon and other #fediverse destinations, directly from your site instead of posting a copy on yet another account on yet another server.

Third, and this is a key piece that distinguishes proper POSSE setups, with original post perma(short)links back to your posts on your domain:

“typically with some kind of link back to your blog.”

All copies link to (your) home.

"And your blog becomes the hub for everything, your main home on the internet."

You have power over your domain (name), not outside silos.

David embedded a screenshot of one of my posts, a reply post:

in which I posted a reply *on my own site*¹ to @Zeldman.com’s tweet (itself a reply to a POSSE copy of one of my posts), and POSSEd my reply to Twitter so it would thread with his reply.

This illustrates another important detail of a proper POSSE setup:

Fourth, post *replies* and other responses from your own site, whether to other #IndieWeb sites, or to others’s silo posts (tweets etc.).

Own your data means owning your replies as well.

David also noted several challenges and good questions about POSSE. Some of these have answers & established practices, others are areas of exploration. E.g.

"The first is the social side of social media: what do you do with all the likes, replies, comments, and everything else that comes with your posts?"

The short answer is #backfeed: https://indieweb.org/backfeed

Backfeed is a concept I first wrote about as “reverse syndication”².

As you syndicate your posts out to #socialMedia silos, you reverse syndicate any responses there back to your original post.

Your site can do this with a service like #Bridgy, which uses the #Webmention standard to forward such silo responses back to your site, and #BridgyFed which does same for responses from Mastodon to your #federated posts.

David asked many other questions, which are deserving of their own posts to help answer, so I’ll leave you with just one more:

"The most immediate question, though, is simply how to build a POSSE system that works."

The short answer is: just start³.

Even if you have to do it manually (until it hurts), even if you have to edit your posts on a static GitHub site (behind your domain name of course), and then copy & paste to your silo(s) of choice, just start.

By practicing POSSE, even manually, you will learn what aspects of POSSE & backfeed matter the most to you, what aspects actually involve reaching & responding to friends and others you care about.

By doing so you will naturally focus on setting up & making what you need, and you too can join the future of web publishing, today.

Questions? Join us in the chat: https://chat.indieweb.org/ (also on Discord, IRC, and Slack⁴)

This is day 46 of #100DaysOfIndieWeb. #100Days

← Day 45: https://tantek.com/2023/289/t1/bridgyfed-webmention-like-fediverse
→ 🔮

Post glossary:

backfeed / reverse syndication
https://indieweb.org/backfeed
Bridgy
https://brid.gy/
make what you need
https://indieweb.org/make_what_you_need
manual (until it hurts)
https://indieweb.org/manual_until_it_hurts
original post link
https://indieweb.org/original_post_link
own your data
https://indieweb.org/own_your_data
own your replies
https://indieweb.org/own_your_replies
permalink
https://indieweb.org/permalink
permashortlink
https://indieweb.org/permashortlink
POSSE
https://indieweb.org/POSSE
silo
https://indieweb.org/silo
social media
https://indieweb.org/social_media
static site
https://indieweb.org/static_site
start
https://indieweb.org/start
Webmention
https://indieweb.org/Webmention

¹ https://tantek.com/2023/253/t2/
² https://tantek.com/2010/034/t2/diso-2-personal-domains-shortener-hatom-push-relmeauth
³ https://tantek.com/2023/001/t1/own-your-notes
⁴ https://indieweb.org/discuss

Tantek ()'s status on Monday, 08-May-2023 19:46:00 EDT

Tantek

I am running for election in this month’s #W3C (@w3.org @w3c@w3c.social @w3c) Advisory Board (AB) election¹ and blogged my personal statement: https://tantek.com/2023/128/b1/running-for-w3c-advisory-board-ab-election

@fantasai.inkedblade.net (@fantasai@w3c.social @fantasai) is also running for the #W3CAB, and admirably blogged her imminent affiliation change *before* the election started: https://fantasai.inkedblade.net/weblog/2023/affiliation-change/ — Congrats Elika! Your new affiliation is lucky to have you.

In addition to the two of us, @cwilso.com (@cdub@mastodon.social @cwilso) also posts on his own blog and is running for the AB.

Those are the three candidates I know have their own personal #website, and was able to verify by searching for candidates on the web, #socialMedia, etc.

Three out of the nine candidates² running for election to the World Wide Web Consortium’s Advisory Board.

As I wrote in my statement:

> “I believe governance of W3C, and advising thereof, is most effectively done by those … who directly use & create on the web using W3C standards. This direct connection to the actual work of the web and W3C is essential to prioritizing the purpose & scope of governance thereof.”

I firmly believe that direct hands-on experience with using the web, beyond reading the web or using someone else’s apps, actually writing to the web, posting on the web, creating for the web, provides better insight into the technologies & standards necessary to evolve the web, how to improve them and represent the communities working on them.

I ask for your support for the Advisory Board, and support for those who create on the web.

If any other candidates have their own #IndieWeb site (or set one up!), and especially if they blog their personal statements, I will gladly link to them as well.

Thanks for your consideration.

¹ https://www.w3.org/blog/news/archives/9903
² https://www.w3.org/2023/04/ab-nominations.html

Tantek ()'s status on Thursday, 20-Apr-2023 20:57:00 EDT

Tantek

In https://www.theverge.com/2023/4/20/23689570/activitypub-protocol-standard-social-network, author @pierce@mas.to does an excellent job covering a broad range of #ActivityPub related updates, and goes beyond the usual #Mastodon focus to describe numerous implementations.

I was very happy to see that he also clearly communicated several #IndieWeb principles¹, practices, goals, and reasons why². Like this quote:

“But the advice you’ll hear from most people in this space is this: own your own domain. Don’t be john@/mastodon.social or anna@/facebook.com. Have a space that is yours, that belongs to you, a username and identity that can’t disappear just because a company goes out of business or sells to a megalomaniac.”

and this:

“It’s [your own domain is] your YouTube channel name and your TikTok username and your Instagram handle and your phone number and your Twitter @, all in one name.”

Great interviews with @stevetex@mozilla.social, @mike@flipboard.social, @dustycloud.org (@cwebber@octodon.social), @evanp.me (@evan@cosocial.ca), @anildash.com (@anildash@me.dm), @coachtony@me.dm, and @manton.org.

As Manton said in the article:

“If you solve identity with domain names, it makes things easier because it fits the way the web has been for 20 years,”

Pierce also noted:

“you might soon be able to turn your personal website into your entire social identity online”

Already can.

I replied to Pierce’s post³ about his article noting this⁴, from #federating directly from my website for the past ~6 months⁵, to over a decade of using it as my social identity with the POSSE method⁶ with various #socialMedia silos.

It’s important enough that I’ll repeat part of Pierce’s quote at the top:

“own your own domain. Don’t be john@/mastodon.social or anna@/facebook.com. Have a space that is yours”

He gets it. Don’t be someone at someone else’s server.

Big Chad or Little Chad’s garages⁷ are social media stepping stones towards owning your own domain and IndieWeb presence.

We’re here when you’re ready to take that next step: https://chat.indieweb.org/

This is day 38 of #100DaysOfIndieWeb. #100Days

← Day 37: https://tantek.com/2023/109/t2/years-ago-first-federated-indieweb-thread
→ 🔮

¹ https://indieweb.org/principles
² https://indieweb.org/why
³ https://mas.to/@pierce/110231624819547202
⁴ https://tantek.com/2023/110/t1/
⁵ https://tantek.com/2022/301/t1/twittermigration-bridgyfed-mastodon-indieweb
⁶ https://indieweb.org/POSSE
⁷ https://tantek.com/2023/001/t1/own-your-notes

Tantek ()'s status on Wednesday, 22-Mar-2023 11:14:00 EDT

Tantek

Watching #MozFest session Dialogues & Debates: Making the Fediverse¹ and panelist @stevetex@mozilla.social (@stevetex) just announced that we (#Mozilla) are standing up a #Mastodon instance², starting with limited sign-ups.

I’m excited that Mozilla is experimenting with #socialWeb alternatives to centralized #socialMedia silos.

There are many #Mozillians with #fediverse addresses you can follow:
* https://wiki.mozilla.org/Mastodon

Several of these folks also have their own #IndieWeb sites.

It’s interesting seeing how people are individually choosing to use a fediverse address on someone else’s server, vs their own server like with a subdomain, vs just using their existing site.

One trend I have seen is people using someone else’s Mastodon server as a stepping stone, a learning experience, before migrating to either self-hosting Mastodon (or an easier to run alternative like microblog.pub ³, not to be confused with micro.blog ⁴), or ideally directly using their own site, blog etc. to connect to the fediverse⁵.

Do you have an @-@ address and want to use your own site instead?

If you’re a #webdev, you can totally do this by connecting your existing personal site with https://fed.brid.gy/ and own your presence on the web, social web, fediverse all at one place.

Got questions? Drop by the IndieWeb chat! https://chat.indieweb.org/dev

This is day 35 of #100DaysOfIndieWeb #100Days

← Day 34: https://tantek.com/2023/072/t1/blog-as-if-ai-trained-posts
→ 🔮

¹ https://schedule.mozillafestival.org/session/UEEGYL-1
² https://mozilla.social/
³ https://indieweb.org/microblog.pub
⁴ https://indieweb.org/micro.blog
⁵ https://tantek.com/2022/301/t1/twittermigration-bridgyfed-mastodon-indieweb

Tantek ()'s status on Wednesday, 22-Mar-2023 11:14:00 EDT

Tantek

Watching #MozFest session Dialogues & Debates: Making the Fediverse¹ and panelist @stevetex@mozilla.social (@stevetex) just announced that we (#Mozilla) are standing up a #Mastodon instance², starting with limited sign-ups.

I’m excited that Mozilla is experimenting with #socialWeb alternatives to centralized #socialMedia silos.

There are many #Mozillians with #fediverse addresses you can follow:
* https://wiki.mozilla.org/Mastodon

Several of these folks also have their own #IndieWeb sites.

It’s interesting seeing how people are individually choosing to use a fediverse address on someone else’s server, vs their own server like with a subdomain, vs just using their existing site.

One trend I have seen is people using someone else’s Mastodon server as a stepping stone, a learning experience, before moving to either self-hosting Mastodon (or an easier to run alternative like microblog.pub ³, not to be confused with micro.blog ⁴), or ideally, directly using their existing site, blog etc. to connect to the fediverse⁵.

Do you have an @-@ address and want to use your own site instead?

If you’re a #webdev, you can totally do this by connecting your existing personal site with https://fed.brid.gy/ and own your presence on the web, social web, fediverse all at one place.

Got questions? Drop by the IndieWeb chat! https://chat.indieweb.org/dev

¹ https://schedule.mozillafestival.org/session/UEEGYL-1
² https://mozilla.social/
³ https://indieweb.org/microblog.pub
⁴ https://indieweb.org/micro.blog
⁵ https://tantek.com/2022/301/t1/twittermigration-bridgyfed-mastodon-indieweb

Tantek ()'s status on Tuesday, 17-Jan-2023 12:05:00 EST

Tantek

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

Tantek ()'s status on Saturday, 14-Jan-2023 02:39:00 EST

Tantek

Your #IndieWeb site can be the home you’ve always wanted on the internet.

While posting on a personal site has many^1 advantages^2 over only posting to #socialMedia, maybe you already quit social media silos^3.

There are lots of reasons to get a domain name^4 and setup your own homepage on the web.

If you’re a web professional, a personal site with your name on it (perhaps also in its domain) can make it easier for potential employers to find you and read your description in your own words.

If you’re a web developer, a personal home page is also an opportunity to demonstrate your craft.^5

If you’re a writer, you can organize your words, essays, and longer form articles in a form that’s easier for readers to browse, and style them to both be easier to read, and express your style better than any silo.

Similarly if you’re an artist, photographer, or any other kind of content creator.

See https://indieweb.org/homepage for more reasons why, and what other kinds of things you can put on your home page.

Thanks to Chris Aldrich (https://boffosocko.com/) for the header image.

This is day 13 of #100DaysOfIndieWeb #100Days.

← Day 12: https://tantek.com/2023/012/t1/six-years-webmention-w3c
→ 🔮

^1 https://tantek.com/2023/001/t1/own-your-notes
^2 https://tantek.com/2023/005/t3/indieweb-simpler-approach
^3 https://indieweb.org/silo-quits
^4 https://tantek.com/2023/004/t1/choosing-domain-name-indieweb
^5 https://indieweb.org/creator

Tantek ()'s status on Sunday, 08-Jan-2023 23:43:00 EST

Tantek

11 years ago today, Ryan Barrett (https://snarfed.org/ @schnarfed) launched Bridgy (https://brid.gy/) to copy #socialmedia replies as comments on original blog posts.

This meant those of us building #IndieWeb sites could use a service for that functionality, instead of having to write code ourselves, for each proprietary API.

When a few of us originally started syndicating to silos (https://indieweb.org/POSSE), and sometimes reverse-syndicating replies (https://indieweb.org/backfeed), we had to write custom code to do so, calling each social media API (like Twitter) both ways.

Bridgy alleviated some of that burden, and over time added support for more silos, sometimes dropping support when they were shutdown (Google+, Buzz) or scuttled their APIs (Facebook).

While Bridgy started only with backfeed as a service, it eventually added publishing support, POSSE as a service.

Even though I already had code working to POSSE text notes to Twitter, when I added photo posting support to my site, rather than write more code to call Twitter’s API, I started conditionally using Bridgy Publish to POSSE my photo (and video) posts.

In 2017, Ryan launched Bridgy Fed (https://fed.brid.gy) which he has substantially improved in the past few months.

I and many others now use Bridgy Fed to broadcast to & interact with Mastodon (and other ActivityPub) servers, without having to write any ActivityPub, Webfinger etc. code ourselves.

https://tantek.com/2022/301/t1/twittermigration-bridgyfed-mastodon-indieweb

Every user of Bridgy Fed gets a nice dashboard for notifications and activity. Here’s mine: https://fed.brid.gy/user/tantek.com

Bridgy is a great example of a project that was started to fulfill a personal need (https://indieweb.org/make_what_you_need), growing to support broader community needs.

Read more about Bridgy & Bridgy Fed:
* https://indieweb.org/Bridgy (including Publish)
* https://indieweb.org/Bridgy_Fed
* Launch post: https://snarfed.org/2012-01-08_bridgy_launched

It’s this hybrid of encouraging personally relevant work and community contributions that makes the #IndieWeb community special.

Yes there is a focus on greater independence with your personal website. However we can all do more by working together.

We achieve more independence, more quickly, by collaborating in community.

This is day 8 of #100DaysOfIndieWeb #100Days.

← Day 7: https://tantek.com/2023/007/t2/more-100daysofindieweb-projects
→ 🔮

Tantek ()'s status on Thursday, 27-Aug-2020 20:38:00 EDT

Tantek

I believe in the #webPlatform (#EngineDiversityAbsolutist)
And the web as *your platform* (#IndieWeb over #BigTech #socialMedia corporate web)

#webDeveloper @ohhelloana @smashingmag:
“Autonomy Online: A Case For The IndieWeb” https://www.smashingmagazine.com/2020/08/autonomy-online-indieweb/

Tantek ()'s status on Sunday, 08-Mar-2020 21:03:00 EDT

Tantek

Freshly posted: Toward a More Civil and Social Web
@optoutools founder Teresa’s keynote @IndieWebCamp Berlin last November

12:10s video: https://archive.org/details/iwcberlin2-keynote-teresaingram

#AI #AIEthics #NLP #machineLearning #socialWeb #socialMedia #TechIsNotNeutral #IWD2020

Must see for anyone desiging/building tech for humans.

Tantek ()'s status on Saturday, 22-Feb-2020 11:47:00 EST

Tantek

Great first #IndieWebCampAustin keynote by Natalie on the upsides and downsides of #socialmedia, how she started her #IndieWebGratitude Joural@microdotblog, did #DeleteFacebook, yet still posts@Instagram, though with a much more limited circle.

Tantek ()'s status on Thursday, 19-Dec-2019 13:54:00 EST

Tantek

I have repeatedly expressed to peers working on #IndieWeb #SocialWeb #SocialMedia #FederatedSocialWeb that tech/plumbing-centric framing of #dweb "Decentralized Web" "Distributed Web" is heavily problematic. Beyond MastoGab, there is now something much worse (not linking). I’ll follow up with a longer blog post (it’s been in my drafts for a while), explaining why, how we got here, and maybe some ways for how can we replace use of "Decentralized Web" or "Distributed Web" with something human-centric instead.

For a start, re-read Mozilla’s Manifesto and Principles:

https://www.mozilla.org/en-US/about/manifesto/

Tantek ()'s status on Friday, 15-Feb-2019 21:22:00 EST

Tantek

#IndieWebCamp#Austinis next weekend!
Get a #website, #ownyourdata, cut back #socialmedia, or hack on #dweb#webstandards.
Join@manton2(@microdotblog)@aaronpk(#indieauth #webmention)@dshanske(#WordPress #IndieWeb) & more!

RSVP:https://2019.indieweb.org/austin

majestyx (majestyx)'s status on Tuesday, 21-Jul-2015 16:36:07 EDT

majestyx

Public

Notices tagged with socialmedia