<![CDATA[The Swearing Developer]]>http://www.swearingdeveloper.com:80/http://www.swearingdeveloper.com:80/favicon.pngThe Swearing Developerhttp://www.swearingdeveloper.com:80/Ghost 1.22Sun, 26 Aug 2018 23:37:54 GMT60<![CDATA[8 Use Cases for Itty Bitty Site we want to see now]]>http://www.swearingdeveloper.com:80/8-use-cases-for-itty-bitty-site-we-want-to-see/5b4b9214a6f57a64c97cc778Sun, 22 Jul 2018 00:27:57 GMT8 Use Cases for Itty Bitty Site we want to see now

Don't know what Itty Bitty Site is for? Neither do I but lets shoot a few ideas up the flagpole and see what happens.

1. Itty Bitty Social Network

Right now every post on social media just looks like an SMS - text and emoji . Instead of that blah you could have each post be an Itty Bitty site. Then you'd have a whole microsite of JS/CSS/HTML to play with. Can you imagine what those Kardashians would do with that?

2. Micro-blogging platform

The idea here is that you could create a blog where each post on the blog is actually an Itty Bitty site. The platform itself could just be a whole load of RSS feeds. Each blogger would have an RSS feed that hosts the URLs that are their blog posts.

Lets make RSS great again!

What's missing here is a tool to spit the posts out. Some kind of CMS-style app for generating each post, configuring the layout and preview. To publish a post the tool would just update the RSS feed.

3. Lets make Yet Another JavaScript View framework

This one would be a new approach to organising a Single Page Application. Here you can make sections or components of the site to be an Itty Bitty SIte. The main application just loads up the main page which has Itty BItty site URLS for the components on the page. Some sort of dispatcher process would call the Itty BItty URLs and render the results in place on the page.

What's cool about this one is that each section of your site is completely independent of the others and you can mix up your front end technologies as you see fit.

4. Executable code as content

Anywhere that you can send text can now be used to send an Itty BItty Site. The recipient can then load the site in a browser or webview component and have an executable app. This could be built into whatever site or app that you are using for messaging. Take the official calculator example. You can transmit that in a tweet and the receipient can execute that in their browser.

5. A design revolution

Forget Mobile First, the new challenge is Itty Bitty First. Especially if some of these other ideas take off y'all need to start shaping up your microsite design skills.

6. Dirt cheap static web hosting

If you want to host a static web page such as a marketing landing page then your hosting costs will disappear if you use an Itty Bitty Site. Your site is just a record in DNS. No need to pay for a CDN or hosting. No servers to patch.

What would be needed here would be a site where marketing drones could create IBS landing pages and easily pop them into DNS. You could charge a fee for them to use this platform. Customers could have their main site alongside this and for landing pages they need they can just create them as IBS sites.

7. New eBook format

Who wants shitty DRM-laden commercial ebook file formats when we can just use open technologies? Each page in the book is an Itty Bitty site with a link to the next page.

8. Less is more

Why bother with a fancy website when you can just take it back to basics with an Itty Bitty microsite?

So there we go, a few ideas for you to work on.

Get cracking nerds!

If you found this interesting then why don't you:

8 Use Cases for Itty Bitty Site we want to see now

]]>
<![CDATA[Go long! AWS EC2 switching to longer resource IDs from July 30th]]>http://www.swearingdeveloper.com:80/aws-ec2-long-resource-id-change/5b2bb5d1a6f57a64c97cc75fMon, 25 Jun 2018 23:24:22 GMTGo long! AWS EC2 switching to longer resource IDs from July 30th

As I'm sure you remember Amazon announced way back in December 2017 that they would be switching to longer resource ids for EC2. Therefore you will also remember that they will start the transition 30th July 2018.

No?

Ok, well whether you marked your calendars or not, here's what you need to know to be prepared.

1. Wait for it...

Given Amazon have got a bazillion EC2 instances on the go, the transition is going to take a while. It will start on 30th July and will end 17th August. Not all customers will transition at the same time, not all regions will transition at the same time and not all resource types will - you've guessed it! - transition at The same time.

From the 17th August all new resources will receive the longer format resource id. Any resources with a short resource id will continue to be supported but will just start to feel insecure about it.

2. So when's it actually going to switch up on me?

Log into the AWS Management Console, click through to EC2 and you'll see a "Resource ID length management" link on the right of the screen under Account Attributes

Go long! AWS EC2 switching to longer resource IDs from July 30th

Expand the "Advanced Resource ID Management" section to view transition dates for all your resources. Remember, not all regions will transition at the same time so you will also need to flip through each of your EC2 regions and check this page on them to find out when all of the resources in your account will transition.

