#[kaushal_modi]I'm not well-versed with DDOS. I read that wiki, but still not sure what a user can do to prevent that. Looks like the prevention measure need to be taken by the endpoint? Or is there something a user (WM source/destination URL) can do too? If so, can someone point to some examples?
KartikPrabhu, EmreSoku_, eli_oat, snarfed, EmreSokullu and barpthewire joined the channel
#GWGI am having a slow time of it designing a POSSE system that takes the same input for everything but outputs to the appropriate system..be it Bridgy Publish, or a native API
#GWGBridgy Publish does this by using Microformats 2 to build a submission. I need to use the same, but where they are stored on my system
#GWGLooking at silo.pub and how it does this as well.
#kaushalmodi!tell Zegnat Thank you for your response on the DDoS issue. I have a static site. So I will have to just wait and watch and deal with the DDoS issue if it ever affects me.
#snarfedGWG: which native api(s) do you want to posse to that bridgy doesn't support? just curious
#GWGsnarfed: Too many people are blaming me for Bridgy Publish not being able to interpret their Microformats because they didn't set them up. I just want to make sure I can support them transparently if I add them.
#GWGsnarfed: I'm mostly trying to make it so it isn't a 'Bridgy Publish' plugin anymore. It's just a generic publish plugin
#snarfedsure, i understand. i read your post. :P i was just curious where else you want to add posse support for
#snarfeddo you know how you'll handle bad mf2? use the underlying wp data directly instead? you'd then need to implement all the silo APIs yourself, right?
#snarfedhey Zegnat are you awake? i think i fixed bridgy etc for your auth endpoint. mind testing? just type your url into the indieauth box on https://oauth-dropins.appspot.com/
#waglesince the hmm factor was "high", thought i'd ask around a little to see if there was any scuttlebutt
#wagledgold: need it to work for 50 years.. well, 5?
#snarfedbut again digital is arguably better there. you can keep and maintain copies of your relatives' *digital* photos, but not their paper photos
#snarfedalso the JPEG format has lasted many decades, so for just photo files themselves, no real migrations needed, just backups
#waglehavent gotten a lot of interest.. main problem now is that I have the paper copies, and they shouldn't go poof when I die.. so gotta get the two sides to saw which goes to which side of the families
#Loqisnarfed has 60 karma in this channel (382 overall)
jgmac1106 joined the channel
#GWGsnarfed: It looks like it was the improved error handling. It is only logging errors. This wasn't reported as an error, so it didn't log it. I just moved it to log everything.
#waglescan first requires that II annotate each pair of fronts and backs on the hundreds of old photos then implement a way to find the paper again.. any suggestions? or am I a pioneer?
#snarfedwagle: tons of prior art for that. google :P
#GWGsnarfed: It is trying to redirect to.. https:\/\/tiny.n9n.us\/wp-login.php?redirect_to=https%3A%2F%2Foauth-dropins.appspot.com%2Findieauth%2Foauth_callback&reauth=1&action=indieauth&response_type=id&client_id=https:\/\/oauth-dropins.appspot.com\/&state=%7B%22endpoint%22%3A%22https%3A%2F%2Ftiny.n9n.us%2Fwp-json%2Findieauth%2F1.0%2Fauth%22%2C%22me%22%3A%22https%3A%2F%2Ftiny.n9n.us%22%7D&me=https:\/\/tiny.n9n.us&_wpnonce=4935d40ed5"
#Zegnatsnarfed, I am half awake. I was able (I think) to login on the oauth-dropins.appspot.com. At least it says “ Authenticated https://vanderven.se/martijn/ on IndieAuth. ”
#LoqiZegnat: kaushalmodi left you a message 1 hour, 59 minutes ago: Thank you for your response on the DDoS issue. I have a static site. So I will have to just wait and watch and deal with the DDoS issue if it ever affects me.
#pstuifzandI could also authenticate with the oauth_dropins website, but not without adding a application/json content type first. It seems it was missing from the verification step.
#GWG!tell snarfed You are missing response_type=code . Without it, you are in the authentication, not authorization flow, which does not return a code.
#GWGsnarfed: I think I shouldn't try to troubleshoot while I'm thinking about something else.
#GWGBut, it still looks to be a urlencoding issue.
snarfed and [snarfed] joined the channel
#[snarfed]thanks for debugging GWG! not high priority, feel free to punt
#Loqi[snarfed]: GWG left you a message 16 minutes ago: I found your problem.
#Loqi[snarfed]: GWG left you a message 15 minutes ago: You are missing response_type=code . Without it, you are in the authentication, not authorization flow, which does not return a code.
snarfed joined the channel
#GWG[snarfed]: I think I did find a problem I want to fix with the workflow you are trying to use
snarfed joined the channel
#[snarfed]ok! also if you're going to test your plugin, feel free to test against bridgy instead of o-d since bridgy has actual users :P