A Stack Overflow Sidebar Gadget

Update: The gadget (which now also supports both Serverfault.com and SuperUser.com), with source code, is now available on CodePlex.com.

I have been following the progress of the Stack Overflow web site since it has started. In fact, I did also participate in the beta testing of the site. In podcast episode #54 , Jeff announced that they are adding the functionality to put a flair on your home page or blog. That’s a really nice idea.

One thing that would be even more cool is to have your flair as a Windows Vista / Windows 7 Sidebar Gadget. So I decided develop one. Why not? On the screenshot below you can see how it looks like. Please consider this first release as a beta release. If you find something odd, please email me.image

Download from here.Disclaimer:
It works on My Machine.

Works-on-my-machine-starburst

image

image

image

When you have installed it, it says that you must enter your user id.

imageimage

So, hover over to the right of the gadget, and click the Options icon.  Now, in order for it to work, you must provide it with your Stack Overflow user id. You can find it in the URL of your user profile page.

image

Enter your user id in the User Id textbox and click ok.

image

Now, it should display your Stack Overflow flair ! Now go over to Stack Overflow and ask or answer some questions.

If you like this gadget, please consider a donation to keep it updated.

Donate

A list of recommended MOSS Service Accounts

Account Type
Purpose
Account Name
MOSS Farm Account

Server Farm Account. This account needs some SQL permissions granting: dbcreator and security admin (do not grant this account SA!). If using ADACM this is the account used for creating objects in the OU specified – so you’ll need to delegate permissions on the OU to this user.

svcMOSSFarm1
MOSS App PoolIdentity for the any MOSS Web App Application Pool(s). A separate process identity should be used for each content Web App (this allows for greater security and auditing). Using the site name in the naming is not advisable as although this may make troubleshooting and auditing easier it reduces security by showing the relationship between App Pools and Web Apps.

svcMOSSAppPool1
svcMOSSAppPool2
svcMOSSAppPool3

SSP Service AccountSSP service accountsvcMOSSSSP1
SSP App PoolIdentity for the SSP Web App Application PoolsvcMOSSSSPAppPool1
MOSS SearchAccount under which the Office SharePoint Server Search runs under.svcMOSSSearch1
MOSS Content AccessAccount used to access content sources to be crawled and indexed. Need to grant this account permission to any NON-MOSS content sources (e.g. NTFS file share, Exchange public folder, websites etc…)Separate accounts may be configured for access to specific content sources using crawl rules.svcMOSSCrawl1
User profile & Properties Access AccountAccount used to access Active Directory for the Profile importsvcMOSSDSA1
WSS SearchAccount which the Windows SharePoint Services Search service runs under. Due to the fact the Office SharePoint Server Search service is running this will only index the WSS Help files.svcMOSSWSSSearch1
WSS Content AccessAccount used by WSS search service to crawl content.svcMOSSWSSCrawl1
MOSS Install AccountAccount used to install MOSS and perform all the required configuration changes.As this account will be used to install and configure the SharePoint servers it must be granted local admin on all farms members and have permissions to the SQL instance.This account can be disabled after installation and configuration is complete (it is not advised to delete it).svcMOSSInstall1
SQL ServicesUsed to run MS SQL Services

svcSQLSVC1
svcSQLRS1
svcSQLAS1

 

This list is copied from Matt Grove, thanks Matt.

To make the creation of these accounts easy, I have created a VBS script that does the job.

 

Then, follow a guide to install a complete MOSS setup.