@kev, I read your post about whether blogs need to integrate.

https://kevquirk.com/does-a-blog-need-to-integrate/

I have opinions of my own. The short version is that it's not the blog's job to integrate as long as it provides a #RSS, #Atom, or #JSON feed.

https://matthewgraybosch.org/blog/re-does-blog-need-to-integrate/

#webdev #indieweb #blogging #posse

Have managed to avoid/leave most silos with two exceptions: Letterboxd and RYM. It’s been almost a decade keeping track of movies and I was not thinking of leaving, but the way sparkles handles watches makes the idea very appealing… sparkle it up with the Last.FM API so one can mark Albums as listened and we’ve got the ultimate Micropub client.

Can one of the #indieweb folks please remind me the URL I should send content to in the update services section of #Wordpress?

I know that I should be working on my WP site at the moment... but Gods, some of the stuff I get to read up here... makes my day. I haven't been on #Twitter since this morning, and that was only to reply to somebody decent I know who has no #Fediverse account, and who is now out of state. #indieweb #productivity

A great writeup by @kev on not integrating personal #blogs to services like #ActivityPub or #Indieweb: https://kevquirk.com/does-a-blog-need-to-integrate/

I tend to agree here with my #lazyblorg at least for the moment: https://github.com/novoid/lazyblorg/issues/71

Thanks to @mxbck for the Webring Starter Kit which I forked for my webring! #indieweb

@blaine @ChrisBoese @jeffjarvis @coachtony @mathowie @buster which is why we spend a lot of time at #indieweb documenting these things and distinguishing the kinds of responses, as there are commonalties across systems, not snowflake silos, and if we are to have the ability to choose which it is worth understanding them. https://indieweb.org/responses
The AS2 process shrunk a lot of variety from AS1, and in both cases the taxonomy of existing post and response types was not preserved.

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
#100DaysOfIndieWeb #100Days #IndieWeb
@zeina@mstdn.ca, good questions to ask when considering a “provider” (of any sort).

https://micro.blog/ is a paid service (~$5/mo last I checked), while Tumblr is not.

micro.blog is more like a professional storage service, with a similar relationship and incentives, rather than a neighborhood garage which depends more on the whims and available time & interest of the admin.

I personally agree with “spinning up your own CMS” for a variety of semi-obvious reasons, however, that requires a web development skillset (and perhaps time & patience) that few have or have cultivated. Hence a turn-key for-pay service (with tons of export options at sign-up time) may help many more to join and interact peer-to-peer with other #IndieWeb sites.
https://craveytrain.com/, thanks for the kind words! Big believer in walking the talk, and the persuasive power of live examples.

That’s a fine 2023 commitment! If you’d like, drop by https://chat.indieweb.org/dev/ and feel free to share your thoughts-in-progress on how to own and publish your content (on your own domain).
https://jwz.org, thanks for the RT/boost. Am curious how you happened upon the POSSE tweet copy presumably first, rather than the original  https://tantek.com/2023/001/t1/own-your-notes which should be natively visible on the “fediverse” (like this reply), perhaps by copy/pasting that URL into a Mastodon search box.

Hoping to find ways to improve original post discovery, so tools can (semi-)automatically convert such POSSE links to original post permalinks when sharing/replying/reposting etc.

My final project of 2022 was to set up my own personal space on the #IndieWeb and I'm still not quite done getting things in order. Current thing that has me a bit stumped is how to handle #comments on https://gregsplace.net I'd much prefer to turn off the native #Wordpress commenting system and stick to #Webmentions but I'm not 100% certain how to go about that... Of course, since I'm learning as I go along, more & more little things like this get added to my to-do list.

Lots of conversation recently about integrating #blogs with services like #ActivityPub and #IndieWeb.

Here's some of my thoughts on those integrations:

https://kevquirk.com/does-a-blog-need-to-integrate/

I'm seeing this sentiment emerge more and more lately.

I like it.

https://www.theverge.com/23513418/bring-back-personal-blogging

#indieweb

Plenty of work still to do (especially on the home page), but my site redesign was already looking better than what was public, so I’ve merged my branch. https://kevinyank.com/ is now showing my work-in-progress redesign. #indieweb https://kevinyank.com/

Farewell, Fail Whale

I find the arguments against officially supported Fediverse search pretty tedious, as you have…

I looked everywhere to store files in a web app (for Noodle):
- Dropbox & GDrive JS libraries
- LocalStorage (erf)
- IndexDB
- Decentralized storage pods like Solid, RemoteStorage etc.
- showDirectoryPicker() (awesome but Chrome only)
- blockchain-based storage like IPFS

What am I missing #indieWeb?

It's mind blowing how hard it is, in 2023, to build a web app that read and write user files privately. It would be SO easy to just ask users to create an account and store everything in a DB. Why?