Paul Lindner

Some notes on my #indieweb experience.

#indieweb #gplus

I'm still pretty happy my indieweb publishing experiment.

Content is flowing in all the right ways.  Posts end up as Posts.  Photos are uploaded native with backlinks. POSSE via brid.gy just works.  You can see that Brid.gy polls Google+, and then saves what it finds back to the original post by sending Webmentions.  The result is a full archive of activity around this content.

Oh and cross posting to SoundCloud worked perfectly.  And so do embeds..

After a fix from the Known Team WebHooks are working.  I get a POST whenever content changes.  To test this out I send the URL to the Internet Archive Save Page.  Voila!  Instant archiving of my content.  [Next up, backups in IPFS]

I was able to set up the Known open source software on my own server.  Next step is to pull a backup from the hosted version I'm using so I can experiment further and contribute back to the project.

Mobile Posting via Chrome on Android is working well.  You can access the Camera and a rudimentary file picker.  HTML editing is workable, but not great.  I installed the Url Forward app so I can also have native sharing intents.

Bumps

Of course there are some issues encountered...

Spelling errors mean you Publish Once, Edit Everywhere.  Or if you messed up the URL, Publish Once, Delete Everywhere

I tried using a native web mention to reply to another post, but it didn’t appear on the target site.  There wasn't any visible UX feedback.

I found that there’s no UI support for backdating posts.  Okay, I’ll try Micropub to post.  Nope, very rough implementations, but Quill seems nice.  Eventually I wrote a stub post in Wordpress, exported, imported and edited.  Phew!

But.. it appears that brid.gy doesn’t syndicate to old posts like this.  Even when I went back and pointed links at each other.  I’ll have to followup on that.

Also, I lost the first version of this post due to a CSRF error since I left it sitting too long in the browser.  Oops.

TinyMCE still is a pain and loves using &nbsp; and CMD-9 is bound to <address>..   I might have to use Markdown instead.

I miss @ mentioning people, and wish there was a UI for that.

Native Google+ support in brid.gy needs an API.

But still overall quite happy with the way this is going.  I hope you're enjoying the journey with me.

Tagged: #indieweb #withknown

*Good*: Facebook killed the profile 2 minutes after I reported it for impersonation. Also a great way to get in touch with old friends as they ask 'was that you?'.

*Bad*: the grammar.

*Ugly*: 19 people had friended that profile before it was taken down.

Be vigilant out there....

https://plus.google.com/photos/107786897865850743842/albums/6325073859824754257/6325073857645853762?...

#googplus

#googplus

Handwritten in pencil.

Yours truly,
Paul

#googplus

End of day #1 with Known.  I'm quite pleased with the results.

Good Stuff

• brid.gy is awesome.  Having +1's, likes and comments consolidated is so nice.
• Webhooks!  I'm thinking of writing one to automatically archive pages to archive.org.
• PuSH appears to be fully working.  Again, could extend things there..
• Google+ renders images well.
• The editor saves drafts.
• Lightweight page editor should be useful.
• AMP support is there (add ?_t=amp to any page)  Some validation issues, but works.
• Real anchor tags and hyperlinks.  No more writing [1] [2] in posts with multiple links (like lynx)

Rough Edges

• The built-in Photo type doesn't send the permalink to Twitter, so now I have a weird post without context.  Flickr, Facebook working perfectly, might try another setting.
• I need to get to writing a Google+ outbound connector.  I'm doing those by hand now.
• TInyMCE sucks.  It has always sucked!  If only Medium would open source their editor.  At least markdown is an option.
• Looks like syndicated Google+ links are using profiles.google.com instead of plus.google.com.
• Some profile pics cloned from G+ are coming back with size 0.  This shows as broken images.
• Long status posts have extra long permalink URLs.
• Built-in analytics are weak.  Would rather avoid using GA for that.
• Limited import options.  Will need to convert Typepad export file to Wordpress format.
• Bulleted lists line-height is tight, tight, tight.

Overall I'm pretty happy and excited about getting more content in place.

And who knew that a post on SSL/TLS certs would be soooo exciting?

Tagged: #indieweb

