Sunday, April 27, 2014

Code Your World

When I started writing in 1993, and had not decided whether I wanted to write science fiction or Romance, I heard of a program called Kepler. As I recall, one was supposed to be able to design alien worlds and check them out.

I never found it.

However, this week I found codecademy. One of the starter lesson sets allows the rookie coder to try world-building.

Look for it here: http://www.codecademy.com/learn

For one reason or another (unless you are already tech savvy) you might be glad you gave it a try. I am.

My apologies for an ultra short blog. I'm preparing for a discussion of the DMCA for the USPTO, with especial emphasis on the benefits of standardizing Take Down notices.

Best wishes,
Rowena Cherry

2 comments:

RowenaBCherry said...

AOL and Blogger do not appear to be playing nicely together.

AOL refused to deliver to me a copy of my own blog! Has this happened to anyone else? I received Margaret's excellent blog on Thursday when the new AOL policy was in place.

Here's what AOL wrote to me:

"AOL Mail updates DMARC policy to 'reject'
Posted Apr 22nd 2014 3:54PM by Vishwanath Subramanian
Today we moved to change our DMARC policy to p=reject. This helps to protect AOL Mail users' addresses from unauthorized use.

It also stops delivery on what previously would have been considered authorized mail sent on behalf of AOL Mail users via non-AOL servers. If you're a bulk sender on behalf of AOL addresses, that probably includes mail sent from you.

This can include but is not limited to:
Email service providers (ESP) sending mail on behalf of businesses using AOL addresses
Websites with "Share with a friend" functionality, sending mail using AOL addresses
Small businesses using other 3rd party services to send mail and communication between their employees and / or customers
Services used to forward mail
Mailing lists (listservs)
Mail sent on behalf of AOL Mail users to DMARC-compliant domains will be rejected by those domains unless the mail passes SPF and/or DKIM authentication checks AND the domain(s) used in those checks match aol.com.

We recognize that some legitimate senders will be challenged by this change and forced to update how they send mail and we sincerely regret the inconvenience to you.

What should you do?

In almost all cases, we recommend that you switch to sending mail from your own domain. You may also consider using AOL SMTP directly.

For mailing lists, also known as listservs, we recommend configuring reply behavior to fill the From line with the mailing list's address rather than the sender's and put the actual user / sender address into the Reply-To: line. Please also note that current "auto unsubscribe" logic based upon bounces might be too rigid until this change has been in place for a while.

For website operators with 'share from email' functionality, please consider using an email address from your own domain as the From address and populate the Reply-To: line with the address of the person sharing.

If you have specific questions around configuration and authentication options as well as DMARC related inquiries, please contact us at dmarc-help@teamaol.com.

Learn more about DMARC here. Thanks for working with us as we make email a safer and better experience for everyone."

Clear as mud!

Margaret Carter said...

I have no idea what this message from AOL is trying to say! However, two blog comments from you did arrive in my AOL e-mail a few minutes ago.