#[catgirlinspace]new idea. i just, do relmeauth on my own site for auth. except itd just be github oauth. no passwords to store then and i dont have to learn how to use webauthn which makes like, 0 sense...
#[snarfed]any thoughts? BF currently supports 410, and it has a request for u-unfollow-of also, but I'm inclined to say no, that plus a UI for it is enough
#aaronpkpublic content should be public content and you can read it without the publisher knowing who you are. If you want to publish content for a specific audience, you can give them a way to authenticate, at which point you should know that they are fetching your content
#aaronpkblogrolls are a good way to share links to things you're following, but that is different than a follow post and doesn't need to overlap
#[snarfed]agreed, following in a reader is internal to the reader, no need to publish anything. I guess then I wonder how much blogrolls and follow posts should/could overlap? could a blogroll just be an h-feed of h-follow-ofs?
#aaronpkAdding structure to a Blogroll seems useful, and that sounds like a reasonable way to publish it in HTML instead of OPML
#[snarfed]this also implies that tools like Bridgy Fed shouldn't actually expect to handle follow/unfollow via webmention + mf2. following in readers or BF would generally only be in their UIs
#[snarfed]interestingly social networks kind of take the opposite tack. following someone both follows them (ie adds them to your timeline) _and_ shows them in your following list (equivalent to blogroll/list of follow posts), which is public if your account is public
#[snarfed]ugh this kind of functionality analysis and synthesis is not my strength, needs [tantek] [KevinMarks] and many of the rest of you all
#[KevinMarks]Follow was later - subscribe was the original verb for feeds. Follow was by contrast to Friend which needed approval by the person.
#[KevinMarks]We have struggled with it historically - I think the original xfn discussion suggested diffing the follows over time to see changes.
#[KevinMarks]It was added as a verb in AS1 because there was a common pattern of sites publishing follows in the users feed
#[KevinMarks]AP took that follow verb and made it imperative rather than reporting.
#[snarfed]also AP needed it architecturally, for the protocol, independent of any user-facing terminology or features
#capjamesgI am unsure whether mf2/webmention following is in scope for BF right now given the lack of people publishing / interested in processing follows outside of AP.
IWSlackGateway, [snarfed], [snarfed]1, [aaronpk], [aaronpk]1 and [aaronpk]2 joined the channel
#[aaronpk]sorry [snarfed] your last 2 messages didn't go through the gateway because I was messing with it
IWSlackGateway joined the channel
#[0x3b0b]I think there are a few aspects of BF where the decisions are likely to be different depending on whether you are trying to provide Least Surprise for the side being bridged to or the side being bridged from...
[schmarty] and [tantek] joined the channel
#[tantek][snarfed] is right that both models are likely useful, for different use-cases. And there are more like the Dopplr model
#[tantek]I think it would also help to document the various friend follow request-follow allow/follow UIs across silos and software
[catgirlinspace], [aaronpk], IWSlackGateway and [snarfed] joined the channel
#[snarfed]0x3b0b yup! bridges are an exercise in compromise
#[tantek]aaronpk @vocab is how LD does mapping between different property names (URLs) that have the same semantics I believe so that a "full LD processor" can treat them as the same thing in memory or something
#[tantek]No @context maps short property names into long URLs
#aaronpk> @vocab is used specifically to declare a default vocabulary from which all terms derive, without having to declare specific mappings for each term (as you normally do in a @context).
#aaronpki really want a way to just upload a photo from my phone and have it post on my website with the date from the metadata on the photo
#[snarfed]extracting and using date from EXIF sounds doable entirely inside your own web server, doesn't really need any standards anywhere other than EXIF, right?
#aaronpki might do it as a one-file micropub client I can post to from a shortcut
#aaronpkI know Shortcuts can also extract the date but it always takes me longer to create and debug shortcuts
#ZegnatI think petermolnar is/was displaying a dump of the photo’s EXIF data next to it on his site? Looked pretty straight forward
tabi, tabi1 and aaronpk_web_test joined the channel
#[catgirlinspace]i wannya do something where i can upload pictures to my website and it stores the original + a version where gps is removed, then display the safe version publicly along with a little display for the other exif data for like, camera used and stuff.
tabi2, tabi3 and tabi4 joined the channel
#GWGI would do what you said as well, but how would I tell the Micropub endpoint to behave that way? Custom instruction?
#aaronpkwhy would you not want it to always do that? also it seems not a feature of the micropub endpoint but of the website when it displays the photo
#aaronpklike, store the original, and display a subset of the info. similar to how you often want to display a scaled down size
IWSlackGateway, [aaronpk] and aaronpk_web_test joined the channel
#GWGaaronpk: If I upload a photo it stores that information in my site already... but it doesn't set the publish or location property of a post based on it
#GWGI was talking about an instruction to set post properties from the photo property
#aaronpkWhy do you need an instruction? Why not do it always?
#aaronpklooks like it represents a rectangle of the main subject of the photo
[schmarty] joined the channel
#[schmarty]You're getting close to my ideal checkin client! Use time and location data from one or more photos, reverse-geocode for address, optional comment and tags, tadaaaa
#[tantek]only for new venues presumably. if you've checked in there before, you can likely re-identify when you're at the same venue and skip all the reverse geocode hoohaw
#aaronpkwell that just means you're reverse geocoding against your own location database
#aaronpkand that still has problems in dense areas, but does help a lot
#aaronpkfor a while i was doing auto-checkins, if I was in a location for more than 10 minutes it'd check if there was an unambiguous place I had been to previously and check me in automatically
#[tantek]heck, if you're following friends checkins, cache all their venues as well, and use those as an L2 location cache even for first time checkins at venues
#[tantek]my guess is that would drop the number of new to you and all your friends venues checkins down to <1% of all your checkins
#[tantek]beyond that you could add an L3 location cache by preloading venues adjacent to venues you've been to before, or for any street segment with 2+ venues you've checked into, preload that entire segment of venues into L3
#[tantek]having your prior venues (L1), your friends prior venues (L2), and pre-loaded adjacent / same-street venues (L3) in a cache means you can load that cache clientside and eliminate network latency for my guess is 99.9% of checkins, especially in urban areas.
#[tantek]this is useful because many "free" reverse geocoder services have API call frequency limits
#aaronpkbased on my auto-checkin experience, I completely agree that using a local venue cache first will give you a huge benefit for the use case