Archives for: October 2011

How to make any webpage your Mail signature

29/10/11 | by admin [mail] | Categories: Mac OS X

This works for Apple Mail in 10.5 and 10.6 at least, not tested on other versions. You might have issues with Lion, because the Library folder is now hidden by default.

Mail stores its signatures as Safari webarchive bundles. This means that you can save any Safari readable page (including all the images, links, text, CSS, etc) as a webarchive and use it as a signature in Mail. This is very handy, as it means you don't need to use the somewhat limited built in signature editor to create your signatures. It also means that for a large deployment of signatures, you can create webpage that takes variable input and use that to create standard signatures across all users. As simple as a basic form asking for Name, Job Title, Phone or whatever, that then gets output in a pretty webpage that can be saved as a webarchive.

Now, how to do this more or less easily.

Step 1. Open Mail
Step 2. Go to the Mail menu, and select Preferences
Step 3. Click the Signature tab
Step 4. Click the Plus button at the bottom left of the window to create a new signature (this is just a place holder file which we will replace with the webarchive). It will show up under "All Signatures" and you can optionally rename it from "Signature #1" (or whatever) to 'anything you like'.
S
Step 5. Assign the new signature to an email account or accounts by dragging and dropping it from the "All Signatures" list to an account or accounts in the pane on the left.
Step 6. Optionally set it as the default signature for an account, by clicking on the account in the pane on the left, then using the "Choose Signature" selector to set it as the default signature.
Step 7. Close the Preferences window.
Step 8. Quit Mail

Step 9. Open Safari
Step 10. Browse to the webpage you wish to use as your signature
Step 11. Go to the File menu in Safari and select Save As
Step 12. Now this is the slightly tricky bit, we need to find the placeholder signature file we created in Step 4, and save over the top of it. So, navigate to ~/Library/Mail/Signatures, sort by date and select the newest file signature (NOT THE PLIST FILE, that will screw up your signature settings), make sure the format is set as webarchive and click save.
a. Click the arrow next to the filename until it is pointing down.
b. Click your home folder from the list in the pane at the left
c. In the middle pane, double click Library
d. double click Mail
e. double click Signatures
f. click the list view (the button with the horizontal lines, middle of the set of three buttons to the right of where it says "Signatures")
g. click the "Date Modified" column to sort by date
h. click the file with the gibberish name (a set of random letters and numbers which is the GUID for the signature) with the most recent date. DO NOT CLICK THE SignaturesByAccount.plist file.
i. Make sure the format is set as "Web Archive"
j. Click save
Step 13. Reopen Mail
Step 14. Create a new Mail message and check that the webpage you have just saved as a signature shows up correctly.

Bonus extra information. When you create a new signature in Mail, it is assigned a GUID as the filename (well, GUID.webarchive to be precise), and this GUID is used as the reference in the SignaturesByAccount.plist. It is possible to modify the plist directly to point at any file, to use that as a signature. This can be useful for automating mass deployments, you just need to write the scripts. However, this method of just saving over the top of an existing signature works well for a one off.

SSH Port forwarding

16/10/11 | by admin [mail] | Categories: Networking

There is this article that attempts to explain the basics of SSH port forwarding. I find it a little hard to follow, I think because it lacks concrete examples. So, I'm putting a few here

There's two main flavours: forwarding and remote forwarding.

You can use forwarding to forwarding incoming requests to a local port (a port on your computer) to a port on a remote computer. So, you can do something like:

ssh user@remoteserver.example.org -T -L 5900:localhost:15900

This will allow you to connect to a local port (15900) to access port 5900 on the remote machine. This port is for VNC, so what it means is if you have SSH access to a remote machine, and perhaps only SSH access, you can connect to localhost:15900 to access the VNC service on that computer. Very useful when dealing with firewalled or natted remote computers.

Now, remote forwarding does the opposite. Imagine that you have console access on a remote box, and it is sitting behind a NAT or firewall. It can SSH out to another computer, but you can't SSH in. Not an uncommon situation for a typical client box. What this computer can do however is a remote forward, so that requests to port 15900 on the server are sent to port 5900 on the local box.

ssh user@myserver.example.org -T -R 15900:localhost:5900

You could package that up as a script, send it to a friend to run so that they connect to your server, and then access port 15900 on your server to in fact VNC into their computer. Very handy for providing remote support.

You can add these together, so that a server out there on the internet which both you and your friend have SSH access to can act as relay.

Alternatively, by specifying a public IP, or hostname, which works in all cases (locally and remotely) before the first port, and adding the -g flag, you should be able to access that port from outside. To use the -g flag, GatewayPorts Yes needs to be in your sshd_config
Eg

ssh user@myserver.example.org -T -R myserver.example.org:15900:localhost:5900 -g

The only other thing you might need to remember, is if you are running ssh on a nonstandard port, you will need to add the -p flag with the port at the beginning (before the user@host bit) eg:

