When I saw a speculative article about Google wanting to “kill” URLs appear in my news feed, I didn’t think too much about it. Trying to hide “ugly” URLs… well, that feels like a natural thing for an app to try and do. Designers of apps often (erroneously) assume that users cannot cope with “technical” things like URLs and try to hide them away, lest the user start bleeding from their eyes.
I generally like where John is taking this idea and the fact that he’s actively experimenting and documenting what he’s coming up with as potential solutions. While I do like some of the low-tech angle that he’s taking, I’m not sure, based on what he’s written, how some of it will come out within the broader spectrum of DoOO or IndieWeb-related technologies.
- How easy/hard will it be for students to own/export their data after the class?
- How might they interact if they’re already within the DoOO cohort or already self-hosting their own space?
- What are the implications for students of maintaining multiple spaces with a variety of technologies and therefor overhead?
- I’ve never had a lot of luck with Disqus, which I find to be heavy and often has problems with auto-marking all of my content as spam. I’ve definitely found it to be an issue with using for POSSE workflows. Worse, with the introduction of specifications like Webmention to the DoOO space, students could be writing their responses to classmates and teachers on their own sites and thereby owning all of that content too, but with Disqus, this just isn’t possible.
I’ll reserve judgement for once I’ve seen some of the code and further ideas in parts II and III as I suspect he’s likely taken some of these issues into account.
We’ve played with this concept of front-end blogging for a while now. Alan Levine has built an open sourced tool called TRU Writer that even provides this type of front end interface on a WordPress site. ❧
I’m curious if John, Alan Levine, or others have yet come across the concept of Micropub? It generalizes the idea of a posting client and interface so that it could work with almost any CMS-related back end. I could see people building custom micropub clients for the education space, or even using some of the pre-existing ones like Quill, InkStone, or Micropublish.net. Many of them also use JSON or form encoded data that they could also be using with platforms like the one John describes here. The other nice part about them is that they’re flexible and relatively open in more ways than one, so they don’t necessarily need to be rebuilt from scratch for each new CMS out there.
Commentary: Fortnite gives Google the middle finger, but both are failing us to some degree.
30% is a pretty high tax, particularly for such a massively large platform versus the direct costs for maintaining it. One would think that at their scale the cost would be significantly lower.
The Data Transfer Project was formed in 2017 to create an open-source, service-to-service data portability platform so that all individuals across the web could easily move their data between online service providers whenever they want.
The contributors to the Data Transfer Project believe portability and interoperability are central to innovation. Making it easier for individuals to choose among services facilitates competition, empowers individuals to try new services and enables them to choose the offering that best suits their needs.
Current contributors include: Facebook, Google, Microsoft, Twitter
The Data Transfer Project makes it easy for people to transfer their data between online service providers. We are establishing a common framework, including data models and protocols, to enable direct transfer of data both into and out of participating online service providers. http://datatransferproject.dev
cross reference: https://boffosocko.com/2018/07/22/data-transfer-project/
In a blog post, Google has admitted the newest version of Chrome rolling out to customers worldwide is going to consume up to 13% more of your system memory. For a browser whose biggest failing has long been its excessive memory consumption (1,2,3,4,5), this is the last thing users will want. Especially those with older systems and less RAM. Google also confirmed this is a cross-platform change and will apply to Chrome on Windows, Mac, Linux, and Chrome OS. The last of these could be particularly impacted as Chrome OS systems often ship with only 4-8GB of RAM.
Painfully bad clickbait headline to say that their browser will be slower to protect against Spectre.
New data shows the impact of Facebook’s pullback from an industry it had dominated (and distorted).
(Roose, who has since deleted his tweet as part of a routine purge of tweets older than 30 days, told me it was intended simply as an observation, not a full analysis of the trends.)
Another example of someone regularly deleting their tweets at regular intervals. I’ve seem a few examples of this in academia.
It’s worth noting that there’s a difference between NewsWhip’s engagement stats, which are public, and referrals—that is, people actually clicking on stories and visiting publishers’ sites. The two have generally correlated, historically, and Facebook told me that its own data suggests that continues to be the case. But two social media professionals interviewed for this story, including one who consults for a number of different publications, told me that the engagement on Facebook posts has led to less relative traffic. This means publications could theoretically be seeing less ad revenue from Facebook even if their public engagement stats are holding steady.
From Slate’s perspective, a comment on a Slate story you see on Facebook is great, but it does nothing for the site’s bottom line.
(Remember when every news site published the piece, “What Time Is the Super Bowl?”)
This is a great instance for Google’s box that simply provides the factual answer instead of requiring a click through.
fickle audiences available on social platforms.
Here’s where feed readers without algorithms could provide more stability for news.
Google’s unofficial motto has long been the simple phrase “don’t be evil.” But that’s over, according to the code of conduct that Google distributes to its employees. The phrase was removed sometime in late April or early May, archives hosted by the Wayback Machine show.
A subtle, but interesting change. Most importantly does this portend a broad change in corporate philosophy?
The archival Web—the one you see through the protocol HTTP—will soon be condemned, cordoned off behind Google's police tape, labeled "insecure" on every current Chrome browser. For some perspective on this, imagine if suddenly all the national parks in the world became forbidden zones because nature created them before they could only be seen through crypto eyeglasses. Every legacy website, nearly all of which were created with no malice, commit no fraud and distribute no malware, will become haunted houses: still there, but too scary for most people to visit. It's easy to imagine, and Google wants you to imagine it.
Google's partnership with WordPress aims to jump-start the platform's support of the latest web technologies -- particularly those involving performance & mobile experience. And they're hiring WordPress experts.
Contributing back to the community is an interesting way to go, though I’m curious how readily the community will pull the pieces back, particularly into core. This is certainly a better modus operandi than attempting to press forward on AMP technology.