Navarr's Tech Side » General

Xoom and ICS

Navarr — Tue, 07 Feb 2012 02:21:26 +0000

So, today I managed to snag myself a Xoom. By which h of course I mean that I received a Xoom in the mail from my good friend Amazon.com. I have been playing with it since I opened hue packaging and so far I have to say that I absolutely love it. Touch typing on a screen is definitely awkward but I have a feeling that I'll get more used to it as time goes on.

This is my first tablet, and hopeful I'll be able to writ some neat maps for it. I've already had a great idea that nobody seems to be implementing in the android store atm.

So maybe I will at a future date?

Feeling like I’m PWNing REST

Navarr — Sun, 05 Feb 2012 05:10:26 +0000

I'm working hard to make the private API I'm implementing at my current job a RESTful uri scheme, and I feel like I hit a point of transcendence recently when I decided how to record a user staring a story.

PUT /article/:articleID/favorite/:userID
DELETE /article/:articleID/favorite/:userID

I decided that POST didn't make sense, as you couldn't really favorite a story more than once at a time, and of course DELETE makes sense here. Adding them as a relation between the article and the user seems to make sense in this URI scheme as well.

So, all in all, I'm proud of myself. Despite it being such a tiny, simplistic thing.

Great Scott, I’ve discovered something delicious

Navarr — Sun, 02 Oct 2011 00:52:57 +0000

Truthfully, I've tried my best to make a difference in programming, in code, trying to learn, trying to be amazing. I never thought I'd just randomly happen upon a chance discovery that would turn out to be amazingly delicious.

Late August, I went to my friend's house in Toledo. There, we picked some pears. I took home some for myself and placed them in my fridge, unfortunately never stopping to think to eat them.

Late September, I place a Sunkist can I had not had time to finish beside the pears, leaving it for later.

October 1st, I pull the pears out of the fridge, giving them up to inspection by Rebecca. They look as if they haven't aged, possibly frozen by sitting beside the freezer inside the fridge. I pull out the sunkist and set it on top of the fridge to deal with later. Rebecca declares that the pears, although not yet rotten, would be as soon as they thawed as their cellular structure would not be able to survive being frozen and thawed.

Later that evening, I accidentally take a swig of the sunkist left on top of the fridge. It has a delicious taste of pear to it, despite its flatness it does not taste bad. It is delicious, but sickly sweet. But amazingly delicious.

Now that I've learned this, what should I do about it?

The Web Needs a Federated Payment Protocol

Navarr — Tue, 30 Aug 2011 01:30:11 +0000

When it comes to paying for good and services on the Internet, the consumer has many choices - Paypal, Amazon, Google Checkout, their respective Credit Card...

However, you rarely see all of these accepted in a single place - and for very good reason: Its gorram difficult to implement so many different APIs and systems, and have to deal with tracking each of them.

Clearly, the Web needs a way to deal with this - and having a Federated Payment Protocol would solve it.

Think about it: A vendor website would easily communicate with a payment processor through this protocol. They wouldn't have to know who the Payment Processor is, or even care for that matter. The vendor would issue a request to the payment processor. The processor would be in charge of authenticating the user, and would send back their "terms" (out of the requested amount, *this* much will be dispersed and *this* much will be taken as a processing fee). The vendor will agree, disagree, or change the payment amount based on what the processor sent. The processor would then submit this change to the user, if the user accepted the processor would send the new details and the vendor would accept or deny. The processor would send the money through whatever system they need to, notifying the vendor how long it should take, and if its a short enough time the vendor can hold the user until the payment has cleared (or if it is a trusted source not hold at all) and provide the promised goods or services, after confirming the transaction with their receiving service.

This solves a few key issues:

Vendors have to trust that they are receiving the money for their services.
Credit Card details would never have to be provided to the vendor, as the service would be directly through their credit company's payment service.
Vendors would not have to implement different APIs for different payment methods.
"Credit Card Fraud" liability would be the burden of the Credit Company, of whom authenticated the user. A vendor would no longer be required to make sure a person is who they say they are.
Banks could offer their own payment services ("Debit." Possibly with No Fee, resulting in a reduction of prices from vendors, hopefully).

Clearly this is a good idea, and I wish I had the know-how to put it together myself.

Programs I Want to See Made Into (Browser) Web Applications

Navarr — Sat, 25 Jun 2011 18:36:35 +0000

MyAnimeList Updater
Windows Live Writer
PuTTY
git – though Cloud9 IDE works pretty damn well.
WinSCP or something similar

Closing Desktop Notifications on a Timer

Navarr — Tue, 11 May 2010 22:42:17 +0000

So, one of the few things about Chrome’s desktop notifications I’ve been trying to figure out is how to close them on a timer, and it finally came to me.

This timer will only activate when the notification is opened, and will close the notification even if the page that originally spawned it has been closed.

