#LoqiDisappointed that Ghost created a custom posting API instead of adopting Micropub, which is a W3C recommendation. It’s okay to have Ghost-only APIs as long as you start with standards as a baseline. Now we have fragmented client apps.
#ZegnatGhost to me has always felt like they are just doing their own thing
#ZegnatBut would definitely have been nice if they had used Micropub
loicm, [frank], [jgmac1106], [tonz], jeremych_ and [calumryan] joined the channel
#[calumryan]I know one of their developers comes to my local web meetup group, will bring up Micropub with them and encourage them on here
#petermolnarbecause I see ld+json in examples LD, but also json+oembed for oembed
#Zegnatoh, interesting, I would have expected oembed+json
#ZegnatBut maybe oembed defines its own parsing spec
#ZegnatWhy does the easyrdf converter add XSD type declarations on every one of your values, petermolnar :S
#ZegnatI do not think that is a turtle requirement at all
#petermolnar^^^ famous last words before diving into RDF specs :D
#ZegnatLets just say I know it is an option, but I do not remember seeing anyone actually doing it back when I was looking at turtle for a SOLID implementation
swentel and [Rose] joined the channel
#[Rose]Does anyone have a good link they can share which is basically "crash course in unit tests"? PHP specifically if that helps, the program I need to create them for did not use a framework
[tonz] and [coreagile] joined the channel
#[coreagile]While I have practiced TDD for many years, I'm not a PHP programmer. So, take this recommendation with a grain of salt. 🙂.. https://course.testdrivenlaravel.com/
#ZegnatIt is a good example of how minimal first tests can be :) I would personally avoid loops within single tests. Instead I would have wanted to create a data provider that read all the separate JSON files and then have the test method run on each separate file that way
#ZegnatBut I will not claim to know what actual best practices are.
#ZegnatThe single method should really only test 1 thing, separation of concern. Though yours just test the validity of the JSON, so that seems right. But then the test method itself should not busy itself with having to fetch data to test.
swentel joined the channel
#ZegnatNot sure if other people do it like that, but it is how I have been approaching it. cweiske probably has better opinions
#cweiskeour tests always fetch the data they are validating
#aaronpkone of the reasons I *dont* like things like that, while "better", is that it makes it harder to figure out what's going on by reading the code
#cweiskeonce you got a basic understanding of writing tests, you can dig deeper and try to use data providers
#aaronpkThe reason i have that test there is because people hand make those JSON files and send pull requests and I want to make sure the JSON is valid before someone can make the PR
benwerd, [davidmead] and snarfed joined the channel
jbove, benwerd, [kevinmarks], [kevinmarks786], gRegorLove__, [tonz], [chrisaldrich], snarfed, KartikPrabhu and [tantek] joined the channel
#sebselSo, for authentication, Microsub points to Micropub. Then enter into the real of tokens and all that stuff. To verify a token, I should check the token endpoint. Should I check for *every* microsub request made to my server?
#sebselFor Micropub that seems fine, because who's posting more than 20 posts a day? (:'D) but for microsub... it's easy to spam token endpoints when scrolling feeds.
KartikPrabhu joined the channel
#sknebeltrue, it's a different rate - for now, we generally assume requests are cheap. if you don't, revocation would not be immediate. I'd suggest a) measuring your request patterns and b) then see how much a really short-term cache does
#Loqi[Ryan Barrett] Bridgy
hit 1000
unit tests last night!
436 in Bridgy itself, 508 in
granary, 56 in
webutil. Silly milestone, but I still got
excited. Go team. Next
up, 2000!
#jackywow! the things we do to make sure nothing goes bump in the night
#jackysknebel: my way around that might be preventing those posts from using slugs (in Koype, it's either a slug or the internal post UUID that's shown which is meaningless to humans)
#sknebel(e.g. Github shows 404 for repos you can't acess, but they have names in there that might have strong relevance)
#[eddie]It's tough, because I'm thinking if I might have pages that I would send to family to login (like family photos or something), I would probably want the page to say "Login to view"
#[eddie]because my family would probably be confused if they reached a "This post doesn't exist" page before they were logged in
#[eddie]Since it's still in the "probably only techy people will be dealing with my private posts" phase, that's why I currently return "Does not exist" in the HTML and 403 as the HTTP status
#sebselyea, I do 401 for non logged in users and 403 for logged in users who don't have the right permissions
#[eddie]I won't be AT the summit in person, so I can't really show viewing anyone else's stuff. My mine is close enough to being finished that I could post private content including a private reply that could be used in a collaboration demo