WordPress 4.8 will be released soon, and when that happens, local events will show up in the dashboard! For more background, check out this post. This is really exciting! It’s going to be eve…
Month: April 2019
👓 WordPress Events in the Dashboard | Make WordPress Communities
Since WordPress 4.8, there has been Dashboard widget showing upcoming local events. The widget shows upcoming WordCamps and meetup events inside wp-admin, making it easier for people to find out wh…
👓 What to Expect | WordCamp Central
If you’re thinking of attending a WordCamp, you may be wondering what to expect. Though each WordCamp will be different (based on the organizers, speakers and attendees of each event), there are some general guidelines that all WordCamps follow, as well as some things you can expect at your WordCamp no matter where it is.
👓 Call for Speakers | WordCamp for Publishers 2019
WordCamp for Publishers: Columbus is looking for speakers and workshop facilitators who will educate, inspire and inform attendees about topics related to using WordPress for managing publications.…
👓 Call for Speakers — Opening Soon | WordCamp US 2019
We are really excited to announce this year’s call for speakers. Of course, this is an exciting time every year, but this year we are hoping to spice things up a bit! Our call for speakers will be opening on Monday, March 11, 2019. You will have 5 weeks to submit your creative talk ideas as the de...
👓 RSS feed now available for newly announced WordCamps | WordCamp Central
Wish there was a way for you to know as soon as possible when a new WordCamp goes on the schedule? Now you can subscribe to newly announced WordCamps with RSS! If you already use RSS, just copy and…
Followed WordCamps
Upcoming WordCamps
Tue, Apr 30, 2019, 7:00 PM
WordPress Pasadena is back in beautiful Old Town Pasadena at one of the first (and finest) Co-Workin' spaces in town, CrossCampus.
Bring your curiosity, your questions, your swell attitude and lots of potatoes. J/k, just bring your smiling faces. Please read the info below as it pertains to our meetup format and FAQs.
👓 Instagram influencer cries at the prospect of getting a ‘normal’ job after account is deleted | The Independent
The influencer said she is 'nothing without my following'
This would leave Bridgy free from being the potential source for security leaks and put the onus on the end user. You’d naturally need to have the ability to reset/change the user’s hash in the case that they accidentally allowed their custom email address to leak, although generally this isn’t a huge issue as emails which don’t match the user’s account/endpoints would be dropped and not send webmentions in any case. (In some sense it’s roughly equivalent to my being able to visit https://brid.gy/twitter/schnarfed and clicking on the Poll now
or Crawl now
buttons. It’s doable, but doesn’t give a bad actor much. You’d probably want to rate limit incoming emails to prevent against mass spam or DDoS sort of attacks against Bridgy.)
A side benefit of all of this is that those who have kept their old email notifications could relatively easily get much of their past missing back feed as well. Or if they’re missing back feed for some reason, they could easily get it by re-sending the relevant emails instead of some of the current manual methods. Perhaps allowing preformatted emails with those same manual methods could be used to do back feed for Facebook or other providers as well?
We could also put together some forwarding filters for common platforms like gmail to help people set up autoforwarders with appropriate keywords/data to cut down on the amount of false positive or password containing emails being sent to Bridgy.
The one potential privacy issue to consider(?) is that this set up may mean that Bridgy could be sending webmentions for private messages since users get both private and public message notifications whereas the API distinguished these in the past. To remedy this, the comment URL could be tested to see if/how it renders as a test for public/private prior to sending. Separately, since Bridgy doesn’t need to store or show these messages (for long?), private messages could be sent, but potentially with a payload that allows the receiving end to mark them as private (or to be moderated to use WordPress terminology). This would allow the user’s website to receive the notifications and give them the decision to show or not show them, though this may be a potential moral gray area as they could choose to show responses that the originator meant to be private communication. The API would have prevented this in the past, but this email method could potentially route around that.
Followed Think Like a Hacker | WordFence
Join Mark Maunder for the Think Like a Hacker podcast as he and Kathy Zant cover interesting topics related to WordPress, security and innovation.
I’ve already begun digging into some follow up and what comes next. One of my favorite ideas is doing a future WordCamp for Kids in the Los Angeles area. I’ve also begun thinking of some future volunteering-related projects at larger scale, but more on that later.
Thanks again to all the volunteers, sponsors, and attendees who helped to make it such a great camp!
I’m pretty sure I caught the right people in person, but I’ll say it again that this was one of my favorite camp themes of all time.
📺 Content Calendars and Synergy – Planning Ahead is the Only Way to Cultivate a Cohesive Brand | WordCamp Orange County 2019
In my session I will be exploring several ways to create a cohesive branding strategy, by delving into posting schedules, content strategies, relevant social media (what you actually need), and more. By the end we will all have (hopefully) learned something about what the current web users consider important, and what actually attracts your targeted audience.
📺 Bringing WordPress Core to PHP 5.6 and Beyond | WordCamp Orange County 2019
Every version of PHP from 7.0 and below has been designated end of life (EOL). Currently, WordPress’ minimum PHP requirement is 5.2.7 which was EOL’d over 8 years ago.
In the 2018 State of the Word Matt said we would be moving to PHP 5.6 as a minimum requirement in April, 2019 and increasing the minimum to PHP 7.0 by the end of 2019.
This presentation will attempt to describe the safeguards put in place to avoid breaking the internet.
Thanks Andy, sorry I couldn’t be there to support you in person.
I’ll note that while not traditional slides that Andy has posted the bulk of his talk with images and text here: Bringing WordPress Core to PHP 5.6 and Beyond
Followed Andy Fragen
Trauma surgeon, WordPress developer, and all-around good guy