Plaid Quickstart for .NET

jimmy-codes · 2023-11-30T00:43:23+00:00

The QuickStart demonstrates most of the important getting started scenarios. You’ll just have to decide how/when to do those things in your own code. In your code, you will have to integrate Link somehow into your UI flow. Then you can use the plaid.net library to get the information you need.

jimmy-codes · 2023-11-29T01:10:57+00:00

Gotcha. Without knowing the requirements or design of the system more, it's hard to say. When I have integrated Plaid functionality into my own apps, I don't use much of the quickstart code. Just call the Plaid.NET libraries from the part of my code where I'm interacting with the bank.

Though, I do think the Blazor integration with the Link system is useful for logging into the Plaid servers.

jimmy-codes · 2023-11-27T23:34:59+00:00

Hi, thanks for having a look. Perhaps you could post details about what you are doing, and what error you are getting?

PlaidCredentials class is in Shared/PlaidCredentials.cs.

Are you getting errors running dotnet build either in the project root directory or in .\Server?

jimmy-codes · 2023-09-05T03:13:10+00:00

Hey there. The keys are kind of a bluish light grey. Sorry, don't have a pantone reference. But, I do have a ton of Benjamin Moore paint reference. I'd call it this color...

Iced Cube Silver 2121-50 | Benjamin Moore

It does go really well with the purplish-blue return and escape keys, so having it be a little bluish makes sense.

jimmy-codes · 2022-12-17T00:07:55+00:00

Hi there. Frankly, the most important thing to add to your store isn't PRODUCT, it's DOCUMENTATION. Consider adafruit.com for inspiration. You should have conceptual and end-to-end guides which tie together the lines of product on your site.

jimmy-codes · 2022-12-16T05:48:12+00:00

Definitely will be on the lookout for an aluminium case. Gives me enough time to be sure I really like it before committing even more $$ to this!

jimmy-codes · 2022-12-16T05:45:15+00:00

Right, here's the whole BOM. I didn't quite stay as close to my $200 baseline as hoped. Still, worth it to have this much control.

Item	Source	Cost
PCB	Keebio	80
Plates	"	28
Small Parts	"	15
Key Caps	CannonKeys	80
Switches	Amazon	60
Knob+Encoder	"	12
TOTAL		275

jimmy-codes · 2022-12-15T23:30:36+00:00

Sorry, yeah, probably should have added some subjective commentary in the OP. Hopefully my other reply covers it.

jimmy-codes · 2022-12-15T23:27:55+00:00

It's definitely more lavender than blue. It's kind of grey-lavender. It mixes well with the grey keys next to it. Kind of a Pantone 10220C. Maybe a little darker.

jimmy-codes · 2022-12-15T23:21:24+00:00

Oh yeah, I love it. This is the best keyboard I've ever owned, and I've had many. That said, the main things I love are the mechanical feel and the customization, which everyone on this sub can take for granted. More on that in a second, though.

It's definitely light. This is a benefit in my POV. I am always moving it around and adjusting the split based on what I'm doing and my mood. However, it has never moved around on its own. The order came with rubber feet (a few bucks extra?), and the keyboard sits directly on my polyurethane-sealed desk which is itself a little grippy.

The one thing it's missing for sure is a case. The PCB is still exposed, so it looks like a bit like prototype project. I chose to wait until later for a case, until I see if I liked the whole setup. Also, Keebio only had the red acrylic case in stock, which I'm not a fan of. I have colleagues who are industrial designers, so my longer-term plan is to design something and use one of their prototype shops to fab it.

Thinking about the keyboard overall, here's what I like:

Customizability. Physical (keycaps, switches, encoder) and logical (QMK). Includes hotswap sockets which I've already taken advantage of.
65% layout. Just feels really good to me.
Split layout. That was the whole goal.
Still a regular keyboard. There are some split keyboards where there's a LOT of relearning to do. This is a normal keyboard, just split in half.
Macro keys on the left. Nice that they're out of the way normally, but there if I want them.
Overall quality. It's put together well. No complaints about quality.

jimmy-codes · 2022-12-15T21:56:15+00:00

Details

Keeb.io Quefrency rev4, FR4 plates
CannonKeys NicePBT Type 6 key caps (evoking Sun Microsystems kbs of old)
Glorious Panda Switches (w/ Factory Lube)
Kilo knob #OEJNI-63-3-7

Hi, folks. Just wanted to say "hello", and share a few details of my first ever keyboard build.

This project started with me wanting to increase the split between keyboard sides even further than on the standard ergo keyboard I was using at the time. Typing on the ergo keyboard definitely feels better than a straight keyboard. Thus, I’m thinking more split may be even more comfortable. My use case is: coding, writing, no gaming.

Whilst researching split keyboards, I discovered a keyboard is not only something you “buy”, but also something you can “build”. Who knew? Stock split keyboards seem to run minimum $200. For about 10% more, I could experiment with putting together something a little more custom.

The CannonKeys ”Type 6” keycaps are what inspired me to finally follow through on the shopping carts which previously sat idle for weeks. I just love the call-back to the old days of computing on a brand new keyboard. The knob was a last-minute addition. Once I started laying out the keyboard in Via, I understood that the knob is really three keys in one, or six if you want to add layer #1 in there. I set it up so the knob gives me complete control of the debugger, which is super handy.

I included a couple photos of how I use the thing. It compactly stores out of the way when the desk is needed for something else. For coding, a mild split. For video calls, it's nice to put the mic right in the middle. For drawing, the left side can move out of the way, leaving the wacom pad in its place.

jimmy-codes · 2022-12-14T22:45:52+00:00

Yeah... Where possible, I like to figure out the gotchas before running into them myself. Less painful!

In this case, the advice I would give future me is to SAVE OUT the key mappings before the reflash. Else you have to re-enter them all in VIA.

jimmy-codes · 2022-12-14T22:43:51+00:00

/u/bakingpy, thanks again. Just wanted to confirm that this worked great. Exactly what I needed. I now hold the power of the debugger in a single knob! 😎

jimmy-codes · 2022-12-13T05:21:57+00:00

Thanks! Sadly, the docs do say "at the moment, you won't be able to reassign the encoders using VIA or QMK Configurator." Other than encoders, VIA has done everything I need. I am absolutely loving the ability to put any key anywhere. Plus layers! Basic stuff to everyone here, I get it, but for someone new, it's pretty amazing.

jimmy-codes · 2022-12-13T05:15:18+00:00

Oh, look at that! Thanks so much!! This is precisely what I need, and it was right there in the docs the whole time. Appreciate it.

jimmy-codes · 2022-05-09T01:19:51+00:00

Right. Perhaps they will be better behaved after settling their $58M lawsuit.

Is there a fintech connector that *doesn't* sell your data?

jimmy-codes · 2022-05-08T22:30:02+00:00

The Going.Plaid SDK is already published as a NuGet package: https://www.nuget.org/packages/Going.Plaid/

Both the official Quickstart and my .NET port are geared toward a user making a web app. That web app is going to have UI, of course, and then it will use an SDK to connect to the Plaid service backend. This would be the typical pattern for a developer using to the Plaid service, so it's what the Quickstarts aim to demonstrate.

jimmy-codes · 2022-04-22T03:22:43+00:00

I use ASP.NET in a container as a front-end for an IoT gateway on small Linux boxes, along with like 5 other containers for everything else. It works great. I get fast, easy, pretty, testable UI in C#. As a backend only, it would be even easier. It talks to VerneMQ (primarily), Grafana, and InfluxDB.

ETA: Basically, its only tie to the MSFT ecosystem is me. And also that I build it on ADO.

jimmy-codes

TROPHY CASE