Network Programming in .NET

When was the last time you tried to decode a VIN for an RV, specialty trailer, or electric scooter only to get a frustrating “manufacturer not found” error? If you’ve worked with vehicle data beyond mainstream cars and trucks, you’ve probably hit this wall more times than you’d care to count.

The standard NHTSA VIN decoder works brilliantly for Ford, Toyota, and GM vehicles. But what happens when you’re dealing with a Highland Ridge travel trailer, a Segway electric scooter, or a custom-built utility trailer? You’re often left with nothing but the basic World Manufacturer Identifier and a lot of guesswork.

That’s exactly the problem that led us to create NicheVinDecoder – an open-source .NET library specifically designed to decode VINs from the manufacturers that traditional decoders leave behind.

The Problem: A Tale of Two VIN Decoders

Picture this scenario: You’re building an application for an RV dealership. A customer walks in with a 2023 Highland Ridge Open Range travel trailer, VIN number 58TBM0BU8P3A13051. You run it through a standard VIN decoder and get:

Manufacturer: Highland Ridge RV (maybe)
Model Year: 2023
Everything else: Unknown

But with NicheVinDecoder, that same VIN reveals:

Manufacturer: Highland Ridge RV
Model Year: 2023
Model: Open Range 330BHS Travel Trailer
Body Style: RV Trailer [Standard] Enclosed Living Quarters
Trailer Type: Ball Pull (Travel Trailer)
Axle Configuration: Two Axles (Tandem)
Length: 38 ft - less than 40 ft
Plant Location: 3195 N. SR 5, Shipshewana, IN 46565
Model Code: A1 (330BHS)
Sequential Production Number: 3051

The difference is dramatic. Instead of generic data, you get actionable information that can drive business decisions, inventory management, and customer service.

🔗 Check out NicheVinDecoder on GitHub

Who This Library Is For

NicheVinDecoder isn’t trying to replace existing VIN decoders – it’s designed to complement them. It’s perfect for developers working with:

RV and Trailer Industry

• Dealership management systems
• Insurance applications
• Parts lookup systems
• Rental platforms

Specialty Vehicle Markets

• Electric vehicle fleets
• Industrial equipment tracking
• Custom manufacturer databases
• International vehicle imports

Data Integration Projects

• Vehicle history reports
• Fleet management systems
• Auction platforms
• Compliance tracking

The Technical Architecture

We built NicheVinDecoder with extensibility as the core principle. The library uses a factory pattern that automatically detects which decoder to use based on the World Manufacturer Identifier (WMI):

csharp

// Simple usage
var result = VinDecoder.Decode("58TBM0BU8P3A13051");

if (result.IsValid)
{
    Console.WriteLine($"Manufacturer: {result.Manufacturer}");
    Console.WriteLine($"Model: {result.Model}");
    Console.WriteLine($"Plant: {result.AdditionalProperties["PlantLocation"]}");
}

Each manufacturer decoder inherits from BaseVinDecoder and implements the specific VIN structure for that manufacturer. This means adding support for a new manufacturer is as simple as creating a new class and defining their VIN format.

Current Coverage and Growing

As of today, NicheVinDecoder supports six manufacturers across diverse vehicle types:

ManufacturerVehicle TypesExample ModelsHighland Ridge RVTravel Trailers, Fifth WheelsOpen Range, Mesa Ridge, Go PlayBrinkley RVLuxury Fifth WheelsModel Z, Model GAppalachian TrailersUtility TrailersCar Haulers, Equipment TrailersNine Tech (Segway)Electric ScootersA-Series, B-SeriesXPO ManufacturingCommercial TrailersDry Freight VansLoad Glide TrailersAluminum TrailersFlatbed Trailers

But here’s where it gets exciting – this is just the beginning.

🚀 Contribute to NicheVinDecoder

Real-World Impact

We’re already seeing NicheVinDecoder make a difference in production environments:

RV Dealership Systems: Dealers can now automatically populate inventory details, generate accurate listings, and provide instant vehicle history to customers.

Insurance Applications: Underwriters can access precise vehicle specifications for accurate risk assessment and premium calculation.

Fleet Management: Companies managing specialized vehicle fleets can track detailed asset information for maintenance scheduling and compliance reporting.

The Open Source Advantage

One of the most exciting aspects of NicheVinDecoder is its open-source nature. Every manufacturer decoder is built using publicly available VIN specifications, and we encourage the community to contribute.

Adding a new manufacturer is surprisingly straightforward:

