Using the Last Seen Function in Simple Location

One of the features in Simple Location that doesn’t get much notice is the Last Seen functionality.
Simple Location adds a section to your WordPress user profile called Last Reported Location. It allows you to set the last reported location for a given user.  It reports latitude, longitude, altitude, and whether or not the location is public, private, or protected.
In the Simple Location Settings, you can set this to update each time you publish a post if the location isn’t set as private. So it would reflect the last post you made.
This feature can be used in one of two ways. You can add the Last Seen Widget to your page and display the last place you were seen. Alternatively, this can work in reverse. You can set it so your posts will set post location from the last seen location of the author.
But, what use is that if the only way a to update the Last Seen setting is to set it from a post(creating an endless loop) or to set it manually? If you always want to always set a default location, this can be an option.
However, that doesn’t work for me. So, I built a way to update your location from an outside service.
First, you need an IndieAuth token. If you installed the IndieAuth plugin, you can get one manually under Users->Manage Token.

curl -i -H 'Authorization: Bearer FAKETOKEN' -d "latitude=30&longitude=-115&visibility=public" "https://www.example.com/wp-json/sloc_geo/1.0/user"

Here is an example of updating your location via a curl command line command. It figures out which user based on the user of the token you created.
The parameters currently used are latitude, longitude, altitude(will be automatically derived if not present), and visibility(public, private, protected).
If you are successful, it will return ‘Updated’ and automatically lookup the name of the location you are at.
So, what can you do with this feature? Keeping in mind the day, though I call today Tuesday…Let’s say hypothetically you are in the package delivery business and you want to share your location with the people who are eagerly awaiting your deliveries. You could use this to send your location from your phone to your website to keep the display updated.
Alternatively, if you don’t trust the browser on your computer to know where you are, you could rig up a shortcut on your phone to update the location so it would be accurate if you post, for example on Android with Tasker.
There is more that is needed to enhance this feature. On my list for future is Geofencing…the idea of zones inside which the location would either be set to private or display a generic ‘Home’ or ‘Work’ etc. I already have the code to calculate this, but haven’t figured out how the UI would look. This would allow much more granular controls than the global privacy default.

Replied to
I question whether or not anyone will care about what I am posting publicly and often talk myself out of it. I think the question is always why you want to share the information. But I know one of the reasons is because I hope to interact with others. The pieces for interaction…the plumbing of posting and responding, consuming with a reader are coming together. There are still some gaps to make it a smooth experience for many. I have made an effort to post more. But it is how easy I have made that which helps, and how rarely it starts a dialogue that disappoints me. The incentive for public posting is interaction as private posting is just for you.

Simple Location Version 3.5.0 Released

Version 3.5.0 of my location plugin, Simple Location, is now out(forgot to push a fix and had to release 3.5.1 as well). Simple Location is, as time goes on, anything but Simple. It is all about location, including the weather at your location. It adds this to posts, and offers several simple widgets to show current weather and current location on the homescreen.
The new version completely redesigns the interface inside the post editor to work in both classic and Gutenberg. It doesn’t integrate with Gutenberg in any way. It relies on Gutenberg’s compatibility functionality. Because of that, the box with the Gutenberg settings is now in the sidebar, rather than below, and expands to show the various options.
The interfaces with weather APIs like DarkSky and OpenWeatherMap were reorganized to improve the quality of the return data. And all data will be stored going forward in international units. While I am a Fahrenheit and Feet user, most of the world isn’t. So everything will be converted on the fly for display for those of us in the imperial system, making it much less fragile. Flip a setting and it changes.
Simple Location uses the WordPress REST API, and there are new endpoints for frontend use. The geocoding endpoint now has an option to return the weather as part of the lookup instead of requiring a second request. New abilities to lookup by airport code are also built in, mostly for the current conditions widgets. This will be fully functional in a future version.
For those of you worried about hitting or being charged for API usage on commercial sites, I added a simple weather provider courtesy of the U.S. National Weather Service. This will only work with locations inside the United States. It finds the nearest NWS Weather Station to you and uses the current conditions from that location.
There is a new Weather Station widget, split from the other Weather Widget, which allows you to display from a specific station.
There are a lot of good features here, but there will be more in future. So try it out.
https://david.shanske.com/wp-content/uploads/2018/12/Indieweb12.mp3


In the latest episode of An Indieweb Podcast, Chris Aldrich joined me for a late night(for me at least) discussion of Gutenberg, the new WordPress editor, and the usual project talk. I felt I was a bit off due the lateness of the hour, but I still enjoyed the conversation.

Parkeology Challenge November 2018

On Wednesday, November 28th, I participated in the Parkeology Challenge. It is a marathon of sorts where you try to ride every ride at Walt Disney World in a single day. That is 4 different parks, and 49 rides…although only 46 were in the challenge this week due long-term closures. You can only use things available to the average guest.
In order for the people who run Parkeology to certify the results, you have to provide a Twitter record of same. That was handled by one of my four teammates, but I kept a recording on my site of all of the locations I was in. This would be my timeline for the day. The pictures are backed up from the original challenge.
To see the individual posts, you can click here.

It was a day I can honestly say I will not soon forget.

Challengers Meetup at end of Night

Parkeology Challenge 2018 in Brief


To all the awesome teams that ran the @Parkeology today we offer a huge congratulations! It was freezing, rides broke down, hours were lost and you still crushed it! Thanks, we look forward to seeing you again soon!” via Twitter.
A few facts

  •  The Park Operating Hours for the Day Determines Difficulty. Less than 18 hours is considered Expert.
  • The last completion of the challenge was August 18th, though there have been many attempts since.
  • Over 39,000 steps
  • Over 17 miles of walking
  • The numbers above are based on my phone. My watch actually has a higher number.
  • There were 10 teams competing that day. Only one other team had 4 people on it.
  • The range of completed rides were 11-42. The other 4 person team got 42.
  • 6 Teams Completed the 3 Parks We Did. It seems like a lot of people were looking to complete on that day, which is a rarity.