I updated my homepage to show the latest photo post: gregorlove.com/#photos

I added a "Guestbook" to my personal site!

Feel free to drop by and sign it however you please:

https://foreverliketh.is/docs/assortments/guestbook/

Also open to any thoughts / suggestions on its implementation.

#webdev #web #indieweb #website #hugo

New Core Intuition! We talk about marketing and upcoming app plans. I also fixed a feed issue in Micro.blog with it, so posts will start flowing into @coreint@micro.blog again for fediverse folks who want to follow along.

Are there any other indie web makers on Mastodon making cool things?

#indieweb #indie #maker

I'm dying! The Normal Gossip Podcast described 90s internet as

"a magical, lawless land where fewer parts of the internet were centralized so that 4 men could make a lot of money"

#internet #indieweb

One way of getting to know me is my writing and my talks.

Here is a selection of posts within the areas of Digital Ethics, Human Rights, Usability, Accessibility and more – all with a leaning towards design and communication theory.

The Elements of Digital Ethics
AI and Human Rights - video and transcript
The Trouble Diamond
Design for Universal Wellbeing
The world map that reboots your brain
The slavery supported by that device in your pocket
Tech addiction: Why it matters
Digital Compassion: A Human Act
Fairy tale experiences talk at UXLx - my first talk on design ethics in front of an international audience
25 years of online resilience - a newsletter about #indieweb
Digital abuse is hard to leave – by design

I teach, consult and write about these issues. If you want to know more, don’t hesitate to contact me.

#Introduction #DigitalEthics

🎉 Six years ago today, the #IndieWeb Webmention protocol was published as a W3C REC https://www.w3.org/TR/webmention/

A key social web building block, Webmention enabled peer-to-peer comments, likes, and other responses to be created, updated, and deleted across the web, by both dynamic & static websites.

It was accompanied by a report of over a dozen implementations that demonstrated interoperability: https://webmention.net/implementation-reports/summary/ using an open test suite: https://webmention.rocks/ that is still up and running and used by developers today.

Many many more implementations have been developed, open sourced, shipped, launched since. The specification itself has a webmention endpoint and accepts webmentions.

Exactly a year before that, Webmention was published as a First Public Working Draft by the W3C Social Web Working Group: https://www.w3.org/TR/2016/WD-webmention-20160112/

It took the best parts of the prior Pingback protocol, simplified it (ditched XML-RPC), made it more secure, separated presentation from plumbing, and added update & delete semantics.

It was in many ways a model for how open web standards should be developed.

See the wiki page for an overview and numerous screenshots of implementations: https://indieweb.org/Webmention

If you want to implement Webmention yourself, there are now numerous developer resources to do so.

Start here: https://indieweb.org/Webmention-developer and come say hi at the IndieWeb development chat channel: https://chat.indieweb.org/dev

Previously, previously, previously:
* https://tantek.com/2020/012/t1/happy-birthday-webmention
* https://tantek.com/2018/012/t1/anniversary-million-webmentions
* https://tantek.com/2017/012/t1/webmntion-first-w3c-recommendation-high-bar

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

← Day 11: https://tantek.com/2023/011/t1/indieweb-evolving-at-mention
→ 🔮
#IndieWeb #100DaysOfIndieWeb #100Days

I was able to get my #100DaysofIndieweb post today in just under the wire. I was actually able to write it from my phone!

Have a look here: https://crowdersoup.com/posts/projects/indieweb/100-days/day-7-posting-from-my-phone/

#indieweb

Someone should create a service that enables people to establish and retain an identity in the Fediverse. Its great that you can move from instance-to-instance on Mastodon, with redirection, but it would be better if the instance that a user was on was largely irrelevant.

You should be “@ user @ your domain” and seamlessly be able to change backend instances.

opened: Memento Mori, the Yami no Matsuei fanlisting
http://hoshi.nu/yamimatsu/

...okay, it's 3AM, I'm exhausted, bedtime nao.

#YaminoMatsuei #YamiMatsu #fanlisting #fansite #staticwebsite #oldweb #handmadehtml #indieweb #retroweb

I think an often-overlooked tool for us alternative-platform users is bridging/syndication. Not everyone agrees on what platforms to use, and that's okay.