1. Research the VIN Structure: Gather the manufacturer’s VIN specification
2. Create the Decoder Class: Implement the decoding logic
3. Add Unit Tests: Ensure reliability with comprehensive tests
4. Submit a Pull Request: Share your work with the community

We’ve made the contribution process as smooth as possible with detailed documentation, code templates, and examples.

A Community-Driven Future

The beauty of focusing on niche manufacturers is that there’s a passionate community behind each one. RV enthusiasts know Highland Ridge inside and out. Electric vehicle advocates understand every nuance of their chosen brands. Trailer professionals have deep expertise in their specialized equipment.

By tapping into this collective knowledge, NicheVinDecoder can grow to cover hundreds of specialized manufacturers that would never make it into mainstream VIN decoders.

Getting Started

Ready to try NicheVinDecoder in your project? Here’s how to get started:

Installation

bash

# Clone the repository
git clone https://github.com/infiniteloopltd/NicheVinDecoder.git

# Or reference it in your project
# (NuGet package coming soon)

Basic Usage

csharp

using NicheVinDecoder;

var result = VinDecoder.Decode(yourVin);
if (result.IsValid)
{
    // Access rich vehicle data
    var make = result.AdditionalProperties["Make"];
    var plantLocation = result.AdditionalProperties["PlantLocation"];
    // And much more...
}

📖 Full Documentation Available on GitHub

What’s Next?

We have big plans for NicheVinDecoder:

Short Term

• NuGet package for easy installation
• Additional RV manufacturers (Forest River, Thor Industries)
• More electric vehicle brands
• Enhanced error handling and validation

Long Term

• Web API for non-.NET applications
• Machine learning for automatic VIN structure detection
• Integration with popular vehicle databases
• Mobile SDK for field applications

Community Driven

• Whatever manufacturers the community needs most
• International vehicle support
• Specialized industry focus areas

Join the Movement

NicheVinDecoder represents more than just another code library – it’s a movement to ensure that no vehicle gets left behind in our increasingly digital automotive world.

Whether you’re a developer who’s frustrated by VIN decoder limitations, a domain expert with knowledge of a specific manufacturer, or simply someone who believes that open source makes everything better, we’d love to have you join us.

Ways to Get Involved:

🔧 Developers: Contribute decoder classes for manufacturers you know 📚 Domain Experts: Share VIN specifications and vehicle knowledge
🧪 Testers: Help validate decoders with real-world VIN samples 📢 Advocates: Spread the word in your professional networks

⭐ Star NicheVinDecoder on GitHub

Conclusion

Every VIN tells a story. With mainstream vehicles, that story is usually easy to read. But for the millions of specialty vehicles on our roads – the RVs that enable adventure, the trailers that move commerce, the electric scooters that transform urban mobility – those stories have been largely untold.

NicheVinDecoder changes that. By focusing on the forgotten corners of the automotive world and leveraging the power of open source collaboration, we’re building something that couldn’t exist any other way.

The next time you encounter a VIN from a manufacturer you’ve never heard of, don’t just shrug and move on. That vehicle has a story to tell – and with your help, NicheVinDecoder can learn to tell it.

Ready to dive in? Check out the project on GitHub, try it with your own VINs, and let us know what manufacturers you’d like to see supported next.

🎯 Visit NicheVinDecoder on GitHub Today

Have experience with a manufacturer not yet covered by NicheVinDecoder? We’d love to hear from you! Open an issue on GitHub or reach out to discuss adding support for your area of expertise.

As developers, integrating rich user profile data can elevate the experience of our apps, websites, and services. Today, let’s dive into how you can fetch Flickr profile information by email using AvatarAPI, a handy service that consolidates avatar and profile data from multiple platforms — including Flickr.

Why Flickr?

Flickr remains a popular photo-sharing platform with millions of users showcasing their photography. While many apps focus on social media giants like Twitter or LinkedIn, Flickr’s unique focus on imagery and photography makes it valuable for projects centered around visual content or creative communities.

What is AvatarAPI?

AvatarAPI is an API designed to fetch user profile avatars and metadata by providing common identifiers such as emails, usernames, or social media IDs. It supports many sources, including Flickr, making it a one-stop shop for profile enrichment.

How to Fetch Flickr Profile Data via AvatarAPI

When you request Flickr profile info through AvatarAPI, the data is returned in XML format, containing a rich set of fields to help you understand the user behind the email address.

Here’s an example snippet of the raw XML you get from AvatarAPI for a Flickr profile:

