This Week in the IndieWeb Audio Edition • August 12th - 18th, 2023

#podcast #IndieWeb #this-week-indieweb-podcast

@forteller I also had problems with Mastodon sign-up, possibly due to my #SpamGourmet email address or my 72 character, high entropy password. Either way my mastodon.technology account never worked.

See: https://indieweb.social/@mcrocker/109332738993329060

I've been happy with #indieWeb social, https://indieweb.social , since I moved there, but I used a #DDG email, https://duckduckgo.com/email, and a (high entropy) password Mastodon can handle, for my account login.

Cc: @tchambers

#Tweet RT @soulcruzer: it's things like this that explain why you should have your own blog, run from your own domain, and syndicate it out to social media sites instead of using them natively. #indieweb

Twitter Deletes All User Photos And Links From 2… https://twitter.com/mndell/status/1693153510227919252

it's things like this that explain why you should have your own blog, run from your own domain, and syndicate it out to social media sites instead of using them natively. #indieweb

Twitter Deletes All User Photos And Links From 2011-2014 https://www.forbes.com/sites/mattnovak/2023/08/19/twitter-deletes-all-user-photos-and-links-from-2011-2014/

Starting off @retrostrange Movie Night early with some Vincent Price infomercial magic https://live.retrostrange.com #IndieWeb #Streaming #Retro

I started what I hope will be a series of posts describing my experiences taking over maintenance and development of a custom Learning Management System (LMS). Hopefully by making it public and attracting a couple followers, I will be more likely to actually make it a series and not just another one-off attempt at "I'm really going to start blogging this time"

https://www.hazyblue.me/2023/maintaining-and-updating-a-custom-learning-management-system-introduction

#indieweb #lms #php #webdevelopment #highered

I have spent the past couple of weeks fixated on implementing #Webmentions on this website, and I have finally deployed the feature! (I think)

https://orangegnome.com/posts/2482/webmentions-maybe

#Django #Indieweb

My Taylor Swift eras

Glass questions at 2 years

Updated my personal #portfolio with a new contact session and a few more sprinkles of the #IndieWeb: added h-card information, more rel="me" links and added my site to a web ring! 🥰

Go have a look: https://kovah.de/

If you could pick the brains of the smartest people in the web industry on the topic of building and maintaining your own personal website and publishing your work online – what would you ask them?

#personalsites #websites #IndieWeb Repost=😻

@losmyke I use @rizzi‘s Reeder — it’s excellent! I wish it supported #IndieWeb’s microsub tho!

On this week's Press This podcast, I asked @david how the #IndieWeb, #Fediverse, and #WordPress can help keep the web weird and free. I enjoyed this conversation and I hope y'all do to.

You can find "Press This WordPress Community Podcast" on your favorite podcasting app. Mine is @overcastfm https://overcast.fm/+2e5-UjRSE

Having spent a fair amount of time developing for all of them, my experience has been that most proprietary social network (“silo”) APIs are on the easy/low effort end of the spectrum, followed closely by the Bluesky API, webmention + microformats2, and Nostr, then a big jump up to ActivityPub at above average, then AT Protocol at the high end.

They all differ in many important ways beyond development effort, of course. Personally, I’m most excited about webmention + mf2, ATProto, and then ActivityPub, for all the obvious reasons. Still though.

(If not for all the NIPs, Nostr would be the easiest of all. Developing for Nostr is pretty simple, but the NIPs are so loose and terse and spread out that ramping up on them and grokking how they all fit together can feel chaotic, at least at first.)

I previously wrote about why you should start a #blog (https://shellsharks.com/you-should-blog). That piece is filled with solid reasons I still stand by today. But since that time, I've come to understand a more meaningful reason to have a website and as part of that site, some form of syndicated content (i.e. a blog). For most, "identity" on the web is tied to one, or fractured across a few, social media platform(s). Recent history has revealed the pitfalls of this approach. Enshittification, terrible management, or even platform collapse can result in catastrophic loss of your connections, communities, business income and more. So many refuse to leave Twitter (er... "X") because they're too invested, to leave would be to sacrifice one or more of these things. Why do we continue to feed these platforms that always fail, that always betray us, that violate our privacy, that never represent who we truly are? Having a website, a place that is yours, that you can design to your specification, share anything you want, how you want and make easily available to all is such an obvious solution and it really isn't that much harder than creating a (pick your social media platform of choice) account. There are a TON of services these days that make it dead simple to get up and running with a customizable site and start publishing. The beauty of this (blogging), is that you can syndicate however you'd like from there. So go ahead, share on Mastodon, or Threads, or wherever, but remember to link back to the true canonical representation on your site.

#indieweb #blogging

https://shellsharks.com/notes/2023/08/16/your-website-your-identity

RIP, looks like my #HomeServer is down for the day. Luckily my blog can still be found on #IPFS.

#IndieWeb
https://dweb.link/ipns/vzqk50.com

I'm a bit overwhelmed. There's nextcloudpi. Using that now. It's usually for singe-purpose machines, but they have a container as well. But I read it's being deprecated? Then there's Nextcloud AIO? For Enterprise?
What's the easiest way to go about that?
#nextcloud #docker #raspberrypi #indieweb

@hmans Could be that they are lazy fetching it or something

I was quite amazed to see issues like this be totally left to the implementers of #ActivityPub

Especially as #PubSubHubbub / #WebSub which #OStatus and other predecessors use (and the #IndieWeb still use) was specifically designed to avoid thundering herd problems that arise from a lot of subscribers all eagerly fetching content at once upon receiving a ping about new content