#dev 2022-10-24
2022-10-24 UTC
tbbrown, [benatwork], jacky and gxt joined the channel
#
GWG https://ma.tt/2022/10/open-source-podcasting-client/ - Wonder if there is a way to now get my data in/out of their sync system?
#
[schmarty] ah thanks for the reminder GWG. i am curious to play with this!
#
[schmarty] scrobbling support via micropub would be fun
tbbrown, [benatwork], dodo1 and [aciccarello] joined the channel
#
slyduda[m] snarfed: got it, i was overthinking what needed to be done on my end and realized that this was a two step pr. thanks for the guidance and sorry for the back and forth
mro, nertzy and [aciccarello] joined the channel
#
Saphire ...how much can I trust indieauth clients to honor the profile info from the server and ignore the inital "me"/profile url?
#
Saphire Wait
#
Saphire Is IndieAuth PKCE S256 incompatible with OAuth
#
Saphire Wait nvm
#
Saphire Oh nvm yeah, I see, derp
jacky, geoffo, mro, gRegorLove_, [tantek] and omz13 joined the channel
#
[schmarty] can you clarify what you mean by "local"? like some list of venues on a page on your site? or in your micropub endpoint available with a `?q=...` query?
#
[schmarty] also what are the purposes for the "local" venues? does a venue have a page on your site that acts as a nexus listing checkin posts at that venue (or other posts that mention the venue in some way)?
#
[schmarty] my gut answer based on my assumptions about your question is that you'd want to make a "local" venue any time you make a post that involves that venue in some way.
#
[schmarty] ah, yeah, i've been thinking about this for a checkin client as well. i think the best option will be... context dependent. 😄
#
[schmarty] like if there's only a handful (1-3?) of already-known venues nearby, it seems fine to load in "remote" results right below that, so long as they are on the screen.
mro joined the channel
#
[schmarty] but another approach is thresholding - if you fetch both already-known and "remote" venues, sorting them by whatever is closest will probably always make sense, as long as location accuracy and density are good.
jacky joined the channel
mro joined the channel
Pyroxtheythem[m], jacky, KatherineMoss[m], slyduda[m], AramZ-S[m], kandr3s[m], h4kor[m], lqdev[m], jordemort, [Murray] and [jgarber] joined the channel
#
[jgarber] > Safari 16.1 adds support for Scroll to Text Fragment, making it possible to include a text directive for finding a text fragment as part of a URL. When a user navigates to a URL that includes such a directive, the browser scrolls the text fragment into view and marks it with a persistent highlight.
#
[KevinMarks] Try it with highlightpoetry.com
#
Saphire FINALLY
#
[tantek] IMO Fragmentions with a polyfill on your own site is a better way to go, better /URL_design
#
Saphire takes it down for now until it's wrapped in docker and stuff
#
superkuh Anything that requires JS execution should be avoided.
#
superkuh I really, really hate sites that implement anchors via javascript.
#
Saphire ...mmh?
#
superkuh Just use anchors.
#
Saphire Ah
#
superkuh I'm pro-browser based implementation here.
jacky and tbbrown joined the channel
#
[KevinMarks] These are anchors that you don't pre provide though
#
@SaphireLattice IndieAuth implemented, IndieWeb Wiki login successful!
Woo
Now to wrap that in docker, whack out a frontend, actual login page, etc
...feeling like being lazy and slapping an SPA in there >_>
I mean, it's not like I'll share that instance with many people :P (twitter.com/_/status/1584624652298878980)
#
Saphire coughs
jacky joined the channel
#
gRegor Huh, didn't realize that was getting more adoption outside Chrome. https://wicg.github.io/scroll-to-text-fragment/
#
gRegor Bummer (but not surprising) they declined on supporting fragmention fallback. Due to SPAs I guess? https://github.com/WICG/scroll-to-text-fragment/issues/5
[jeremycherfas] joined the channel
#
[tantek] !tell KarthikPrabhu looks like your https://kartikprabhu.com/ redirection broke again — should we repair all your links on the wiki to require the "www." in front?
chenghiz_, walkah, oodani, t0nic and oxtyped joined the channel
#
Loqi It looks like we don't have a page for "photo archiving" yet. Would you like to create it? (Or just say "photo archiving is ____", a sentence describing the term)
[jgmac1106] joined the channel
#
[schmarty] GWG: keeping it a secret?
EncryptedGiraffe joined the channel
nertzy, dodo2, jeeyoon, [aciccarello], IWSlackGateway, IWDiscordGateway and haskell_is_no_ha joined the channel
#
haskell_is_no_ha Hello everyone! I'm attempting to host a React website I built on a local machine running a LAMP stack. I'm able to see my webpage on my LAN when I access it using the domain name, and the DNS hookup works fine. However when I attempt to access it the same way via WAN, it times out. I feel like I'm missing something fundamental here, I think I've properly set up the port forwarding (port 80, and the ipv4 address
#
haskell_is_no_ha for the machine running apache), so I don't think that's the problem either. Did I just miss a step somehow?
