#dev 2023-06-10

2023-06-10 UTC
#
vladimyr
[tantek]: Matthew Wise is author of self-hostable blogging platform havenweb - https://github.com/havenweb/haven
#
Loqi
[preview] [havenweb] haven: Self-hostable private blogging
#
vladimyr
They gave lightning talk about it on last year's libreplanet conf http://techrights.org/2022/04/03/matthew-wise-on-haven/
#
vladimyr
Same vid is available from frama peertube instance https://framatube.org/w/3zU6um3C5mj7oXDeumkdz8
#
[tantek]
what is Haven
#
Loqi
It looks like we don't have a page for "Haven" yet. Would you like to create it? (Or just say "Haven is ____", a sentence describing the term)
#
[jacky]
oh I remember haven
#
[jacky]
they were in here once about protected posts
#
vladimyr
In terms of technology here is what they say in their Show HN ann https://news.ycombinator.com/item?id=26013717
#
vladimyr
> There’s nothing new here in terms of technology--server-side rendered web pages using Ruby on Rails, no javascript frameworks, RSS using HTTP basic auth. But also no analytics libraries or ad-tracking. Pages are lightweight and load really fast. I’ve even provided a limited ability to add custom CSS so you can really make your page your own.
#
Loqi
[preview] [mawise] Hey HN, I’m the author, Haven has been my side project for a little while. The core idea is that we should be able to make it easy for anyone to host their own private webpage as an alternative to centralized social media. A lot of the decentraliz...
#
[tantek]
does it have any IndieWeb building blocks support like IndieAuth? if it does we can document it
#
vladimyr
I guess basic auth is protected posts part
#
vladimyr
And as they admit down in the thread support for authenticated rss endpoints across rss readers isn't that great: https://news.ycombinator.com/item?id=26014156
#
Loqi
[preview] [mawise] I embed username and password in the URL; each user gets their own dedicated RSS Url. Support for this among feed readers is admittedly spotty, for example Inoreader requires you to be on a paid plan and Feedly doesn't support it. If there's tracti...
#
vladimyr
I don't see any IndieWeb stuff but I haven't looked into the code yet
#
vladimyr
What I found is this article on Webmentions on their blog https://havenweb.org/2023/04/10/private-comments.html
#
Loqi
[preview] Private Comments, or Why I’m Down On Webmentions
gRegor joined the channel
#
[tantek]
didn't find anything in Haven issues either, except for a postponement of support for TicketAuth: https://github.com/havenweb/haven/issues/29
#
[tantek]
well if someone here starts using Haven on their site (IndieWeb Example), or Haven adds support any IndieWeb building blocks (like any, even microformats), we can create an article for it, until then, not going to worry about it
#
vladimyr
a month ago Jim Nielsen proposed new .well-known URI for personal avatars https://mastodon.social/@jimniels/110333956499414771
#
Loqi
[preview] [Jim Nielsen] Proposal to make a new .well-known URI for personal websites that surfaces your avatar, e.g.https://www.jim-nielsen.com/.well-known/avatar
#
vladimyr
reading through fedi comments I spotted this gem https://fediverse.zachleat.com/@zachleat/110418825853810681
#
Loqi
[preview] [Zach Leatherman] @jimniels relatedly, @eleventy has an indieweb-avatar service that solves some of this with app icons: https://www.11ty.dev/docs/services/indieweb-avatar/
#
[tantek]
Why are people proposing well-known paths for things that already have rel-based discovery that's been widely implemented?
#
vladimyr
dunno but I can think of two reasons: 1) they might not be aware of rel mechanism 2) contrary to rel-s it doesn't require html parsing?
#
vladimyr
I mean yeah, there is HTTP Link header but setting that up is kinda tricky and not always allowed
[aciccarello] joined the channel
#
[aciccarello]
I think one of the comments mentioned an existing well-known based avatar spec
#
[aciccarello]
Clearly not well known enough 😉
#
vladimyr
existing well-known avatar spec, you mean webfinger with profile photo?
#
[aciccarello]
It was probably that one
[marksuth], geoffo and [jeremycherfas] joined the channel
#
c​apjamesg
I have been polishing the IndieWeb Utils docs: https://github.com/capjamesg/indieweb-utils
#
c​apjamesg
Or, rather, the README.
#
Loqi
[preview] [capjamesg] indieweb-utils: Utilities to aid the implementation of various IndieWeb specifications and functionalities. Built with Python.
pharalia, eitilt1, bterry1, ahappydeath and geoffo joined the channel
#
[snarfed]
capjamesg++
#
Loqi
capjamesg has 37 karma in this channel over the last year (105 in all channels)
#
[snarfed]
found a problem with the proposed identity mappings between protocols in https://fed.brid.gy/docs#translate : if you have the same domain as your handle on multiple protocols, which is likely to happen - eg http://snarfed.org is my web site, my Bluesky handle, and my Nostr NIP-05 domain - the current proposal is that they all appear in the fediverse as the same handle, @snarfed.org@fed.brid.gy , with no way to disambiguate that
#
[snarfed]
collision
#
[snarfed]
thoughts?
#
[snarfed]
one obvious solution is to use different bridge domains for each protocol. so for me, my Nostr user would be @snarfed.org@nostr.brid.gy, my Bluesky/ATP would be @snarfed.org@atp.brid.gy, and my web site would be @snarfed.org@web.brid.gy , or something similar
geoffo joined the channel
#
[tantek]
What's the UI problem of having them all show up as the same on fedi?
#
[snarfed]
we can only return one WebFinger response and AS2 actor for @snarfed.org@fed.brid.gy, not three
#
[tantek]
Shouldn't the "one webfinger response" just be your plain domain?
#
[tantek]
All those others are just POSSE copies at best right?
#
[snarfed]
for us, yes, but I'm expanding Bridgy Fed to bridge other protocols, eg AP <=> Bluesky
#
[snarfed]
(happy to discuss this elsewhere if it's not indieweb-relevant enough)