Galactic editing

After I posted a photo I took over the weekend, long-suffering reader and all-round top ‘tog Chris J Wormwell (you may remember him from such posts as Chris’ PoA sky & lighthouse p0rn and The photo that I wanted to share yesterday but couldn’t because the dog ate the internet) got in touch with some sage advice:

This was a huge help and step forward for me recently: https://www.lonelyspeck.com/how-to-process-milky-way-astrophotography-in-adobe-lightroom/

I clicked through, and was rewarded with a step-by-step guide to making this photo:

look better:

And it only took me ten minutes or so.

Some points from my experience:
I think the photo looks much better.
Note that all that stuff was there in the original – you just couldn’t see it.
If I can do it, so can you.
The guide was really helpful.
I now know that I will need to take a better photo next time if I want to make it even better.
But also, I now know how to do that.
There are loads of other ideas for night photography on that site that I haven’t had chance to look at yet.

A(nother) new door has been opened. Thanks, Chris.

Google Docs as Word Processor Alert

If you use Google Docs as your Word Processor, you need to be aware of this!” proclaimed the clickbait, and I do, so thought I’d better give in and click through. Here’s what it said:

Gosh.

It turns out that Google locked “a ton of users” (eish) out of their documents due to “inappropriate content”. The issue with this seems to be twofold. Firstly, that there was no “inappropriate content” within the documents in question. And yes, it turns out that this was an error on Google’s part: something they acknowledged and apologised for, stating:

This morning, we made a code push that incorrectly flagged a small percentage of Google docs as abusive, which caused those documents to be automatically blocked. A fix is in place and all users should have access to their docs.

And then secondly:

…the incident raises important questions about the control Google Docs users have over their own content. The potential to lose access to an important document because it hasn’t yet been polished to remove certain references or sensitive material has concrete implications for the way Google Docs is used.

Well yes, I suppose so. In the same way that using MS Windows apparently opens me up to all sorts of hacking and viruses, and in the same way that using online banking apparently puts me at risk of phishing and the like.

So yes, it might happen, but in all reality, it really probably won’t. And, when you think about it, it really actually hasn’t. This was an error which was corrected and which shouldn’t happen again.

“Google’s abuse policy prohibits the posting of serious threats, needlessly graphic or violent content, hate speech, harassment, confidential information, pornography, and anything illegal including child exploitation and copyrighted content.”

So if you’re writing that sort of thing, maybe you need to look elsewhere for your word processing requirements, and maybe also for your kicks.

I don’t pay for Google Docs, but of course some people do. I’d guess that we all agreed to these policies when we signed up though. (You did read all the Ts&Cs, didn’t you?) And so, as usual, it comes back to that simple adage: if you don’t like it, don’t use it.

But for me, much like using Windows and online banking, the convenience and economic benefits far outweigh any potential “censorship”.

WSW

And so, without any more ado, and not ever so much fanfare, here’s one of the photos I took over the weekend. It’s quite dark (hey, it was night time), and so it looks MUCH better on black, but to look at it like that you’ll have to click through to Flickr here.

This was a 30 second exposure looking WSW (240.99º to be exact) from Suiderstrand bay. Next stop heading straight out from here is Necochea, Argentina, 6819.62 km across the South Atlantic.

But I didn’t go there. I wandered the 100m or so back up to the cottage and had a brandy.

Four photos from the weekend: here.

Rollback

I solved my problem yesterday by using the System Restore tool to travel back in time to a point when I didn’t have the catchily-named

Windows Malicious Software Removal Tool for Windows 8, 8.1, 10 and Windows Server 2012, 2012 R2, 2016 x64 Edition – November 2017 (KB890830)

on my laptop.

My laptop didn’t seem to like something about that particular update, but all seems to be running smoothly now. And yes, I realise that I will have to reinstall that update at some point, but at least if things go awry again, I’ll know why it is and I can deal with it a bit more quickly than I did this time around.

All of that meant that I could finally get some photos uploaded from the weekend, and that means that you will be able to see them shortly.

Watch this space.

Conn ctiv y prob ems

I’m having a few connectivity problems today. They’re preventing me from uploading a few of the photos I took over the weekend, and which were to be the basis for today’s blog post.

It’s a weird thing that’s happening. The (new) laptop tells me that it is happily and securely connected to any given wifi (I’m having the same issue on 4 different networks I have tried, so I’m guessing it’s the laptop that’s somehow at fault here), but then I can’t do stuff on various programs.

Lightroom can’t connect to Flickr. The connection to Gmail keeps dropping on Chrome (it’s ok for 30 seconds or so, then dies), but Facebook is fine and Twitter seems unaffected too. Uploading anything to anywhere sometimes works, sometimes doesn’t. But mostly doesn’t.
A quick ping of the ISP was faultless. I’ve lowered Firewalls and run troubleshooters.

Nothing so far has worked. I’m now in the process of resetting all my network adaptors. All of them.

If you see a photo on Flickr or on here later, something might have worked.
If not, you’ll just have to follow me on Instagram.