tantek.com

t

  1. using BBEdit

    Day 1 of #IndieWebCamp #Berlin 2024^1 was very well attended! * 20 participants, more than 3x the previous one in 2022, and second highest (2019 had 22). * 18 introduced themselves^2 and their personal sites or aspirations for one Collectively we proposed and facilitated 11 breakout sessions^3 on many timely #indieweb 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 ^1 https://indieweb.org/2024 ^2 https://indieweb.org/2024/Berlin/Intros ^3 https://indieweb.org/2024/Berlin/Schedule#Saturday This is post 28 of #100PostsOfIndieWeb. #100Posts ← https://tantek.com/2024/306/t1/simple-embeds → 🔮

  2. using BBEdit

    Still reflecting and listening to how different folks are reacting after the US #election results. A few immediate thoughts: * take care of yourselves, physically, emotionally, etc. * lean into mutual care, check on those close to you * (re)connect with community and especially those that reach out to you * (re)consider privacy implications of your actions, IRL & online, spending habits Here in #SanFrancisco and #California we are seeing mostly positive local results^1 including a new mayor (who I happened to rank first for many reasons). Lots to think about and do in the next couple of months. ^1 https://sfstandard.com/2024/11/05/san-francisco-election-results-november-2024/

  3. using BBEdit in reply to: @pointlessone@status.pointless.one

    @pointlessone@status.pointless.one short answer: oEmbed requires JS for publishers and consumers. Longer: For me, "simple" means a little HTML is all you need. I was inspired to come up with something that anyone could create with (existing) HTML text files. Zero imperative code. Simple HTML also means easier / better support for static file hosting solutions. E.g. if your website is on GitHub Pages or other static site hosting, you can’t implement an oEmbed endpoint (certainly not without an external service, which has other problems). Whereas plain old semantic HTML (POSH^1) works great on GitHub Pages or other static site hosting. Would be interesting to see if someone can build an oEmbed "shim" service that did discovery on rel=embed and then translated h-entry into oEmbed’s specific JSON vocabulary. That way publishers would have less work to do (with plain HTML) and existing oEmbed consumers would support embedding more publishers. ^1 https://microformats.org/wiki/posh

  4. using BBEdit also on: IndieNews

    Last week at a #HomebrewWebsiteClub session^1 I pointed out that I was working on implementing a “simple” way to support embeds of my notes, that is, make my short notes embeddable, like how people embed tweets or toots. I noted that to keep it as simple as possible while being flexible to implementation changes, I planned to implement three things: 1. A separate “embed” version of my post permalinks, with just the entry information (no header, nav, search, sidebar, footer etc.), embeddable via copy/paste or an iframe. 2. A way to “Follow Your Nose” discover that separate embed version 3. A way to discover the original post from the embedded version For (1) a minimal h-entry, with perhaps a little bit of inline CSS would suffice. For (2) I proposed using “rel=embed” which I’ve subsequently written up briefly^2. For (3) The obvious existing answer is rel=canonical link from the embed version to the canonical post permalink. Soon thereafter, several folks in the #IndieWeb community went ahead and implemented such embeds for their own sites, and even the https://libre.fm/ open scrobbling service! https://indieweb.org/embed#IndieWeb_Examples I have yet to implement it myself, and that’s fine. This is one of the things I appreciate about the community, we can share our plans and ideas for improving things on our own sites, and if someone else does it first, that's great! We celebrate it and explore the solution space together. Got other ideas for simple embeds? Want to implement them on your own site? Join us in the #indiewebdev chat: https://chat.indieweb.org/dev UPDATE: What about oEmbed? tl;dr: oEmbed requires JS and backend code, more work and unsuitable for embeds from static site hosting (like GitHub pages). A simple HTML method is accessible to many more independent publishers and easier to implement. More: https://tantek.com/2024/306/t2 Glossary embed https://indieweb.org/embed Follow Your Nose https://indieweb.org/follow_your_nose h-entry https://microformats.org/wiki/h-entry oEmbed https://indieweb.org/oEmbed rel-canonical https://indieweb.org/rel-canonical static site hosting https://indieweb.org/static_web_hosting References ^1 https://indieweb.org/events/2024-10-23-hwc-europe#embedding ^2 https://indieweb.org/rel-embed This is post 27 of #100PostsOfIndieWeb. #100Posts ← https://tantek.com/2024/287/t1/fediverse-unfollow-bridgyfed-bug → https://tantek.com/2024/314/t1/indiewebcamp-berlin-2024-day-1