#dev 2022-07-21
2022-07-21 UTC
# [tantek] blockchain << Criticism: YAGNI even for SSI: 2022-07-08 [https://weh.wtf/ssi.html SSI-on-Blockchain is Objectively a Bad Thing]
# Loqi ok, I added "Criticism: YAGNI even for SSI: 2022-07-08 [https://weh.wtf/ssi.html SSI-on-Blockchain is Objectively a Bad Thing]" to the "See Also" section of /blockchain https://indieweb.org/wiki/index.php?diff=82322&oldid=82228
# superkuh Server side includes on blockchain?
jacky and strugee joined the channel
# [KevinMarks] Overloaded TLA, its Site of Scientific Interest (a kind of nature reserve) too
jacky joined the channel
# vikanezrimaya Good morning IndieWeb! Media endpoint question. When you upload, say, an image to your media endpoint, capable of transcoding images to webp (lossless webp specifically), do you expect the media endpoint to also retain the original upload or only save the converted file?
# vikanezrimaya I'm wondering if I should even retain original image files when transcoding. They'll be essentially wasting space if left unused.
geoffo, gerben and petermolnar joined the channel
gRegorLove_ joined the channel
# vikanezrimaya sknebel: I am a big fan of big images. My screenshots are PNGs of several megabytes, and JPEGs from my phone's camera have ludicrous resolution that is extremely slow to transfer over the internet (believe me, I tried)
# vikanezrimaya webp is my only salvation, as it seems to be more efficient than both of these formats
petermolnar, geoffo, gxt, mro_, superkuh and tetov-irc joined the channel
# vikanezrimaya I just had a small epiphany about IndieAuth. 1) client_id is always fetched to check redirect_uri; 2) identity provider is allowed to reject any scopes it doesn't like whenever it wants to; 3) IndieAuth allows one to define custom scopes. Ergo, I could make a restricted scope only available to certain clients
# vikanezrimaya Nobody else will be able to get that scope except a certain client - because if they spoof client_id, they won't pass redirect_uri check. And if they ask for it otherwise, the server's not gonna grant it.
mro joined the channel
# vikanezrimaya I'm sure this knowledge could be useful to me somehow.
jacky joined the channel
# callym[m] I'm working on a git-based wiki using indieauth to login - I'm currently storing a map of `email => url` for each user, as git stores the email for each commit, and then the url can be used to fetch the h-card data, but I'm not sure if this is the best/right approach? should I be storing the profile returned from the auth directly, or should I instead be storing a token and asking the endpoint for the profile when I need it?
# callym[m] also am I right in saying that gitea doesn't support indieauth?
superkuh joined the channel
# vikanezrimaya callym[m]: if you are using IndieAuth solely as an identity provider and not to interact with your user's website, you can forgo requesting a token (though you are free to get one if you want profile updates to be picked up more often than your average user reauthenticates - assuming the newest version of IndieAuth, sending a token scoped to "profile" to the userinfo endpoint will get you a fresh version of the profile). Using email=
# vikanezrimaya GitHub, for example, looks users up by emails verified in their profile. It can be very fun to upload repositories with spoofed commit author information, because git itself doesn't check it, and GitHub believes commit attribution from Git.
# Loqi Gitea is a site, service, and open source project for code repositories (using git) and issue tracking https://indieweb.org/Gitea
# vikanezrimaya I've never done it, but I've seen others do.
# vikanezrimaya The Go repository is one of the funniest examples of fake commits - you'll have to scroll to the beginning of its history to see the Easter egg.
geoffo, mro, AramZS and jacky joined the channel
# callym[m] I think the being able to commit with any email is fine - the software is in charge of making commits with the email address of the user - if someone else pushes directly to the backing repository with random emails then that's fine I guess
# callym[m] great - just wanted to make sure I wasn't taking the "easy but wrong" way of getting the user data 😄
mro joined the channel
# callym[m] ah there was an issue on the gitea github but it's been closed
jacky, alex11 and geoffo joined the channel
# [aciccarello] jacky, I haven't implemented channels but I'm also interested in how to approach this. I'm thinking about having separate channels for posts (blogs, notes, photos) and activity (bookmarks, replies). But I've wondered about cross-over content. Like if I want to highlight a reply or bookmark, how would I mark that to appear in the main channel.
# jacky https://github.com/indieweb/micropub-extensions/issues/40 (for more context about the concept of channels)
angelo, gxt and jacky joined the channel
jacky joined the channel
jacky and gxt joined the channel
# xyzzydev[m] this is something I have never worked on - video hosting and live streaming and from my understanding they are very costly from a hosting perspective. while I am aware of webtorrents that can alleviate some hosting bandwidth, what are the bandwidth metrics and things to keep in mind while of hosting some 100 personal videos from a self-hosting standpoint ? lets say 1 video has lots of traffic, how do you plan for it ?
# xyzzydev[m] one advantage of central systems like youtube is that it can probably save costs to host so many videos at a time i.e each individual user to self-host could probably cost a whole lot more than individuals sharing a single platform like youtube
# xyzzydev[m] s/of//
jacky joined the channel
# xyzzydev[m] i feel like videos are like the achilles heel of indieweb. once you start thinking of self-hosting videos, it seems like you need a 20$ vps to host even some basic videos
jacky, tetov-irc and gxt joined the channel
# [KevinMarks] If you are happy making your videos creative commons, Internet Archive will host them for you
jacky, gRegor and gxt joined the channel