How do we resolve disagreements in platform choice? By bridging between them! We must accept disagreements in choice.

Also known as: https://indieweb.org/bridge_all_the_things

i.e. Philosophies must be progressive -- not in the political sense, but in the "don't expect everyone to use the same platform" sense.

#SocialCoding #IndieWeb #Fediverse

Medium embraces Mastodon

I’ll be watching as Medium runs their own Mastodon instance. I like my approach better: integrating ActivityPub directly into the blog platform, not alongside it as a separate platform. But there’s no single right way to do this.

The #indieweb social scene is jumping this morning. On Twitter at https://twitter.com/faebornofficial, is mostly the one retweeting all of them. I run that account, by the way.

One of the fun things about #IndieWeb notes & replies is that how we post is actively evolving! Like how should we @ someone?

#socialMedia aliases (e.g. @Twitter) were obvious, with prior @-name usage on Flickr etc.

Now, some have a domain, or an @-@ (pronounced at-at, yes, just like the abbreviation for Imperial All Terrain Armored Transport^1), or some have both.

We can ask questions like why do we @-someone? What are the use-cases?
* In a reply to a public post, clearly express that you’re speaking to that person
* In a reply to a reply, that you’re speaking to everyone upthread (AKA a https://indieweb.org/canoe)
* When attributing something to someone (photo/post/cool thing by so-and-so), giving credit
* Distinguish a person (or something that can be followed) from “just” a site
* For all the above, notifying someone accordingly

Some ideas:

1. Ideally, if/when everyone has their own domain (where they receive Webmention notifications, and a feed you can follow), we can @-name their domain, which your auto-linker^2 should hyperlink accordingly, e.g.
* @aaronparecki.com @anomalily.net @Martymcgui.re@david.shanske.com @voxpelli.com @adactio.com @marcthiele.com @mxb.dev

These all look close enough to social media aliases/names that they’re immediately recognizable as readable @-names, a good consideration when choosing a domain name.^3

2. As a fallback (e.g. for non-@-domain-auto-linking destinations) we can use someone’s plain domain (explicitly with https:), especially if their home page still has a stream or feed you can follow, or maybe if they don’t receive homepage Webmentions (yet), e.g.:
* https://jacky.wtf/ https://tmichellemoore.com/ https://crowdersoup.com/

3. Some folks with personal sites have (for now) created separate Mastodon accounts (or installed an instance on a subdomain), and for them, we can reference their @-@ parenthetically after their domain, like:
* https://kevinmarks.com/ (@kevinmarks@xoxo.zone), https://dangillmor.com/ (@dangillmor@mastodon.social), https://simonwillison.net/ (@simon@simonwillison.net)

Rather than using social media silo @-names (except when explicitly replying to a silo), I’m now experimenting with all three of these (1-3) instead, both to elevate people’s IndieWeb identities, and for Mastodon viewers, provide a convenient way to follow @-@ addresses.

If someone’s homepage receives Webmentions, they will get notified when I @-mention them by domain.

I recently implemented syntactic auto-linking of @-@ addresses like this:
* @user@example.com --> https://example.com/@user
with a special case for @-domain@-domain to just link to the domain, e.g.:
* @tantek.com@tantek.com --> https://tantek.com/

I also made a recent policy decision to auto-link all @-@ (and @-domain) mentions to https:, the reasoning being that identities on the web should be using https.
* Testing in production here: https://tantek.com/cassis.js, search for "auto_link("

Some questions:
* Does/do Mastodon (or other ActivityPub servers) notify people when you @-@ mention them in a post? How? Who’s responsible for that?
* Will Bridgy Fed notify the servers (deliver to AP inboxes) of folks I merely @-@ mention (rather than explicit replies, reposts)? Should it?

So many people are switching to using their personal domains to post (or at least a Mastodon account) that I no longer feel compelled to @-mention people’s Twitter handles in posts, which feels refreshing.

Now the fun part is experimenting and figuring out what combination of @-domain, plain domain, or @-@ mentions looks good, makes sense to people, and sends notifications to people the way they want to receive them.

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

← Day 10: https://tantek.com/2023/010/t2/build-use-services
→ 🔮

^1 https://en.wikipedia.org/wiki/AT-AT
^2 My https://tantek.com/github/cassis/blob/master/cassis.js auto_link() function supports @example.com auto-linking, yours should too.
^3 https://tantek.com/2023/004/t1/choosing-domain-name-indieweb
#IndieWeb #socialMedia #100DaysOfIndieWeb #100Days

Morning everybody. This function is giving me fits, but I will continue tackling it this morning to get a working importer for scrobbles from Last FM as listen posts to my site. #indieweb

One of the fun things about #IndieWeb notes & replies is that we're still figuring things out! Like how should we @ someone?

#socialMedia aliases (e.g. @Twitter) were obvious, with prior @-name usage on Flickr etc.

Now, some have a domain, or an @-@ (pronounced at-at, yes, just like the abbreviation for Imperial All Terrain Armored Transport^1 walkers), or some have both.

We can ask the questions of why do we @-someone? What are the use-cases?
* In a reply to a public post, clearly express that you’re speaking to that person
* In a reply to a reply, that you’re speaking to everyone upthread (AKA a https://indieweb.org/canoe)
* When attributing something to someone (photo/post/cool thing by so-and-so), giving credit
* For all the above, notifying someone accordingly
* Distinguish a person (or something that can be followed) from “just” a site

Some ideas:

1. Ideally, if/when everyone has their own domain (where they receive Webmention notifications, and a feed you can follow), we can @-name their domain, which your auto-linker^2 should hyperlink accordingly, e.g.
* @aaronparecki.com @anomalily.net @Martymcgui.re@david.shanske.com @snarfed.org @ben.thatmustbe.me

These all look close enough to social media aliases/names that they’re immediately recognizable as readable @-names, a good consideration when choosing a domain name.^3

2. As a fallback (e.g. for non-@-domain-auto-linking destinations) we can use someone’s plain domain (explicitly with https:), especially if their home page still has a stream or feed you can follow, or maybe if they don’t receive homepage Webmentions, e.g.:
* https://adactio.com https://marcthiele.com https://mxb.dev/

3. Some folks with personal sites have (for now) created separate Mastodon accounts (or an installed an instance on a subdomain), and for them, we can reference their @-@ parenthetically after their domain, like:
* https://kevinmarks.com/ (@kevinmarks@xoxo.zone), https://tmichellemoore.com/ (@tmichellemoore@mastodon.social), https://voxpelli.com/ (@voxpelli@mastodon.social), https://simonwillison.net/ (@simon@simonwillison.net)

Rather than using social media silo @-names (except when explicitly replying to a silo), I’m now experimenting with all three of these (1-3) instead, both to elevate people’s IndieWeb identities, and for Mastodon viewers, provide a convenient way to follow @-@ addresses.

If someone’s homepage receives Webmentions, they will get notified when I @-mention them by domain.

I also recently implemented syntactic auto-linking of @-@ addresses like this:
* @user@example.com --> http://example.com/@user
with a special case for @-domain@-domain to just link to the domain, e.g.:
* @tantek.com@tantek.com --> http://tantek.com/

I am considering switching these (as well as a plain @-domain) to auto-link to https: instead, the reasoning being we should expect that identities on the web should be using https.

Some questions:
* Does/do Mastodon (or other ActivityPub servers) notify people when you @-@ mention them in a post? How? Who’s responsibility is that?
* Will Bridgy Fed notify the servers (deliver to AP inboxes) of folks I merely @-@ mention (rather than explicit replies, reposts)? Should it?

So many people are switching to using their personal domains to post (or at least a Mastodon account) that I no longer feel compelled to @-mention people’s Twitter handles in posts, which feels refreshing.

Now the fun part is experimenting and figuring out what combination of @-domain, plain domain, or @-@ mentions looks good, makes sense to people, and sends notifications to people the way they want to receive them.

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

← Day 10: https://tantek.com/2023/010/t2/build-use-services
→ 🔮

^1 https://en.wikipedia.org/wiki/AT-AT
^2 My https://github.com/tantek/cassis/blob/master/cassis.js auto_link() function supports @example.com auto-linking, yours should too.
^3 https://tantek.com/2023/004/t1/choosing-domain-name-indieweb
#IndieWeb #socialMedia #100DaysOfIndieWeb #100Days