There's not only an #Apple Steve. MS has their own stereotypical #DotNet version.
Talking of Steve-like jobs, this particular CEB Distinguished Engineer at #Microsoft sure loves to sprinkle #AI fairydust into disbelieving eyes, with 💫 dizzying enthusiast levels:
> “Our North Star is 1 engineer, 1 month, 1 million lines of code”
Rookie: What should I do?
CEB: We'll keep you out of the wind first few days. 250k LoC is fine.
(CEB = Chronically Excitable Ballmer, awarded to MS chief employees)
The New Features and Enhancements in .NET 10
#dotnet
The New Features and Enhancements in .NET 10
#dotnet
These deep-dive #dotnet videos are a treasure!
"Cancellation Tokens with Stephen Toub"
https://www.youtube.com/watch?v=h1GvSPaRQ-U
These deep-dive #dotnet videos are a treasure!
"Cancellation Tokens with Stephen Toub"
https://www.youtube.com/watch?v=h1GvSPaRQ-U
FYI: LLVM vs .NET: Why Choose LLVM? #shorts: LLVM boasts significant industry and community support. It’s older than .NET, with backing and resources. LLVM offers versatility across platforms, empowering developers while requiring careful memory management. #LLVM #dotNET #compiler #technology #programming https://www.youtube.com/shorts/fwfBJivpZSE
Thinking of starting a Blame as a Service (BaaS) called "Blame Khalid”. For a monthly fee, you can blame all your #dev woes on me.
When your boss asks why you're behind.... Khalid
When your stakeholders ask why the feature is broken... Khalid
When you miss deployment deadlines… You guessed it, Khalid!
Reach out to find the right service plan for you and your team. There will be personal and enterprise plans. No longer shoulder your failures alone, let me help!
And here is the polished and fully functional version! 🥳 It is very cool to be able to debug C64 assembly code written in C#. You can modify all registers, stack variables, zero pages variables (you get access to their names!), VIC/SID registers. You can view the memory. Disassemble code. Step in, step through, step out. Even data breakpoints should work! 🚀
This will be released on November 13th, on the day of my talk for the .NET Conf 2025, at 3:30PM - CET, save the date! 📅
And here is the polished and fully functional version! 🥳 It is very cool to be able to debug C64 assembly code written in C#. You can modify all registers, stack variables, zero pages variables (you get access to their names!), VIC/SID registers. You can view the memory. Disassemble code. Step in, step through, step out. Even data breakpoints should work! 🚀
This will be released on November 13th, on the day of my talk for the .NET Conf 2025, at 3:30PM - CET, save the date! 📅
Finally got also the VICE C64 debugger working with C# from Visual Studio as well. The experience is less smooth than VSCode for some aspects, so I won't demo it, but it is usable if you adapt your code to it It is still very cool to have such debugger support while not having to develop a VSIX extension for it! ✨
And here is the polished and fully functional version! 🥳 It is very cool to be able to debug C64 assembly code written in C#. You can modify all registers, stack variables, zero pages variables (you get access to their names!), VIC/SID registers. You can view the memory. Disassemble code. Step in, step through, step out. Even data breakpoints should work! 🚀
This will be released on November 13th, on the day of my talk for the .NET Conf 2025, at 3:30PM - CET, save the date! 📅
Woot! Prototyped this morning a C64 debugger for VSCode for my upcoming C# C64 development toolkit that I will present at the .NET Conf 2025 in November, and I got a first registers view working! 🥳
I should hopefully have something more polished to present! 🤞 It will be pretty cool as it will allow to step over C# code (that assemble 6502 code), with the ability to visualize all CPU registers, VIC, SID registers, zero pages variables...etc. all of that with live editing! 🚀
I went to use a visual studio extension today that helped upgrade older versions to newer ones, it was free, worked offline, and did a great job of converting projects while providing a helpful report of what was changed and other notes about the process. A recent update to visual studio has completely disabled this functionality and added a "Modernize" option that only works with a paid Copilot subscription. Terrible enshittification of a product, but while reading about a possible workaround, I found a nuclear take with one of the worst analogies I've ever seen anyone try to make:
https://developercommunity.visualstudio.com/t/Error-Message-when-loading-VS-20206-afte/10971375#T-N10974933
#VisualStudio #VisualStudio2022 #Microsoft #Copilot #DotNet #enshittification
New to this tag? 50 for FOSS is a monthly pledge where we each choose an open-source project we appreciate and donate $50 to it, no strings attached.
It's our small way of giving back and making free software more sustainable.
This month I'm donating to xUnit ( @xunit), the flagship unit-testing framework for .NET Core. I'm always grateful for how easy unit testing is in .NET, and xUnit's simple, predictable, organized approach is a big part of that.
Big thanks to @bradwilson for taking such good care of xUnit. It's a delight.
Today I've released version 1.5.3 of Dowstodon, my Mastodon client for Windows. It's got some neat improvements for the system notifications and a better look when transparency is disabled, but the biggest addition is the ability to search users by name on user's lists e.g. the following list.
I know it might be annoying to some, but I've also added a donations section the settings page. If you use the app and enjoy it, and have the means to, please consider donating to help development of it.
Oh God I always forget hashtags
https://apps.microsoft.com/store/detail/9PHNV45JVR2S?cid=Mastodon
Hey Fediverse! 👋
We just wrapped up an amazing FediForum June 2025 a week ago, and BadgeFed was right in the thick of it! Here’s a recap of what we did, what we learned, and what’s next for decentralized badges.
BadgeFed had the honor of presenting and hosting two unconference sessions and showing off our work in one speed demo slots (watch the demo). The energy was fantastic; lots of curiosity, sharp questions, and a real hunger for open standards in the credentialing space.
A big theme at FediForum was specs and open standards. We’re right there with you! That’s why we’ve enhanced our technical documentation to explain exactly how BadgeFed uses ActivityPub and OpenBadges together:
Read more in our DETAILS.md.
We heard you: people want to try BadgeFed! Right now, it’s a solo setup (one admin, one Docker container), but we’re working hard to make it easier for others to deploy, configure, and even federate their own instances. Stay tuned for updates on multi-admin support and streamlined onboarding.
One of the most important pieces of feedback we received was about badge discoverability vs. timeline spam (see the issue). We want badges to be easy to find and share, but we also don’t want to flood the Fediverse with unwanted posts. This is now our top priority, we’re rethinking how verbose BadgeFed should be, and exploring opt-in/opt-out models for badge visibility and hashtag use.
We’re also working on ways to let you embed badges in your blog or add them to your Mastodon profile. More news on that soon!
FediForum was a fantastic experience, huge thanks to everyone who attended, gave feedback, and showed interest in decentralized credentials. Let’s keep building a more open, verifiable, and user-empowered Fediverse!
Badge up, and see you in the timeline! 🏅
You can read the article "BadgeFed @ FediForum June 2025: Unconferences, Demos, and Community Feedback" by @mapachehere as well.
#activitypub #badgefed #fediverse #dotnet #decentralization #open-source #openbadges #identity #fediforum #recapHey Fediverse! 👋
We just wrapped up an amazing FediForum June 2025 a week ago, and BadgeFed was right in the thick of it! Here’s a recap of what we did, what we learned, and what’s next for decentralized badges.
BadgeFed had the honor of presenting and hosting two unconference sessions and showing off our work in one speed demo slots (watch the demo). The energy was fantastic; lots of curiosity, sharp questions, and a real hunger for open standards in the credentialing space.
A big theme at FediForum was specs and open standards. We’re right there with you! That’s why we’ve enhanced our technical documentation to explain exactly how BadgeFed uses ActivityPub and OpenBadges together:
Read more in our DETAILS.md.
We heard you: people want to try BadgeFed! Right now, it’s a solo setup (one admin, one Docker container), but we’re working hard to make it easier for others to deploy, configure, and even federate their own instances. Stay tuned for updates on multi-admin support and streamlined onboarding.
One of the most important pieces of feedback we received was about badge discoverability vs. timeline spam (see the issue). We want badges to be easy to find and share, but we also don’t want to flood the Fediverse with unwanted posts. This is now our top priority, we’re rethinking how verbose BadgeFed should be, and exploring opt-in/opt-out models for badge visibility and hashtag use.
We’re also working on ways to let you embed badges in your blog or add them to your Mastodon profile. More news on that soon!
FediForum was a fantastic experience, huge thanks to everyone who attended, gave feedback, and showed interest in decentralized credentials. Let’s keep building a more open, verifiable, and user-empowered Fediverse!
Badge up, and see you in the timeline! 🏅
You can read the article "BadgeFed @ FediForum June 2025: Unconferences, Demos, and Community Feedback" by @mapachehere as well.
#activitypub #badgefed #fediverse #dotnet #decentralization #open-source #openbadges #identity #fediforum #recapHey Fediverse, we’ve got some exciting news—BadgeFed is moving out of the prototype phase! That’s right, what started as a scrappy proof-of-concept is now becoming a real, structured, and (dare we say) polished federated badge system.
And since we believe in working out in the open, we want to share our roadmap with you.
We’re focusing on three major areas to take BadgeFed from “hey, this kinda works” to “oh wow, this is actually usable.”
Right now, logging in is a bit of a mess. So we’re tackling authentication properly, integrating OAuth so you can log in using your Mastodon (or other Fediverse) account.
We’re building this with .NET and Blazor because performance and scalability matter. Plus, no one wants to manage yet another username/password combo.
We’re making sure BadgeFed speaks ActivityPub fluently. Right now, federation kinda-sorta works, but we need to define a proper spec that makes badge issuing,
earning, and verification seamless across different platforms. Whether you’re on Mastodon, Pleroma, or something else entirely, BadgeFed should just work.
We’re ironing out the kinks so badges travel as smoothly as your cat pictures. Also we want to support export and import from OpenBadges spec, and we need to do some experimentation on how this could travel on the fediverse.
What’s cooler than a decentralized badge system? A decentralized badge system that’s easy to set up.
We’re working on clear documentation, making installation painless, and putting together a Docker container so you don’t have to wrestle with dependencies or even dotnet.
One command, and boom—you’re federating badges like a pro.
Once the big three are solid, we’re setting our sights on some much-needed improvements:
We’re heads-down working on these priorities, but as always, feedback, ideas, and contributions are welcome.
This is an open-source project, and the best way to make sure it fits the needs of the Fediverse is to have the community involved.
If you want to help, hop into our discussions, check out the repo at https://github.com/tryvocalcat/badgefed, or just share your thoughts. Let’s make federated badges a thing! 🏅
You can read the article "BadgeFed: From Prototype to Reality" by @mapachehere as well.
#activitypub #badgefed #fediverse #dotnet #decentralization #open-source #identity #roadmapUPDATE: A blog (that is federated) was created for communicate the progress, follow @badgefed
--
I am creating a #ActivityPub minimalistic implementation of a badge system similar to Credly, built using #dotnet and leveraging the #Fediverse
I have issued a first badge, the idea is to decentralize the verification systems, and allow organizations to self-certify. It is incredible that organizations like Microsoft or Non-Profits pay thousands of dollars to companies like Pearson to just provide "verified" badges. Similar to mastodons installed in social-dot-something, thinkg of badges<dot> mozilla<dot>com , certifications<dot>myschooldistrict<dot>com. Or even a podcast emitting a badge for its guests, with the verification in the domain.
ActivityPub already offers a secure way to sign artifacts and interact between actors. The fediverse already have people with profiles, a social graph as @mike says, ready to use. Think of how LetsEncrypt disrupted that market of few actors selling certificates for websites.
I have a functional poc,
@fediverse is not a mastodon, pledora or blog, it is an actor in a badge system, but you can follow it in Mastodon. Its badges will show in #mastodon but they are not notes or articles. If you want to learn more, follow me, I will be sharing the progress here. Or follow the github project here: https://github.com/tryvocalcat/activitypub-badges
Who wants a badge of early adopter?
