mastodon.xyz is one of the many independent Mastodon servers you can use to participate in the fediverse.
A Mastodon instance, open to everyone, but mainly English and French speaking.

Administered by:

Server stats:

844
active users

#indiewebcamp

0 posts0 participants0 posts today

New blog post: “Updated Scroll Markers in the Table of Contents”

blog.kizu.dev/toc-scroll-marke

I’ve spent most of the day inside the delayed and cancelled trains (thanks, Deutsche Bahn). I did not have an opportunity to come up with a good post for today, but both yesterday (and a bit today) I hacked on my blog, as a part of the #IndieWebCamp.

I did the thing I wanted to do during this weekend: update my blog’s Table of Contents to be similar to what I have on my main site.

Day 1 of #IndieWebCamp #Berlin 2024¹ was very well attended!
* 20 participants, more than 3x the previous one in 2022, and second highest (2019 had 22).
* 18 introduced themselves² and their personal sites or aspirations for one

Collectively we proposed and facilitated 11 breakout sessions³ on many timely topics covering #syndication, #inclusion, #longevity, #federation / #fediverse, how to best use #Mastodon with your personal site, #privacy and #security concerns of being online, #writing, how can we design better user interfaces for text authoring, and personalized reading #algorithms for staying connected with friends.

Session titles (and hashtags)
* How to #POSSE
* How to make the web queerer / stranger. #queer
* Online presence after our #death
* Threat modeling #threatmodeling
* Non-technical collaboration on the internet. #collab
* Locations and #places check-in
* Writing with images. #imagewriting
* Text authoring UX. #textUX
* #SSR, organizing CSS/JS
* Website design without being a designer. #designfordummies
* Timeline algorithms. #timelines

Etherpad notes from sessions have been archived to the wiki, with session recordings to follow!

Day 2 also had 20 in-person participants, the highest IndieWebCamp Berlin day 2 attendance ever! Most everyone from day 1 came back to hack, and three new people showed up. We also had several remote participants.


References
 
¹ https://indieweb.org/2024
² https://indieweb.org/2024/Berlin/Intros
³ https://indieweb.org/2024/Berlin/Schedule#Saturday


This is post 28 of #100PostsOfIndieWeb. #100Posts

https://tantek.com/2024/306/t1/simple-embeds
🔮

Mastodon hosted on indieweb.social Indieweb.Social INDIEWEB.SOCIAL is an instance focused on the evolution of #Openweb, #Indieweb, #Fediverse, #Mastodon, #Humanetech and #Calm technologies.

European friends!

🗓 I am going to Beyond Tellerand (@btconf@mastodon.social) Berlin next week 7-8 November and you should too!

BTconf is the best independent web design, development, and inspiration conference in Europe.

Everything from the speakers to the talks to the side events are a labor of love by @MarcThiele.com (@marcthiele@mastodon.social) and his crew, and it shows in the #btconf community he has gathered over the years.

If you’re in #Berlin, or can hop on a train and join us, you should.

🎟 Grab a ticket: https://btco.nf/t

And while you’re there, consider joining us at #IndieWebCamp Berlin right afterwards on 9-10 November (complimentary camp tickets at the same link), for #barcamp style discussions sessions and an #indieweb Create Day, writing, styling, designing, coding, hacking on our personal sites for a better web for ourselves and everyone else.

Mastodonbeyond tellerrand (@btconf@mastodon.social)1.27K Posts, 56 Following, 900 Followers · beyond tellerrand is the affordable single-track event where creativity and technology meet. Taking place in Düsseldorf and Berlin next with 500+ attendees each in a renowned, familiar and friendly atmosphere.

✏️ I want the Read Write Suggest-Edit Accept-Edit Update Web. The consumer Infinite Scroll Web leaves us feeling empty. Too few of us participate in the Read Write Web, whether with personal sites or Wikipedia. A week ago when we wrapped up #IndieWebCamp Portland and I was reading Kevin Marks (@kevinmarks) live-tooting of the demos^1, I noticed a few errors, typos or miscaptures, and pointed them out in-person. Kevin was able to quickly edit his toots and update them for anyone reading, thanks to #Mastodon’s post editing feature and its support of #ActivityPub Updates. But this shouldn’t require being in the same room, whether IRL or chat. We should be able to suggest edits to each other’s posts, as easily as we can reply and add a comment. 13 years ago I wrote^2: “The Read Write Web is no longer sufficient. I want the Read Fork Write Merge Web.” Now I want the Read Write Suggest-Edit Accept-Edit Update Web. The ↪ Reply button is fairly ubiquitous in modern post user in tantek.com/2024/245/t1/read-wr