Create and Show a new HTMLNotification.

Code block    

<html>
	<head>
		<title>Notification Title</title>
		<style type="text/css">
			body,body* { font-family: sans-serif; font-size: 10pt; }
			h1 { font-family: sans-serif; margin: 0; padding: 0; font-size: 12pt; font-weight: bold; }
			p { margin: 0; padding: 0; }
		</style>
	</head>
	<body onload="setTimeout(self.close,5000)">
		<h1>Notification Title</h1>
		<p>Notification Text</p>
	</body>
</html>

That will close the window after five seconds and will look just like a normal notification!

What I learned is: Notification Windows respond to the javascript method self.close()

Open Letter to Dave Winer

Navarr — Sun, 02 May 2010 22:00:17 +0000

I know you invented RSS and all that, but please, please stop raping your feed.

I do not like getting this every couple of weeks, or days.. I don’t know, I have no concept of time, but this isn’t the first time its happened.

Please?

Why SuperTweets won’t kill URL Shorteners

Navarr — Wed, 14 Apr 2010 19:38:37 +0000

Now, the title of this blog post makes it sound like I’m going to write an essay about why SuperTweets (and the probability of them having a URL metadata for tweets) will not be killing URL Shorteners like j.mp and bit.ly anytime soon.

1) URL Shorteners Keep You Safe

One of the things URL shorteners do now is they keep you safe from malicious websites. You can preview the site you are visiting, and if its determined to be delicious the short URL will either be deleted or blocked or a warning will be shown, letting you know it is no longer safe to visit that URL.

2) URL Shorteners are Branded

All I really have to say here is “Bit.ly Pro” URL Shorteners now have custom branding, so it makes it even easier to send people to your website or promote your brand on twitter by including the link in the text.

3) URL Shorteners are Easy to Remember

When they are used correctly. Services like bit.ly allow you to give a custom name to your short link. This is especially useful in media such as Television or Print: http://j.mp/cnn-transgender is much easier to remember and type than www.cnn.com/2010/LIVING/04/14/transgender.irpt/index.html?hpt=C1

With even just these three simple reasons in mind, it is very clear to me that URL shorteners will not be dying anytime soon, no matter how much metadata you can attach to tweets. I’m not even sure they’re bad for the internet, anymore.

The Very Best Thing about Unixkcd

Navarr — Thu, 01 Apr 2010 10:39:42 +0000

guest@xkcd:/$ make me a sandwich

What? Make it yourself.

guest@xkcd:/$ sudo make me a sandwich

Okay.

Geosense – I’m in Love

Navarr — Mon, 01 Mar 2010 10:13:03 +0000

I love applications that fill in where hardware fails, but this one is really taking the cake! Geosense for Windows gives you the capabilities of a GPS sensor in your computer (but without the actual hardware!) It uses Google Location Services to triangulate your location and provide your coordinates to applications that request them.

Unfortunately, not many applications use this type of data (yet) but Long Zheng and Rafael Rivera are hoping that with this new default driver for PCs without GPS, that many more developers will embrace the creation of geo-location in desktop applications.

Continue Reading for Code Snippets

To that effect, I’ve included some Code Snippets that were originally posted on The League of Paul:

Use with the Sensor and Location .NET Interop Sample Library:

Code block    
using Windows7.Location;
 
public class Location
{
    public String City { get; set; }
    public String Country { get; set; }
    public double Latitude { get; set; }
    public double Longitude { get; set; }
}
 
public static class GlobalPosition
{
    private static LatLongLocationProvider _provider;
    private static CivicAddressLocationProvider _civicprovider;
    private static bool _loadproviderthrowsexception = false;
    private const uint DEFAULT_REPORT_INTERVAL = 0;
 
    public static Location GetLocation()
    {
        Location l = new Location();
 
        try
        {
            if (_loadproviderthrowsexception)
            {
                return null;
            }
 
            if (_provider == null)
            {
                _provider = new LatLongLocationProvider(DEFAULT_REPORT_INTERVAL);
                _civicprovider = new CivicAddressLocationProvider(DEFAULT_REPORT_INTERVAL);
            }
            var y = _civicprovider.GetReport() as CivicAddressLocationReport;
 
            l.City = y.City;
            l.Country = y.CountryOrRegion;
 
            var x = _provider.GetReport() as LatLongLocationReport;
            l.Latitude = x.Latitude;
            l.Longitude = x.Longitude;
            return l;
        }
        catch (Exception ex)
        {
            return null;
        }
 
    }
}

and Powershell:

Code block    
[Reflection.Assembly]::LoadFile("\Windows7.SensorAndLocation.dll")
$provider = new-object Windows7.Location.LatLongLocationProvider(0)
$position = $provider.GetReport()
$position.Latitude
$position.Longitude