Look at that upstream rate from the KMTel's (http://kmtel.com) $45 fiber plan.

... as I sit here with 20% Comcast packet loss on my 30/7 for double the money.

An interesting article about this phenonemom:

http://www.yesmagazine.org/new-economy/tired-of-waiting-for-corporate-high-speed-internet-minnesota-...

#gplus

This is an experiment.  Can I take control of my online life and move it to a place where I have more control?  Can I pull my content out of multiple silos?  And can I import existing content from other platforms and keep it (somewhat) synced over time so I have a full record of my public online life?

We're going to find out..

The trigger for me was an article about my early days working with the Internet Gopher Community.  I had saved most of the email from back then and it was quite easy to reconstruct and remember what happened.  I don't think I'll have the luxury for much of what's happening recently.  The digital ephemera is spread out too far and wide to reconstruct and reflect.

To get there I'm experimenting with the hosted version of Known, a publishing platform that supports the things that matter to me.  I like that it's open source, interoperable and respectful of human effort -- it also supports a number of Indieweb technologies out of the box like WebMention, and brid.gy to pull back content from the Silos.

So.. you're going to see more content in more places as I'll be syndicating out to Facebook, Twitter, LinkedIn and Google+.  And I'll be sharing more as I document this process.

Silos by Doc Searls / CC BY 2.0

Tagged: #indieweb

Regarding cuts, yes. We had to do with less year-over-year. From Hasselmo's 1991 State of the U address:

> """We lost at least 5 million to inflation, and 6 million through a base cut this year. In addition to a potential 5 million loss to inflation next year again, the Governor's vetoes of IT and systemwide special appropriations cut another 3 million in funding -- for which we are aggressively seeking full restoration."""

The mainframe teams had a harder time of things. For Microcomputers we were lucky - our hardware costs decreased and we had a deal with the University Bookstore to support their computer hardware sales.

That stuff was still expensive. Here's some educational pricing for a workstation with substantial education discount in 1994.

                                        list          discount   
  IBM model 25T                         495         400.00
         80Mhz upgrade                  500         $ 953.50
         64MB upgrade                   $             912.00
         2GB disk upgrade               $             463.00
                                                       -------
                                                      10728.50

We liked Hyper-G because it had a bi-directional link model and the Harmony browser was able to render VRML.

Maybe 2016 will be the year VR takes off (again)

This is so true. You have to remember that finances were really tight at this time. The University budget was getting cut left and right throughout the history of Gopher's evolution. At one point there were plans to outsource everyone to the Minnesota Supercomputer Institute.

Of course in hindsight obtaining grants or forming a partnership with a non-profit org or an academic department might have been a better choice, especially for all the professional services requests.

edit: Also you have to remember that computing was a LOT more expensive then. I have old quotes for SparcStations and RS/6000s that were in the 0-40k range, even with an educational discount.. The Mac IIci's were not cheap either ~k when loaded up with RAM.

Twenty-five years ago, a small band of programmers from the University of Minnesota ruled the internet. And then they didn’t.

Read more at The rise and fall of the Gopher protocol via MinnPost

Tagged: #gopher

On: Google+, Facebook, LinkedIn

Hmm, I wonder what s/Node_Modules/blaze-bin/ would reveal..

PB for evil respect to anyone that can implement Hot Pockets example...

https://medium.com/friendship-dot-js/i-peeked-into-my-node-modules-directory-and-you-wont-believe-wh...

#googplus

#googplus

Given all the #firstsevenjobs posts going on I decided to see if I could find my first published source code. And lo and behold the Internet Archive FTW.

https://archive.org/details/1987-06-compute-magazine

As for 1st 7 jobs: Fish House Cleaner, Dock Boy, Rock Picker, Upholsterer Assistant, Commodore 64 hacker, Injection Plastic Press Operator, Library Book Shelver.

Cleaning up stinky crap and rote mechanical tasks? -- I'm your guy.

#googplus

#googplus

WebTorrent one-off file sharing in the browser.

This link will die when the last person closes their browser tab..

https://instant.io/#120d24519a9789b9a0890ba3944e55ab2831b53b

mmm spaghetti

https://instant.io/

