Dave Maze
https://twitter.com/davemaze
•
Jan 23
what’s your favorite? i’ve been just doing old fashions
-
Dave Maze
https://twitter.com/davemaze
•
Jan 23
My summer go-to is a Negroni (gin, campari, vermouth, bitters), winter is Boulevardier season (bourbon, campari, vermouth, bitters). Can you tell I like Campari? -
now you're speaking my language!
-
Johannes Ernst
https://twitter.com/Johannes_Ernst
•
Jan 23
And to this day, nobody knows how to label uSD cards.
to be fair I don't label any of mine anyway -
-
Ben Werdmuller
https://twitter.com/benwerd
•
Jan 23
I just ordered a Post-It printer, and I have no regrets about it.
Wait what's a post-it printer? Is it smol and cute if so I must have one -
Anders Pitman
https://twitter.com/anderspitman
•
Jan 23
I'm imagining a world where email servers handle identity, and authorization servers handle delegation, after confirmation ownership over the email identity.
While that sounds nice in theory, the real world is more complicated. Apple's OAuth server is a great example. User IDs are scoped to the app to prevent cross correlation, and the app gets a proxy email instead of the user's real email. Users don't always want to be identified. -
Anders Pitman
https://twitter.com/anderspitman
•
Jan 23
Don't get me wrong, I think URLs for client IDs is a great idea, which I intend to use. I'm just less sold on URLs for user IDs. Everyone already has email addresses, and they also come with a relatively reliable protocol for contacting the owner.
I was trying to say feel free to pick and choose and use just the client ID part. I think that'd be a huge benefit for OAuth as a whole for the exact kind of use case you're talking about.
-
Anders Pitman
https://twitter.com/anderspitman
•
Jan 23
Ahhh that's what IndieAuth is. I was reading up on it, but didn't see any information about the spec on the website. I think my main hesitance towards it is the use of domains. I just don't see the average user buying their own domain. Emails seems more realistic for unique IDs.
Doesn't have to be a top level domain, just a URL. Both users and apps are identified by URLs.
I do think there's value in just client IDs being URLs in some cases, demonstrated by the fact that Home Assistant picked out just that part of the spec for their OAuth API. -
Anders Pitman
https://twitter.com/anderspitman
•
Jan 22
have their own custom domain for their instance, hosting an auth server. If someone wants to develop an app to talk to my service, they would have to register it with the instance of every user, which is impossible. Am I missing something? 2/2
You're not wrong.
You may want to give this a read, which addresses that exact problem: https://aaronparecki.com/2018/07/07/7/oauth-for-the-open-web
We use this a lot for the case you're talking about, where app developers have no relationship with the OAuth service the app is talking to. -
nystudio107
https://twitter.com/nystudio107
•
Jan 22
Ironically, I have no microformat code on the site. It's pulling that from the JSON-LD "sameAs" URLs, I presume.
Microformats != Microdata
https://microformats.io
tbh I also can't stand the itemprop= itemscope= stuff, it's so messy. That's why I like the Microformats approach instead. -
Chris Ferdinandi ⚓️
https://twitter.com/ChrisFerdinandi
•
Jan 22
"Do what Google says" means we should all build shitty AMP sites, too.
a perfect example 😂 -
nystudio107
https://twitter.com/nystudio107
•
Jan 22
Correct, but spun off as a neutral standard, as has happened for many of the technologies that we're using today.
Regardless, Google is consuming only JSON-LD going forward for some types of structured data, so it'll end up being a choice you have to make at some point.
Like I said already, only if you care about SEO. If SEO is your goal, you do what Google says. There's plenty of uses of structured data outside of that (including the tools that I use to read and post to Twitter) which are easier done using Microformats -
nystudio107
https://twitter.com/nystudio107
•
Jan 22
This implies http://schema.org is invented by Google; it isn't.
"Since April 2015, the W3C http://Schema.org Community Group is the main forum for schema collaboration, and provides the public-schemaorg@w3.org mailing list for discussions."
http://schema.org/docs/about.html
Literally on http://schema.org... "Founded by Google, Microsoft, Yahoo and Yandex..." and look at the names on their about page too. Even if it's not created exclusively by them (which I never said), that looks an awful lot like an oligopoly to me anyway. -
Aaron Bradley
https://twitter.com/aaranged
•
Jan 22
What Google sayx. And Bing. And Yahoo. And Yandex.
But if all you care about is SEO by all means use what you perceive as the flavor of the day. But if you also care about a robust, developer-friendly, serialization format for linked data then JSON-LD is there for you.
Frankly "linked data" is not a priority for me. There's plenty of useful structured data that is not LD, and tbh most developers who use JSON-LD don't even know about the LD part, they just copy the examples and wonder why they have "@context" everywhere -
nystudio107
https://twitter.com/nystudio107
•
Jan 22
Unless I'm missing something, this chart is lacking 2017, 2018, 2019, as well as 2020. Google is strongly recommended JSON-LD usage today, and has been since 2016-ish.
And there are a number of rich snippets that _only_ work as JSON-LD.
https://developers.google.com/search/docs/guides/intro-structured-data
Yes, read the linked post, it's from 2016 -
Aaron Bradley
https://twitter.com/aaranged
•
Jan 22
I know that you're a huge microformats fan Kevin, but among other things: 1) they're not remotely expressive enough for contemporary structured data requirements; 2) they're HTML-bound, meaning you can't provide data like this https://developers.google.com/actions/media/how-to/create-a-feed
If all you care about is SEO then do whatever Google says to do this year and you're fine. Today that's JSON-LD, tomorrow it's ???? I need to update this chart for 2020 but as we see, history keeps repeating itself. https://aaronparecki.com/2016/12/17/8/owning-my-reviews#historical-recommendations
-
Aaron Bradley
https://twitter.com/aaranged
•
Jan 22
I know that you're a huge microformats fan Kevin, but among other things: 1) they're not remotely expressive enough for contemporary structured data requirements; 2) they're HTML-bound, meaning you can't provide data like this https://developers.google.com/actions/media/how-to/create-a-feed
You might be surprised what you can do with Microformats...
https://aaronparecki.com/2018/03/12/17/building-an-indieweb-reader
Even this tweet originated from my own website using tools built on Microformats. -
K. Mike Merrill
https://twitter.com/kmikeym
•
Jan 22
Like Netflix I also use my own private internal measurement that I only occasionally release for stats and yesterday I had 87,000,000,000 views on my website. https://buff.ly/30HVBXk
the guy that runs your website must be really good -
Henrique Dias
https://hacdias.com/
•
Jan 22
Hey Aaron! What software/library are you using to generate those maps with your location? Can they be considered heat maps? And what about the animated video?
It's all a giant pile of PHP code I wrote ages ago, it's not even map-projection-aware it just plots on a 2D canvas. The animation is basically a timelapse of a bunch of frames of that same script played in a row. -
Dave Maze
https://twitter.com/davemaze
•
Jan 21
nice! i’m sure you learn stuff from work that you can utilize for your personal.