xmlCopyEdit<?xml version="1.0" encoding="utf-8" ?>
<rsp stat="ok">
  <person id="12345678@N04" nsid="12345678@N04" ispro="0" is_deleted="0" iconserver="2257" iconfarm="3" path_alias="random_alias" has_stats="0" has_adfree="0" has_free_standard_shipping="0" has_free_educational_resources="0">
    <username>Dr. Random</username>
    <realname>Random Name</realname>
    <location />
    <timezone label="Random City, Random State" offset="+00:00" timezone_id="Europe/London" timezone="57" />
    <description>Random Description</description>
    <photosurl>https://www.flickr.com/photos/random_alias/</photosurl>
    <profileurl>https://www.flickr.com/people/random_alias/</profileurl>
    <mobileurl>https://m.flickr.com/photostream.gne?id=12345678</mobileurl>
    <photos>
      <firstdatetaken>2000-01-01 00:00:00</firstdatetaken>
      <firstdate>946684800</firstdate>
      <count>10</count>
    </photos>
  </person>
</rsp>

Breaking Down the XML

• person attributes:
  • id and nsid: The unique Flickr user ID.
  • ispro: Whether the user has a pro account (1 for yes, 0 for no).
  • is_deleted: Indicates if the account is deleted.
  • iconserver and iconfarm: Used to construct the user’s avatar image URL.
  • path_alias: The user’s Flickr alias, used in URLs.
• Child elements:
  • <username>: The Flickr username.
  • <realname>: The user’s real name, if provided.
  • <location>: Location info, may be empty.
  • <timezone>: Detailed timezone information with label and offset.
  • <description>: User’s personal description or bio.
  • <photosurl>, <profileurl>, <mobileurl>: URLs to various Flickr profile pages.
  • <photos>: Info about user’s photos:
    • <firstdatetaken>: When the user took their first photo.
    • <count>: Number of photos uploaded.

How to Use This Data

With this data, you can:

• Display user avatars and profile links inside your app or website.
• Show contextual user info like location and bio.
• Highlight photography activity through photo counts and dates.
• Personalize user experiences by leveraging timezone and locale info.

Constructing the Avatar URL

Flickr stores user icons using a combination of the iconfarm, iconserver, and nsid. The avatar URL can be built as:

bashCopyEdithttps://farm{iconfarm}.staticflickr.com/{iconserver}/buddyicons/{nsid}.jpg

For example, with iconfarm=3, iconserver=2257, and nsid=12345678@N04:

bashCopyEdithttps://farm3.staticflickr.com/2257/buddyicons/12345678@N04.jpg

Wrapping Up

Thanks to AvatarAPI’s support for Flickr, accessing rich profile data by just knowing a user’s email has never been easier. Whether you’re building a photography community platform, enhancing contact profiles, or adding social proof, the Flickr profile data returned by AvatarAPI can help bring your users’ identities to life.

You can explore the full AvatarAPI docs for Flickr and other providers here: https://docs.avatarapi.com/.

If you want, I can help you write example code snippets in your favorite programming language to get started quickly with AvatarAPI and Flickr!

Happy coding!
— Your Friendly .NET Dev Blog

Scam warning!

TL; DR;
If you get approached by this company for investment. It’s a scam. Evidence below
https://drive.google.com/drive/folders/1s8PmzNv9YZQI_C50Tx118cqO9REkJgvu?usp=sharing

I got approached by this company, which in the exchange of 2 emails offered a $1M investment. To good to be true. With zero-due diligence. I’ve been trhough similar processes before, and expect a month’s worth of due dilligence document preparation before getting to the point of an offer.

Anyway, so I did due dilligence on them, and specifically, their director:
NRIC/FIN/Passport No. : S8838988C
Name : CHENG YONG TECK
Nationality/Citizenship : SINGAPORE CITIZEN
Address : 10 MARTIN PLACE, #17-14, MARTIN MODERN, SINGAPORE 237963

The director being involved in a bizarre mix of different companies, including immigration ( link ) , weddings, plastic surgery ( link )  , Weight loss, and engineering companies.

 Specifically, the Plastic surgery business has left lots of people our of pocket, and is connected to the other holding company;  quote “Anyway, both Dore Aesthethics and Dore Clinic are owned by Kate Holdings.The Director is Cheng Yong Teck who lives in Orchard Residences. Born in 1988.”

In the age of personalization and integration, being able to retrieve user profile images and basic information programmatically can be invaluable for CRMs, marketing platforms, and analytics systems. AvatarAPI provides a simple yet powerful way to fetch profile data from various providers, including Adobe, just by using an email address.

