Show Navigation
Notices tagged with indieweb, page 5
-
Once you have a domain^1, and connect it to an #IndieWeb service like https://micro.blog, or a https://indieweb.org/CMS on https://indieweb.org/web_hosting, you can focus^2 on your writing.
Or if you enjoy #webDevelopment and want to build (option three^3), use developer services to more rapidly add IndieWeb building blocks^4 to your site so you too can focus on creating & owning your content^5.
Here are some of the most common and popular developer services:
1. Webmention sending: https://webmention.app/ by https://remysharp.com/ (@rem@front-end.social), or https://mention.tech/ by https://kevinmarks.com/ (@kevinmarks@xoxo.zone)
2. Webmention receiving: https://webmention.io/ (I use this) by https://aaronparecki.com/ or https://webmention.herokuapp.com/ by https://voxpelli.com/ (@voxpelli@mastodon.social)
3. POSSE & backfeed: https://brid.gy/ by Ryan of https://snarfed.org/ (@schnarfed)
4. ActivityPub federating: https://fed.brid.gy/ also by Ryan. More on Bridgy & Bridgy Fed^6.
Using a developer service to support IndieWeb protocols saves you time. You can also contribute to the community by filing suggestions for improvements, or participating on their GitHub repositories.
If you prefer that your site not depend on any external services, you can do that too.
Most of the above services are also open source that you can install and fully manage yourself. For example:
* Webmention installable services: https://indieweb.org/Webmention#Publisher_Services
Another option is to use one of many open source libraries to more rapidly implement support for IndieWeb standards^7. The wiki pages for each standard list libraries in a variety of programming languages, e.g.:
* https://indieweb.org/Webmention-developer#Libraries
If you choose the path of installing or building something new with libraries or by directly implementing an IndieWeb standard, be sure to test your implementation with its test suite, e.g.:
* https://webmention.rocks/
As a web developer, you can choose how much of your #IndieWeb support you want to implement yourself (and time to invest) vs build on the services, libraries, and other open source that the community has produced and is actively supporting.
This is day 10 of #100DaysOfIndieWeb #100Days.
← Day 9: https://tantek.com/2023/009/t2/edit-reply-comment-update
→ 🔮
^1 https://tantek.com/2023/004/t1/choosing-domain-name-indieweb
^2 https://tantek.com/2023/005/t3/indieweb-simpler-approach
^3 https://tantek.com/2023/003/t1/indieweb-path-chosen-why
^4 https://indieweb.org/building_blocks
^5 https://tantek.com/2023/001/t1/own-your-notes
^6 https://tantek.com/2023/008/t7/bridgy-indieweb-posse-backfeed
^7 https://spec.indieweb.org/
-
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
→ 🔮
-
There are more 2023 #100DaysOfIndieWeb projects, you should check them out:
* https://tmichellemoore.com/blog/tag/100daysofindieweb/ (@tmichellemoore@mastodon.social)
* https://crowdersoup.com/tags/100days (@CrowderSoup@hachyderm.io)
Got one? Reply and I'll add it.
You can (re)start a #100Days project any day. While continuity is nice, you can take breaks. As https://kevinmarks.com/ (@kevinmarks) said in #IndieWeb chat:
* https://indieweb.org/life_happens and should take priority over artificial deadlines.
It all started back in 2017 when https://aaronparecki.com/ did the first #100DaysOfIndieWeb project:
* https://aaronparecki.com/tag/100daysofindieweb
* @100daysindieweb
Want to start one of your own? See past & present IndieWeb related 100 days projects for ideas & inspiration:
* https://indieweb.org/100_days
This is day 7 of #100DaysOfIndieWeb.
← Day 6: https://tantek.com/2023/006/t1/forward-in-time-links
→ 🔮
-
https://dangillmor.com/ wishes for "forward-in-time links so we could read … his 2023 #100Days project, #100DaysOfIndieWeb … more easily from the beginning" https://mastodon.social/@dangillmor/109646621709452885
Great suggestion Dan. Wish granted.
On my #IndieWeb site, I control the user experience.
Since 2010^1, I’ve had previous/next ( ← → ) temporal^2 navigation links on the top right of my post permalinks, across all posts (something I always wanted on my notes, and Twitter lacked)
In 2018^3, I added similar ( ← → ) links on day archive pages, for previous/next days.
Ideally I’d build similar automatic ( ← → ) links for each hashtag in a post, for the previous/next post with that same hashtag.
OR for now I could manually add forward-in-time links to the bottom of my five previous #100DaysOfIndieWeb posts, and with each subsequent post, remember to update the previous one.
So that’s what I did, am doing, per https://indieweb.org/manual_until_it_hurts.
Previous #100DaysOfIndieWeb posts updated.
This is day 6 of #100DaysOfIndieWeb #100Days, which is now a https://en.wikipedia.org/wiki/Doubly_linked_list
← Day 5: https://tantek.com/2023/005/t3/indieweb-simpler-approach
→ 🔮
Previously, previously, previously:
^1 https://tantek.com/2010/032/t7/inventions-to-tweet-from-site
^2 https://tantek.com/2011/102/t2/navigation-arrows-back-past-forward-future-ui-pattern
^3 https://tantek.com/2018/308/t2/indiewebcamp-archive-navigation-day-archives
-
The #IndieWeb approach *is* the simpler day-to-day approach.
Once you setup your domain & provider (or host/CMS), you always know where to post.
Your own site.
Write first, defer "destination decisions".
Create first, edit for audience(s) second.
It’s refreshing & liberating.
Whether text, photos, videos, podcasts, brief thoughts, thinking out loud, a considered essay or “thought piece”, or replies to any of the above, start with your own site.
Why burden yourself with having to decide what to post based on:
* Will this fit in 140^H^H^H 280 characters?
* Or 500?
* Does it need a title?
* Will my photos/videos fit their aspect ratio limits?
* Which four photos for this album? Or 10? What one aspect ratio to crop them all into?
* Will my video fit in 15, 30, 90, or 140 seconds?
* Will I upset Big Chad or be subject to selective enforcement of ever-changing policies?
* Can I edit my post after publishing?
By decoupling creating from “distribution”, or “audience”, or “reach”, or the size of someone else’s storage boxes, you are free to express your thoughts first, then optionally decide if you want to share them elsewhere and edit as necessary.
If you do want to syndicate (POSSE) your post, then you can decide:
* Where else to send your post
* Is it worth your time to edit your post for any particular destination
* … their content limits (number of characters/photos, or video length)
* … their audience expectations or terms of service sensitivities
Creating and editing are different mental tasks.
Decoupling them makes posting easier and you can do a better job at both.
You can defer destination decisions & editing to some point in the future entirely, when you feel it’s worth your time.
You decide how and when to spend time creating vs editing. You are in control.
This is day 5 of #100DaysOfIndieWeb #100Days
Day 4: https://tantek.com/2023/004/t1/choosing-domain-name-indieweb
-
Choosing a domain name is a key step toward getting your own #IndieWeb site. Like choosing an account name (chat, email, Mastodon) but global, feels more personal, and like more of a commitment. Six tips:
1. Use some form of your name (given & family), so you have a chance of having your site and posts show up when people search for you
2. Or a made-up nickname that fits you now and into the future
3. Something easily memorable, speakable, & spellable to better tell people in-person or on the phone (i.e. avoid "cute" or "weird" spellings like dropping vowels)
4. Use https://domai.nr/ to quickly try variants
5. Try to get a .com .net or .org, which are still seen as more legitimate. A .me is ok, as is your country/region (e.g. .us .uk .eu etc. see https://indieweb.org/ccTLD for more examples)
6. Shorter is better for many reasons: https://indieweb.org/short-domains
Once you find an available name, choose a domain registrar, which is like choosing a phone company, except there are more of them. Some recommendations: https://indieweb.org/personal-domain#Domain_Registrars
Got questions, or want more tips & opinions?
Ask in https://chat.indieweb.org/ — you’ll get a lot of sympathy & support as nearly everyone there has gone through this process, and many are eager to share their experiences to make it easier for new folks.
https://indieweb.org/naming is hard, it’s ok to ask for help.
This is day 4 of #100DaysOfIndieWeb #100Days
Day 3: https://tantek.com/2023/003/t1/indieweb-path-chosen-why
-
Is it hard to setup & use your own #IndieWeb site?
Depends on the path chosen, and why.
1 turnkey: get a https://micro.blog/ - easier than #Mastodon, works with
2 #webdev: install a https://indieweb.org/CMS - needs tech knowhow
3 builder: assemble https://indieweb.org/building_blocks as desired, experiment, iterate, and explore how deep the rabbit hole goes
All paths share perhaps the hardest part:
Picking a domain name. Next, tips for choosing one.
This is day 3 of #100DaysOfIndieWeb #100Days
Day 2: https://tantek.com/2023/002/t6/key-owning-notes-domain-name
-
Is it hard to setup & use your own #IndieWeb site?
Depends on the path choosen, and why
1 turnkey: get a https://micro.blog/ - easier than #Mastodon, works with
2 #webdev: install a https://indieweb.org/CMS - needs tech knowhow
3 builder: assemble https://indieweb.org/building_blocks as desired, experiment, iterate, and explore how deep the rabbit hole goes
All paths share perhaps the hardest part:
Picking a domain name. Next, tips for choosing one.
This is day 3 of #100DaysOfIndieWeb #100Days
Day 2: https://tantek.com/2023/002/t6/key-owning-notes-domain-name
-
The key to owning your notes is posting them with permalinks using a domain name you control. That’s it. https://indieweb.org/permalink
There are many providers, like https://micro.blog/, that happily enable using your own domain name for everything you post.
This gives you the ability to change your provider, while preserving your post permalinks. From the web’s perspective, your posts work just as they did before.
You are in control.
This is day 2 of #100DaysOfIndieWeb #100Days #IndieWeb. Day 1: https://tantek.com/2023/001/t1/own-your-notes
-
I am once again asking you to own your notes, rather than tweeting them into Big Chad's garage.
Maybe you left the big garage and now toot in your neighborhood Chad's garage. It's still someone else's garage. https://xkcd.com/1150 #IndieWeb
Maybe it was an easier first step to take. Time to take the next step, with your own domain, and a turnkey service like https://micro.blog/, or an https://indieweb.org/CMS if you prefer, or go full stack and make it yourself, using building blocks like https://indieweb.org/Indiekit. Just https://indieweb.org/start.
This is day 1 of my 2023 #100Days project, #100DaysOfIndieWeb, posting an #IndieWeb encouragement, tool, or tip at least once a day for 100 days, to setup and use your own personal site instead of someone else's garage.
In the theme of: https://indieweb.org/100_days#100_Days_of_IndieWeb
Previously: https://tantek.com/2022/001/t1/12-years-notes-my-site
-
upgraded my @BBEdit to v14. Thanks https://Barebones.com for a smooth & solid text editor for decades. Its HTML validator checks a/area/link rel for XFN values like rel=me (since 9.6.2).
Are there #microformats2 Clippings? Perhaps a holidays project, for h-card, h-entry, h-event, and other #indieweb building blocks.
Reference: https://www.bbeditextras.org/clipping-placeholder-reference/
How to: https://www.macworld.com/article/217200/how_to_create_and_use_bbedit_clippings.html
-
#indieweb 🤝 #fediverse
✨ https://werd.io/2022/the-fediverse-and-the-indieweb (@benwerd)
✨ https://catgirlin.space/posts/moving-to-the-fediverse-and-indieweb/
✨ https://tantek.com/2022/301/t1/twittermigration-bridgyfed-mastodon-indieweb
Previously: https://twitter.com/t/status/1586264352453427201, https://twitter.com/t/status/956436348361158658 #TwitterMigration #ActivityPub #SocialWeb #OpenStandards #OpenWeb
-
#indieweb 🤝 #fediverse
✨ https://werd.io/2022/the-fediverse-and-the-indieweb (@benwerd)
✨ https://catgirlin.space/posts/moving-to-the-fediverse-and-indieweb/
✨ https://tantek.com/2022/301/t1/twittermigration-bridgyfed-mastodon-indieweb
Previously: https://twitter.com/t/status/1586264352453427201, https://twitter.com/t/status/956436348361158658 #TwitterMigration #ActivityPub #SocialWeb #OpenStandards #OpenWeb
-
🎁 Happy December 1st and welcome to another year of the #IndieWeb Gift Calendar! (inspired by #advent calendars)
https://indieweb.org/2022-12-indieweb-gift-calendar
Thanks to https://martymcgui.re/ (@schmarty) for our first IndieWeb gift of the month!
-
🎁 Happy December 1st and welcome to another year of the #IndieWeb Gift Calendar! (inspired by #advent calendars)
https://indieweb.org/2022-12-indieweb-gift-calendar
Thanks to https://martymcgui.re/ (@schmarty) for our first IndieWeb gift of the month!
-
#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?
-
Published today: https://webvision.mozilla.org/
Years of working with co-workers @Mozilla, and something I’m proud of. #OpenWeb #IndieWeb fans & #webdevs see https://webvision.mozilla.org/full/ with #HTML #CSS #JS, nods to nascent #OpenUI @CSSWG #sustainability #s12y efforts, and a lot more.
-
Last month was the anniversary of two #IndieWeb #distributedWeb building block specifications becoming @W3C Recommendations:
* 5y Webmention: https://www.w3.org/TR/2017/REC-webmention-20170112/
* 4y WebSub: https://www.w3.org/TR/2018/REC-websub-20180123/
Both specs are peer-to-peer mechanisms, Webmention for a site to notify another of a new or updated link to it, and WebSub for a site to broadcast (or subscribe to) notifications for when that site has published new content.
Bridgy is a good source of metrics for Webmention. The Bridgy stats from last June https://snarfed.org/2021-06-05_bridgy-stats-update-6 show steady growth in both total Webmentions sent and perhaps more importantly, unique domains sending and receiving Webmentions. In addition the number of implementations & support libraries continues to grow, interoperable across multiple languages: https://indieweb.org/Webmention-developer#Implementations
Webmentions still have interesting social and UX challenges. While spam has not (yet) been a major challenge, there is the larger challenge of how to semi-automatically moderate and/or prioritize handling webmentions received from others, especially people you have not met before. The nascent Vouch extension https://indieweb.org/Vouch has been prototyped and implemented on some sites yet needs some work to address the more sublte social challenges. There are challenges with even trusting and displaying the icons of authors who have sent webmentions. Pixelated icons https://indieweb.org/pixelated are one possible approach.
WebSub has shown slower growth. While the number of sites that provide WebSub notifications for new content continues to grow: https://indieweb.org/WebSub#IndieWeb_Examples the number of hubs and hub implementations have been fairly stable for the past year https://indieweb.org/WebSub#Hubs as well as implementations that consume WebSub notifications: https://indieweb.org/WebSub#Consuming_Implementations
The key next step for WebSub is more Reader implementations, e.g. in modern Social Readers https://indieweb.org/social_reader to provide realtime updates immediately when publishing sites post new content. Once there is broader incentive for more sites to provide WebSub notifications, consuming sites such as readers will have more incentive to implement receiving WebSub notifications, reinforcing a positive implementation feedback loop.
With the combination of Social Readers showing new posts in real time via WebSub and personal sites showing new comments & other responses in real time via Webmention, the peer-to-peer web will provide a responsive experience comparable to centralized social media silos.
Want to support Webmention and/or WebSub on your own site?
Drop by the IndieWeb Developer chat and say hi!
https://chat.indieweb.org/dev
-
I, for one, welcome all the independents speaking truth to power, criticizing organizations when they do or encourage harmful actions, especially in a systemic or global scope.
Even better when folks post said critiques to their personal sites. #indieweb
-
Posting notes on your site is the “Hello World” of the independent web.
If you speak to the ideals of the #openWeb #decentralizedWeb #distributedWeb #federatedWeb #indieWeb or even #smallWeb, walk your talk: post your notes somewhere you control. Whether static HTML, server-generated from storage, or a service supporting your domain, choose a method that works sustainably for you, and stick to it.
Questions about options and when or why to choose one or another?
Ask: https://chat.indieweb.org/
Tantek
All stadeus content and data are available under the