#dev 2023-04-12
2023-04-12 UTC
geoffo and sebbu joined the channel
# 
aaronpk so what's the state of this iOS app? https://indieweb.org/Indigenous_for_iOS
# aaronpk the repo the page links to as the current version is marked as archived https://github.com/IndiePass/indigenous-ios/issues
# aaronpk there's also this stub of a repo that says it's in progress but hasn't been touched in over a year? https://github.com/IndiePass/indiepass
bterry and geoffo joined the channel
# 
[marksuth] Indigenous for iOS got pulled from the App Store by Apple during their cull of un-updated apps. Getting the existing iOS app up to their current standards was taking considerable effort to unpick and bring up to current App Store requirements, hence the restart of building it in flutter.
# [marksuth] The current GitHub repo has been quiet for a while as I’ve been tied up elsewhere for the most part, however I am now actively working on getting it completed,for the most part making use of the underlying code from the android version.
# [marksuth] In addition, I’m currently finishing an update to the current Indigenous for Android app to bring it up to SDK version 33 to prevent it being pulled from the play store as it is currently built against SDK version 29 which is below their upcoming minimum requirements
# [marksuth] Yes of course!
# 
prologic What's Insincenous ?
# 
GWG [snarfed]: Re https://github.com/marksuth/indigenous-android/issues/431, makes me think of a Micropub proposal to offer different syndication targets based on post type
sebbu, IWSlackGateway, Kaja, [pfefferle], saptaks, oxtyped and jonnybarnes joined the channel
# 
@JesperBylund ↩️ I think it was a partly good solution. I'd like to try something similar to the original organic retweets. Using webmentions to host everyones responses publicly (but maybe pseudonymously) (twitter.com/_/status/1646124603947769858)
[capjamesg], [KevinMarks], [pfefferle], geoffo, [tantek], [dave], [manton], gxt__, gRegor and angelo joined the channel
[marksuth] joined the channel
# [marksuth] on a completely unrelated note, anyone got any ideas of what I can do with indiesnail.rocks?
[schmarty] joined the channel
# 
[schmarty] 😂
# [schmarty] build a terrarium
# 
Loqi It looks like we don't have a page for "days since last domain purchase" yet. Would you like to create it? (Or just say "days since last domain purchase is ____", a sentence describing the term)
geoffo joined the channel
# Loqi It looks like we don't have a page for "CGI" yet. Would you like to create it? (Or just say "CGI is ____", a sentence describing the term)
# [schmarty] hmm. thinking on some improvements to my own social reader setup (microsub powered by aperture) and i feel like the /Microsub-spec is missing a way to update entries.
# [schmarty] the problem is i have feeds from youtube which are Atom feeds using xmlns:media to describe the actual content of each entry in a media:group. the title and author info are also there in regular Atom ways, so i get a bunch of entries that are just titles and the channel name.
# [schmarty] i'd actually like to do two different things with these. one is to extract the media:thumbnail and media:description so i can see a few more details. the other is to actually fetch a little more info about the videos to filter out "shorts" because i don't wanna see those.
# [schmarty] yeah pretty much. i want to "improve" these entries. i initially started thinking of this from the perspective of a microsub client that watches for new posts in a channel. it can process them however and, ideally, do something like a PUT to fix up a given entry.
[snarfed] joined the channel
# [schmarty] i'm probably going to proxy the feeds instead, but it still feels like this is something missing from microsub.
# [schmarty] i guess my thinking is that i could run a microsub client wherever i want, but a feed proxy requires exposing and securing and maintaining an HTTP endpoint somewhere for aperture to fetch from.
# [schmarty] i guess this feels like a temptation specifically for aperture because it supports Micropub directly into channels.
# [schmarty] and if it's good enough for posting then why not editing?
# [schmarty] but i also see that this could be a trap!!
# [schmarty] this is more just me sharing a curiosity that popped up unexpectedly in how i use these tools.
# [schmarty] for now i am pretty sure i can set up a proxy and munge the feeds.
# bkil `<iframe>`
[tw2113_Slack_] joined the channel
# [tw2113_Slack_] not sure there is one for that
# [tw2113_Slack_] nothing i can think of at least, i could be wrong
# bkil If you are linking from HTTP/HTML documents, why not also always link to HTTP/HTML documents? The target proxy of the link itself may contain the original proxied gemini/gopher link as an alternate in the `<head>` or in a HTTP header. https://developer.mozilla.org/en-US/docs/Web/HTML/Attributes/rel#alternate https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Link
# bkil I would probably place the different protocol variants of the same link listed in parenthesis either linked to gopher/gemini or perhaps by opting for an icon to depict each and then leave it to the visitor to choose. In case of video, audio and picture, in practice, the determining factor I think is usually whether the platform supports the given codec or not. I haven't seen a user browser setting for preferring codecs (or bitrates) for such elements yet.
# bkil At the same time, such a setting is commonly implemented by WebRTC (JavaScript)-based web apps on that level of the stack.
# Loqi It looks like we don't have a page for "purl" yet. Would you like to create it? (Or just say "purl is ____", a sentence describing the term)
# bkil I'm also considering to implement something like PURR, not sure about this specific project. But it's logical conclusion from TiddlyWiki and Feather https://feather.wiki/ https://tiddlyhost.com/
[chrisbergr] joined the channel
# bkil A question about this: https://indieweb.org/search#searchability_-_level_1#:~:text=post%20content%20in%20HTML Does anybody know what recent artisan search engines (or older ones) that can't run JavaScript are indexing precisely? I recall reading about Google desperately indexing mostly anything within your source code when it was still working statically decades ago (i.e., embedded JSON, data attributes, strings in JavaScript, etc). What are artisan ones doing
# bkil at present?
# bkil I know the safe answer is to "just display everything to the user", but this is a question relating to innovation, not to the status quo.