tantek.com✏️ I want the Read Write Suggest-Edit Accept-Edit Update Web. The consumer Infinite Scroll Web leaves us feeling empty. Too few of us participate in the Read Write Web, whether with personal sites or Wikipedia. A week ago when we wrapped up #IndieWebCamp Portland and I was reading Kevin Marks (@kevinmarks@indieweb.social) live-tooting of the demos^1, I noticed a few errors, typos or miscaptures, and pointed them out in-person. Kevin was able to quickly edit his toots and update them for anyone reading, thanks to #Mastodon’s post editing feature and its support of #ActivityPub Updates. But this shouldn’t require being in the same room, whether IRL or chat. We should be able to suggest edits to each other’s posts, as easily as we can reply and add a comment. 13 years ago I wrote^2: “The Read Write Web is no longer sufficient. I want the Read Fork Write Merge Web.” Now I want the Read Write Suggest-Edit Accept-Edit Update Web. The ↪ Reply button is fairly ubiquitous in modern post user interfaces (UIs). Why not also a ✏️ Suggest Edit button, to craft a fix for a typo, grammar, or other minor error, and send the author for their review, and acceptance or rejection? Perhaps viewable only by the suggester and the author, to avoid "performative" suggested edits. If the author’s posts provide revision histories, when a suggested edit is accepted, a post’s history could show the contributor of the edit. Instead of asking Kevin in-person, what if I could have posted special "Suggested Edit" responses in reply to his toots, for which he would receive special notifications, and could choose to one-click accept and update (or further edit) his toots? To enable such UIs and interactions across servers and implementations, we may need a new type of response^3, perhaps with a special property (or more) to convey the edits being suggested. There is documentation of this and similar use-cases, prior art / UIs, as well as some brainstorming on the #IndieWeb wiki: * https://indieweb.org/edit Our interaction after IndieWebCamp has inspired me to take another look at how can we design and prototype solutions to this problem. For now, if you host your blog and posts as static files on GitHub (or equivalent), you could add a button like this to your posts alongside Like, Reply, Repost buttons: ✏️ Suggest Edit and link it to an edit URL for the static file for the post. I don’t use GitHub static files myself for posts, but here’s an example of such an edit link for one of my projects: https://tantek.com/github/cassis/edit/main/README.md This will start the process of creating a “pull request”, GitHub’s jargon^4 for a “suggested edit”. After completing GitHub’s ceremony of entering multiple text fields (summary & description), and multiple clicks to create said “pull request”, it’ll be sent to the author to review. Presuming the author likes the suggested edit, they can perform the other half of GitHub’s jargon-filled ceremonies to “Merge” or “Squash & Merge”, “Delete fork”, etc. to accept the edit. It’s an awkward interaction^5, however useful for at least prototyping a ✏️ Suggest Edit button on sites that store their posts as files in GitHub. Certainly worthy of experimenting with and gathering experience to design and build even better interactions. We can start with the shortest path to getting something working, then learn, iterate, improve, repeat. #readWriteWeb #editableWeb #suggestEdit #acceptEdit References: ^1 https://indieweb.social/@kevinmarks/113025295600067213 ^2 https://tantek.com/2011/174/t1/read-fork-write-merge-web-osb11 ^3 https://indieweb.org/responses ^4 The phrase “pull request” was derived from the git command: “git request-pull” according to https://www.reddit.com/r/git/comments/nvahcp/comment/h12hzj7/ ^5 “edits” in GitHub require taking far more steps, and navigating far more jargon, then say, Wikipedia pages, which come down to “Edit” and “Save”. We should aspire to Wikipedia’s simplicity, not GitHub’s ceremonies. This is post 20 of #100PostsOfIndieWeb. #100Posts ← https://tantek.com/2024/242/t1/indiewebcamp-portland → https://tantek.com/2024/246/t1/adventures-indieweb-activitypub-bridgy-fed - Tantek

This week seemed to have been the week where the northern lights weren’t all that northern anymore. There were about a million photos of them – and I managed to sleep through the whole spectacle. Well done, Dominik.

Meanwhile it has been one of those short weeks with a public holiday on a Thursday which I spend watching my cousin kick a ball around, followed by cake at a birthday garden party. Good times.

Afterwards it was time to head north to Düsseldorf for the double-whammy of the IndieWebCamp and the beyond Tellerrand convention.
The IWC was good fun, it sure was interesting to meet a whole bunch of people who I’ve only met online up until that point and talk about personal websites. Quite quaint in a way, but it is nice to hang out with people with similar interests.
And of course it was great to have dinner with Ben, Martin and Teymur afterwards. Lovely weekend, indeed.

Meanwhile on the internet and related to the topic of websites: The Revenge of the Homepage – someone at the New Yorker realized that there’s more to the internet than just Social Networks.

Oh deere: (sorry) The solar storms that gave us (well, not me, see above) northern lights also managed to disable farming equipment: Solar Storms are disrupting farmer GPS systems during critical planting time. Apparently tractors are so high-tech now that they can’t work without very precise GPS. Who knew?

Meanwhile this speaks to me: I want it all but, it is impossible – filtering and prioritizing people, knowledge, creation, consumption and off-time is really hard with all the limited time we have. So I’m even more flattered that you decided to spend some time and attention around here. Thank you very much!

And with that I’m done for the week – the sun is rising over Düsseldorf and I’m ready to go to beyond Tellerrand.

Some people were confused by the fact that I used the same picture for my Mastodon account (@dominik@nona.social) and the ActivityPub representation of this blog (@dominik@lostfocus.de) so for quite a while I had the inclination to change the avatar here to this very artistic image:

The IndieWebCamp hack day create day was a good occasion to do just that. I didn’t want to change the image for all calls to the get_avatar function, so that’s what I came up with after Matthias told me about the Activitypub\is_activitypub_request function:

if ( function_exists( 'Activitypub\is_activitypub_request' ) ) {    add_filter( 'pre_get_avatar_data', static function ( $args, $id_or_email ) {        if ( $id_or_email !== 1 || ! \Activitypub\is_activitypub_request() ) {            return $args;        }        $args['url'] = plugin_dir_url( __FILE__ ) . 'blog-squared.jpg';        return $args;    }, 10, 2 );}

Now let me be the first to say this: this is very hacky and the values for the user id and the image url are hard coded. But it works for me and if you need it, you’re probably able to find a way to adjust the values to your use case.