ssh -p10022 user@myserver.example.org -T -R 15900:localhost:5900

And an example with a web service, where on a NATed box, we tunnel port 80 to a remote server.

ssh user@myserver.example.org -T -R myserver.example.org:80:localhost:80 -g

Of course, to do that you won't want to be running anything on port 80 on myserver.example.org. It's a cool way to quickly swap over to a test website from the internet. Killing Apache on myserver.example.org and then starting up your port forward, but probably of limited use.

Open Source everything: the new, new journalism.

16/10/11 | by admin [mail] | Categories: Conceptual, Philosophical

Several years ago, New Scientist published an article on CopyLeft and released it under a CopyLeft license.

In the ensuing discussion, I made a contribution where I suggest that a great many things could be released as 'Open Source' if we thought about how things were made, and what they were made from, you could open source a great many things to varying levels.

A film often discards a great many takes, even entire scenes and sequences. A film is also made from scripts, which under go several revisions. An actor makes choices about how to say a line. Producers about the team that makes the film. Casting decisions. A great many decisions.

Some of those decisions are easily unmade, in a sense, others are harder to unmake. An open source film could just present the constituent takes/scenes i.e. that which 'ends up on the cutting room floor', the decisions made when editing a film. Given that we have digital technology, these various scenes can be accessed from a Randomly Accessible device (non linear), and strung together in various ways, changing order or dropping certain scenes, adding others, choosing one taken over another.

Indeed that was something achievable fairly easily using 10 year old technology - a DVD player and a computer to chose and buffer scenes for smoother playback.

As far as I know, it hasn't been done.

A music single is much the same. Most music produced in the last 50 years has used a level of multi-tracking, and multiple takes. Sound engineering, mixing and production added over the top. Choices are made, source is included or excluded. Lyrics are varied, verses added and omitted, tracks included/excluded, faded in/out, loud or soft. Certain forms of music go further still, and play with individual samples and sounds, tweaking and reordering. These days a drum track is often composed of samples, stuck together, looped, manipulated, time corrected. Choices are made, source is included or excluded. Present the whole, and you have a remixers wet dream.

This has been done. And has invariably given interesting results.

What then of the piece that inspired it all? The magazine article itself. Again, choices are made, writers revise copy, editors edit. Things are stretched and shortened for commercial, even aesthetic reasons. Articles themselves are based on research. Indeed, it could be argued that the journalist's job is to take the raw research, and present it in nice magazine or newspaper sized chunks.

But why? One reason is technology. It is impractical, even impossible, to present all the raw research in a magazine. The raw research might represent several issues worth of words. Or it might include spoken interviews with people, which might be transcribed but certain nuances of speech are illy described with written words. And the large volume of disparate pieces from which a magazine article is born are not easily presented in a printed, paper, form.

This is stuff that the web excels at. The typical volume of data for one article is near trivial in web terms, where websites might run to several orders of magnitude greater than the proverbial Encyclopaedia Britannica (which was once the unit of measurement for such large amounts of data). Multimedia is not a problem, you can include text or audio or video or still photos or interactive diagrams or games… you see my point. And HyperText allows this to be presented in a way that the 'old media' really can't do. A reader can make decisions of their own about which way to follow the data.

In this world, journalism is about collating information and making it accessible. The truth is the readers to discover.

It turns the philosophy of the "New Journalism" on its head. Where the journalist was integral to the arbitration of truth, and subjectivity was so strong that it lead the new journalism movement to embrace it fully, this new new journalism allows the reader to be presented with largely the same wide gamut of raw research that the original journalist had, but could not publish.

Yes, decisions are still made, and some are hard to unmake like which questions to ask in an interview and the order to ask them, and indeed who to interview in the first place, realising that the choices once made will affect what follows.

Interactivity can go some way to presenting this all in a new way. Text can be revised, new data added, interviewees might make further direct contributions to 'the article' once it is published. And of course, the article is never published in that original sense, printed and fixed as a record forevermore.

And, if the article is released as copyleft, then it becomes part of a greater whole. Others can link to it, refer to it, take it apart and put it back together in a different way. Emphasise different part. The subjectivity is diminished further, as the article is no longer the sole work or responsibility of the original author/s.

In this paradigm, the work of Wikileaks (outside of political considerations) makes more sense. They are releasing the raw source. It is up to the audience to find the truth. Wikileaks is not sitting there as the arbitrator, picking and choosing, weaving a narrative to connect it all for us, presenting it in an easy to digest 500 word editorial. They've left that work to others. The web, due to its linked nature, allows this.

All My Bloggings

All Blog entries in one convenient location.

Are we getting close?

October 2011
Mon Tue Wed Thu Fri Sat Sun
 << < Current> >>
          1 2
3 4 5 6 7 8 9
10 11 12 13 14 15 16
17 18 19 20 21 22 23
24 25 26 27 28 29 30
31            

Linkblog

Amiga Links

XML Feeds

What is RSS?

powered by b2evolution free blog software