Show Navigation
Conversation
Notices
-
#TwitterMigration, first time?
Have posted notes at https://tantek.com/ since 2010, syndicated tweets & an #AtomFeed.
Added one .htaccess line, thanks to #BridgyFed, if you use #Mastodon, you can follow my #IndieWeb site:
@tantek.com@tantek.com
Which demonstrates both the redundancy & awkwardness (it’s not a clickable URL) of such @-@ (AT-AT) usernames.
Like why make me type or show “@tantek.com” twice like that?
Why can’t Mastodon follow a username of “@tantek.com”? Or just “tantek.com”?
And either way expanding it internally if need be to the AT-AT syntax.
Why this regression from what we had with classic feed readers where a domain was enough to discover & follow a feed?
Also, why does following show a blank result?
Contrast that with classic feed readers which immediately show you the most recent items in a feed you subscribed to.
Lastly (for now), I asked around and no one knew of a simple public way to “preview” or “validate” that @tantek.com@tantek.com actually “worked”. You have to be *logged-in* to a Mastodon instance and search for a username to check to see if it works.
Contrast that with https://validator.w3.org/feed/ which you can use without any log-in to validate that your classic feed file works.
Why these regressions from the days of feed readers?