For those of you who can grok JSON and who don't like clicking on things you can use the AWS CLI describe-id-format option instead:

aws ec2 describe-id-format

Get the deets on that here

3. Fix your regexes

So if by reading this you've just realised you've got a regex to fix somewhere then it will need to cope with the following:

<resource_type>-0123456789abcdef

That's the resource type, followed by a dash and then 17 hexadecimal characters.

For the full list of affected resource types check the official FAQ.

4. Bonus option: Switch now!

Be the envy of all your friends by switching to the longer resource id format early!

To receive longer IDs today, you can click on Switch to longer IDs in the "Resource ID length management" page in AWS Management Console or use the APIs.

Done. Go forth and go long!

Go long! AWS EC2 switching to longer resource IDs from July 30th
The 29-time PC Mag Award Winner]]>
<![CDATA[Party's over: TLS 1.1 will be discontinued on Maven Central THIS FRIDAY]]>http://www.swearingdeveloper.com:80/partys-over-tls-1-1-will-be-disabled-on-maven-central-this-friday/5b2042aba6f57a64c97cc740Tue, 12 Jun 2018 22:23:17 GMT

I know some of you out there might still be using Java 6 or Java 7.

It's ok, I won't tell anyone.

The thing is the folks over at Maven Central are discontinuing support for TLS 1.1 this Friday. Bummer, I know.

You've got 5 options:

  1. Upgrade. Kinda obvious right?
  2. Configure Java to use TLS v1.2 using -Dhttps.protocols=TLSv1.2. Sneaky!
  3. Use a repository manager that uses a Java version supporting TLS 1.2. A bit more effort...
  4. Revert back to http until you can get your shit together. Not very sexy is it.
  5. Upgrade already!

Official FAQ on the change is here: https://central.sonatype.org/articles/2018/May/04/discontinue-support-for-tlsv11-and-below/

Peace.

If this post saved your ass then why don't you:

Buy Me A Coffee

]]>
<![CDATA[GDPR and The Great Privacy Policy Update of 2018]]>

So we've all seen these goddamned privacy policy bullshit emails recently.

For those of you that live under a rock these are all because of some new European legislation (yawn) called GDPR which stands for God Damned Privacy Rules or some such nonsense. Nobody likes them but they're law..

meme_updated_privacy_policy

So

]]>
http://www.swearingdeveloper.com:80/gdpr/5b1475e2ff8c98088a48ef6fSun, 03 Jun 2018 23:56:25 GMT

So we've all seen these goddamned privacy policy bullshit emails recently.

For those of you that live under a rock these are all because of some new European legislation (yawn) called GDPR which stands for God Damned Privacy Rules or some such nonsense. Nobody likes them but they're law..

meme_updated_privacy_policy

So listen up data nerds here's what you need to know when you're planning on funging around with someone's data:

The rules apply when you collect, store or use personal data

Thanks Captain Obvious!

There's one set of rules for all EU countries

And in the darkness bind them.

Right to know who is processing, what and why

Sure, why not

Right to access your data

So you can reminisce about all of the crap you've vomited onto Facebook over the years.

Right to object

Sadly doesn't work on all those goddamn privacy policy emails though

Right to correct data

Yep. Sharpen your pencils nerds!

Right to have data deleted and forgotten

Bye bye 2am tweets!

Right to have a say when a decision is made about your data by an algorithm

Here's how that will work:

Computer: nope
Human: Glances at spreadsheet It's still a no.

Right to move your data

The official example for this one is, get this, when you change electricity supplier you can pass your electricity usage data to your new supplier. Bet they can't wait to read that!

So there you go. Now you know why you have to make all of these super urgent crappy database queries at work. I've got go now because I've just received another important privacy policy update I need to read /sarcasm/.

Later.

]]>
<![CDATA[Ghost]]>

Well people, it's WORKING!

Welcome to www.swearingdeveloper.com running on Ghost. Let me tell you Ghost was easy to set up. It's really beautiful to look at and the Markdown editor is awesome.

Markdown: because who wants to fuck around with angled brackets?

Anyway the absolute best thing about

]]>
http://www.swearingdeveloper.com:80/ghost-in-the-shell/5b132c68ff8c98088a48ef6cSun, 03 Jun 2018 23:55:02 GMT

Well people, it's WORKING!

Welcome to www.swearingdeveloper.com running on Ghost. Let me tell you Ghost was easy to set up. It's really beautiful to look at and the Markdown editor is awesome.

Markdown: because who wants to fuck around with angled brackets?

Anyway the absolute best thing about it is that by not using Wordpress I'm reducing that bloody statistic where 80% of all Internet sites are running on PHP.

That's it.

]]>