Statuses

Reply to Jaredewy

Replied to a tweet by Jared EwyJared Ewy (Twitter)
@Jaredewy With your domain name, I think that you automatically win the .
I’ve had refbacks on the brain for the past couple of months after having read Why Refback Still Matters, so I figured since I’ve already got the pingbacks, trackbacks, and webmentions enabled, what’s one more way to communicate with my website from the outside? So as of this evening, just for fun, I’m now accepting refbacks too.

Besides earlier this week I joined my first webring in over a decade as well. It can’t be any more embarrassing to support old web tech can it?

 

I’ve come across many journals (and particularly many talking about Altmetrics1,2) that are supporting the old refback infrastructure and wonder why they haven’t upgraded to implement the more feature rich webmention specification?

I’ve been thinking more lately about how to create a full stack IndieWeb infrastructure to replace the major portions of the academic journal ecosystem which would allow researchers to own their academic papers but still handle some of the discovery piece. Yesterday’s release of indieweb.xyz, which supports categories, reminds me that I’d had an idea a while back that something like IndieNews’ structure could be modified to create a syndication point that could act as an online journal/pre-print server infrastructure for discovery purposes.

A little birdie has told me that there’s about to be a refback renaissance to match the one currently happening with webrings.

References

1.
Akers KG. Introducing altmetrics to the Journal of the Medical Library Association. Journal of the Medical Library Association. http://jmla.mlanet.org/ojs/jmla/article/view/250/403. Published July 3, 2017. Accessed July 2, 2018.
2.
Roemer RC, Borchardt R. Chapter 2. Major Altmetrics Tools. ALA Tech Source. https://journals.ala.org/index.php/ltr/article/view/5746/7187. Published July 1, 2015. Accessed July 2, 2018.

QuantaMagazine.org orphans all annotations

Filed an Issue hypothesis/h (GitHub)
Annotate with anyone, anywhere.

Steps to reproduce

  1. Annotate any particular individual article on https://www.quantamagazine.org/
  2. Links to the annotations are redirected back to the root domain and not the individual page

Expected behaviour

The links should direct to the canonical URL of the article

Actual behaviour

All the annotations to individual pages seem to automatically become orphans and are associated with the root domain instead of the individual permalinks.

Example: The annotations at https://hyp.is/lUpgtn15EeivjHMsJK03Tg/www.quantamagazine.org/ and https://hyp.is/6C98en11EeieFgMy1hP9tQ/www.quantamagazine.org/ on the page https://www.quantamagazine.org/mathematics-shows-how-to-ensure-evolution-20180626/ don’t resolve properly because of the orphaning issue on this website.

Browser/system information

This is happening to me on a variety of browsers on Windows 8.1 and Windows 10 including: Chrome 67 and Firefox Quantum 60.0.2 (64-bit).
It also appears to be an issue on both the current versions of Chrome/Firefox on Android v8.0.0

Additional details

I’d guess that the issue is site specific to quantummagazine.org somehow.

Reply to I attended IndieWeb Summit 2018 | Fogknife

Replied to I attended IndieWeb Summit 2018 by Jason McIntosh (Fogknife)
Notes and thoughts from the eighth annual IndieWeb conference, held in Portland, Oregon.

My heart forever broken by social-media silos, I’m not really interested in using Micro.blog as yet another “Okay, I’m over here now” social network. I get the impression that it has potential for much deeper use than that, if I can only get my head around it.

Micro.blog can be many things to many people which can be confusing, particularly when you’re a very tech savvy person and can see all the options at once. I’d recommend looking at it like a custom feed reader for a community of people you’d like to follow and interact with. Spend some time in the reader and just interact with those you’re following and they’ll do likewise in return.

It’s purposely missing some of the dopamine triggers other social silos have, so you may need to retrain your brain to use it appropriately, but I think it’s worthwhile if you do.

I really need to hash out my domain situation! IndieWeb encourages its memership to claim a single domain and use it as their personal stamp for everything they do on the internet. I, though, have two domains: my long-held personal catch-all domain of jmac.org, and fogknife.com, which I use exclusively for blogging. My use of both predates my involvement with IndieWeb.

Don’t fret too much over having multiple websites. As you continue on the answer to what you want to do with them will eventually emerge more organically than if you force it to. For some thoughts and inspiration, check out https://indieweb.org/multi-site_indieweb.

📺 Scalar 2.0 — Trailer | YouTube

Watched Scalar 2.0 — Trailer from YouTube

Learn about the features of Scalar, refreshed with the Scalar 2.0 interface.

This is an intriguing looking tool for potential academic use. I’ll have to find some time to download it and play around.

📺 IndieWeb Summit 2018 Green Room #nonprofit | YouTube

Watched IndieWeb Summit 2018 Green Room #nonprofit from YouTube

Discussing a non-profit org to benefit IndieWeb and the indie web

Playing catch up on some of the sessions I wish I’d had time to be at in person.

There are several ways of doing the non-profit thing in this venue. Many of them don’t bring a lot of additional benefit however. One could set up a side foundation to help on the fundraising and spending side, but as a group, I suspect we’re more than fine for right now.

Replied to Sharing brief @IndieWebSummit notes as they come to mind. by Tantek ÇelikTantek Çelik (tantek.com)
Sharing brief @IndieWebSummit notes as they come to mind.

This was the first year people pre-wrote proposals before the #BarCamp organizing session. As facilitator I decided to have people who never proposed before go first.
 
Coincidentally, @Christi3k just announced the same thing @OSBridge unconference organizing session.

This may be worth codifing as a normal practice. Let first-timers propose sessions first before anyone who has done this before, especially at an @IndieWebCamp before.

The other thing I did was, after the the first-timers finished explaining and scheduling their BarCamp session proposals, I had people *other than* the remaining session proposers choose from the remaining session proposals posted on the side of the grid, and advocate for them. I think that worked quite well for selecting for the sessions that were more compelling for more people.
I was just thinking about how this might be codified a bit better as well, particularly for folks who are attending their first BarCamp-style event.

While there is some implication in the event pages, I don’t know if some people were expecting the sessions and planning to play out the way they did (or if they knew what to expect on that front at all, particularly in chatting with people in the early morning registration/breakfast part of the day).

It was certainly more productive for me to think about and post some of the things I wanted to accomplish pre-camp. (It also helped to have your reminder a month or more ago about what I might build before even going to the summit.)

Having additional time to know what the scheduling process looks like, if nothing else, gives people a bit more time to think about what they want to get out of the conference and propose some additional ideas without being under the short time crunch. This is particularly apropos when the morning presentations may have run long and the conference is already a few minutes off track and we’re eating into valuable session time otherwise. I would suspect that helping to get the session ideas flowing sooner than later may also help the idea and creative processes, and even more so for participants who may need a bit more time to organize their thoughts and communicate them as they’d like.

I definitely liked the process of having beginners go first and then letting people advocate for particular ideas thereafter. This worked particularly well for an established event and one with so many people. It might be helpful to pre-select one potentially popular proposal from an older hand to go first though, to provide an example of the process for those who are new to it, and in particular those who might be quiet, shy, or not be the type to raise their hands and advocate in front of such a large group. In fact, given this, another option is to allow people to propose sessions and then allow advocation across the board, but for beginners first followed by everyone thereafter. This may also encourage better thought out initial proposals as well.

Thanks again for all your hard work and preparation Tantek!