#googplus

#googplus

Orkut.com is back. Promoting hello.com

Of course Orkut could probably retire just by serving ads on 404 responses.

http://orkut.com

#googplus

#googplus

I found my first email to Google. From the year 2000. Since then I've worked through five companies, but Joan Braddi is still here.

And since I'm on the inside now I was able to find the that cl #8802 referenced the work I was doing at the time, which was adding search to www.redhat.com. (Or Red hat, as you can see here)

https://critique.corp.google.com/#review/8802/depot/eng/clientwork/CompletedSites.html

I do have to wonder if Red Hat's slow payment of their 5k+ contract fees hurt the early Google, or what might have happened had Google gotten into the RPM search field as I suggested to them way back when...

And for a real blast from the past see the search stats that were emailed out monthly(!)

https://groups.google.com/a/google.com/d/msg/partner-reports/XiVcELeVONc/AtcwCeBS7uYJ

#googplus

#googplus

I asked an SRE intern if they ran their own server. Said no; but at least they had their own VPS. Made me realize how much I've learned by maintaining a home server for the past 16 years.

While I don't run my own email anymore I still have secondary DNS, NFS, Plex, Docker, IPv6 tunnel and local LAMP stack for projects.

I can highly recommend the Supermicro you see here. 20-30w at idle, super quiet, 8 cores, up to 128GB of RAM, 10GbE, NVMe and much more. I've been running this for 7 months now and it was a big improvement over the Rackable I used to run.

http://www.servethehome.com/supermicro-sys-5028d-tn4t-review-small-box-big-power/

#googplus

#googplus

Ello ships their version of Wanderland focused on their artist/creator content.

The interesting part is they let you flip between:

Discover, Followed and Starred

Worth a look.

https://ello.co/discover/all

#googplus

#googplus

*Uninvited Guests* - Human Agency[1] vs Machine Agency.

I found this gem via a CHI paper. I think it covers a number of pitfalls that can be avoided by insuring that we're designing products that emphasize Human Agency. It also underscores how privacy (especially between the device owner and the device user) is critical.

Also consider if instead of grandchildren the devices were provided by the NHS or Medicare.

[1]https://en.wikipedia.org/wiki/Agency_(philosophy)

Ultimately it is our intention that this, at times comedic story, plays on and gives form to some of the growing tensions between human and machine agency. And in doing so, provoke questions about how we want to live and grow old in an increasingly technologically mediated word.

http://www.superflux.in/work/uninvited-guests

#googplus

Interesting ideas that protocols can be monetized thus leading to more diversity.

I'm not sure I agree with the premise. Large players have many more levers to get their protocols adopted and defend their turf.

There's also the risk that all new protocols will _require_ monetization so governments and internet infrastructure orgs can extract rents/taxes from the activity on the network.

On the other hand if the Gopher Protocol was monetized I might be sipping drinks on the beach instead of toiling in the protobuf mines...

http://continuations.com/post/148098927445/crypto-tokens-and-the-coming-age-of-protocol

#googplus

#googplus

Metastatic isn't something you beat, it's something you live with.

#gplus

Also there's this: _Diverse teams that design for themselves are able to address the needs of diverse audiences, as opposed to teams that design for ‘the other’_

https://ind.ie/ethical-design/

#googplus

#googplus

Current status: detangling legacy code that uses fava extensions, modules and services wrapped in factories.

https://archive.org/details/p3telephonymanua00abbouoft

#googplus

Lots to think about today:
- Everyday uses for the Optimal Stopping problem.
- Application of Ad Algorithms for Exploit vs Explore. [1]
- Sorting algorithms for unreliable comparators
- AI Ethics: Paperclip Maximization[1] and the Repugnant Conclusion[3]

All after watching this:

http://longnow.org/seminars/02016/jun/20/algorithms-live/

And I now have yet another book to put on my reading list....

[1] https://en.wikipedia.org/wiki/Multi-armed_bandit
[1] https://wiki.lesswrong.com/wiki/Paperclip_maximizer
[2] http://plato.stanford.edu/entries/repugnant-conclusion/

http://algorithmstoliveby.com/

#googplus

#googplus