In this post, we’ll walk through how to retrieve Adobe profile details using AvatarAPI, including how to interpret the JSON response and especially the RawData payload.

📬 Making the Request

To fetch a user’s Adobe profile via AvatarAPI, you’ll need to send a POST request to:

https://avatarapi.com/v2/api.aspx

Here’s a sample request payload:

{
    "username" : "demo",
    "password" : "demo___",
    "provider" : "Adobe",
    "email" : "falecom@sergiolimabroker.com.br"
}

Replace username and password with your actual AvatarAPI credentials.

📦 Sample Response

Here’s what a successful response might look like:

{
    "Name": "",
    "Image": "https://mir-s3-cdn-cf.behance.net/user/276/63d4f1907178277.60f249006a140.jpg",
    "Valid": true,
    "City": "",
    "Country": "",
    "IsDefault": false,
    "Success": true,
    "RawData": "[{\"type\":\"individual\",\"authenticationMethods\":[{\"id\":\"google\",\"url\":\"https://adobeid-na1.services.adobe.com/renga-idprovider/social/v2/signin/google\"},{\"id\":\"password\",\"url\":null}],\"status\":{\"code\":\"active\",\"reason\":null},\"images\":{\"50\":\"https://mir-s3-cdn-cf.behance.net/user/50/63d4f1907178277.60f249006a140.jpg\",\"100\":\"https://mir-s3-cdn-cf.behance.net/user/100/63d4f1907178277.60f249006a140.jpg\",\"115\":\"https://mir-s3-cdn-cf.behance.net/user/115/63d4f1907178277.60f249006a140.jpg\",\"138\":\"https://mir-s3-cdn-cf.behance.net/user/138/63d4f1907178277.60f249006a140.jpg\",\"230\":\"https://mir-s3-cdn-cf.behance.net/user/230/63d4f1907178277.60f249006a140.jpg\",\"276\":\"https://mir-s3-cdn-cf.behance.net/user/276/63d4f1907178277.60f249006a140.jpg\"},\"hasT2ELinked\":false}]",
    "Source": {
        "Name": "Adobe"
    }
}

🧠 Understanding the Response Fields

• Image: URL of the profile image, typically hosted on Behance CDN.
• Valid: Boolean indicating whether a profile was found.
• IsDefault: Tells you whether the image is a generic placeholder or a custom user-uploaded image.
• Success: Boolean status of the request.
• Source: Confirms that the provider is Adobe.
• RawData: This is a stringified JSON array with more granular details from the provider.

🔍 Deep Dive into RawData

Let’s parse the RawData field for a better understanding:

[
  {
    "type": "individual",
    "authenticationMethods": [
      {
        "id": "google",
        "url": "https://adobeid-na1.services.adobe.com/renga-idprovider/social/v2/signin/google"
      },
      {
        "id": "password",
        "url": null
      }
    ],
    "status": {
      "code": "active",
      "reason": null
    },
    "images": {
      "50":  "https://...50.jpg",
      "100": "https://...100.jpg",
      "115": "https://...115.jpg",
      "138": "https://...138.jpg",
      "230": "https://...230.jpg",
      "276": "https://...276.jpg"
    },
    "hasT2ELinked": false
  }
]

Key Elements:

• type: Usually "individual", indicating a personal profile.
• authenticationMethods: Shows available login methods for this Adobe account (e.g., Google, password).
• status: Account status, with code typically being "active".
• images: Dictionary of image sizes for the profile picture. Useful for responsive UI.
• hasT2ELinked: Indicates whether the account is linked to two-factor authentication (T2E = Two-step or Two-element?).

🎯 Practical Use Case

If you’re building a user-facing dashboard, you can display a verified profile image directly using the Image field, and optionally allow your backend to parse RawData for more advanced logic, such as:

• Detecting authentication methods.
• Validating account status.
• Choosing image resolution dynamically based on device.

Example (JavaScript):

const profileImgUrl = response.Image;
document.getElementById('avatar').src = profileImgUrl;

🧪 Pro Tip: Parsing RawData

Since RawData is a stringified JSON array, you’ll need to parse it manually:

const rawData = JSON.parse(response.RawData);
console.log(rawData[0].authenticationMethods);

✅ Conclusion

Using AvatarAPI, retrieving Adobe profile details is seamless and efficient. The rich JSON response, especially the RawData, provides developers with a powerful toolkit to enhance user profiles, drive personalization, or even verify identity with minimal effort.

If you’re using AvatarAPI in production or need help parsing the Adobe-specific data, feel free to reach out or drop your questions in the comments!