nullgato

Sorry for the late reply! Honestly, I just kinda wanted to try something new. I find playing around with the bleeding edge fun and if it means I find a genuinely good replacement, that's even better! Bun is still pretty young and I still need to have Node installed for some edge cases, but my experience using it was a genuine joy and I found it easier than with Node.

Definitely brings back ancient memories huh?

I just wanted to share this because I'm an aero enthusiast and think this is amazing, but full disclosure I'm a contributor on this project. This is Aerochat! It's basically an open source WLM wrapper around Discord, also wraps Discord's native login via WebView2 making it account-safe. It tries to emulate WLM as closely as it can considering it's still Discord under the hood. It's pretty solid as it is right now, but new features are added daily as we hammer out what we can. There's a lot that's missing because it's still pretty early in development like no videos, mostly missing embeds, so on. But yeah! If you have any interest in reliving WLM then I highly recommend Aerochat even if I'm biased lol. And for those who want a more authentic experience, Escargot.chat uses the native WLM applications for their service but I don't know much about that project beyond that it exists.

Sorry for the long wait on this! I only have one project at the moment, but I'm working on a music player widget to display on my streams that can be reactive to input sent from my stream deck. The widget and server have a subscribe/publish pattern, and the communication works like this: Widget <-> Webserver The websocket allows for efficient data flow keeping media player data synchronized such as current song, estimated seek position, song attributes, album art, commands such as play/pause/previous/next, far faster than API requests. The webserver's role in this relationship is to communicate desired changes to the widget where the widget will then send a response as to whether that desired change was successful or not. Stream Deck <-> Webserver The Stream Deck interacts via API to send/process my desired commands which will have a success/failure result depending on the decision made on the backend. For example if I ask for a specific song but the song for some reason isn't available, this will not be forwarded to the Widget and the Stream Deck will be given a failure response to display to me. Likewise for the opposite, if the song exists and the Widget & Player were able to have a successful interaction, I'll be given a successful response and the Stream Deck will report that to me visually as well. Desired commands because I like to keep realistic expectations that I'm sure I'll have undesired outcomes at times.

ℹ Overview This is my own web development framework I wrote for a couple of my projects I'm working on. It includes some helper tools that allow you to get started developing for the Bun platform (similar to Node JS) in TypeScript with easy to read logging, easy routing, and the repository contains sample code to get you off and running. It also includes some potentially useful stuff for websockets since that's required for one of my projects as well like a base packet structure that includes (de)serialization methods to make using it easy. My own favorite feature is the string interpolation I've added where you can create an html file with {{ variable }} as the text and you can use the included helper class to load the file with the object containing your variables to be replaced with. It's a small and easy thing to do, but gosh does it go a long way. Available on npm under the package @nullgato/transgress Features An alright routing system Probably okay performance A middleware system Support for websockets (not really a flex, I'm running out of yays) Support for HTML pages and {{variable}} within them A template for websocket packets via abstract class BasePacket Uhhhhh Example Usage import { Logger, Middleware } from '@nullgato/transgress/core' import { transgress } from '@nullgato/transgress' import type { ILogger, ILogObject, ITransgressOptions } from '@nullgato/transgress/interfaces' import { OLogLevel, type RouterResponse } from '@nullgato/transgress/types' // you can write your own ILogger, but one is provided for you const logger = new Logger(OLogLevel.Info) // same with the IMiddleware interface const middleware = new Middleware(logger) middleware.register({ name: 'middleware', callback: async (logger: ILogger, req: Request): RouterResponse => { return new Response('hewwo', { status: 200 }) }, log: (logger: ILogger, data: string | ILogObject): ILogger => { return logger }, }) const options: ITransgressOptions = { development: true, // the errorHandler is optional errorHandler: (error: Error) => { return new Response('rip', { status: 200 }) }, middleware, port: 12000, } const server = transgress(options) // Server is now listening for connections Source on GitHub https://github.com/nullgato/transgress

I was wondering if it's absence was purposeful or just hadn't been migrated over? I don't really do a whole lot of game development anymore but I do quite a bit of other miscellaneous development like web, mobile, bash/PS utils, so having that category would be really neat but I also understand if Cooldown has shifted towards being explicitly gaming.

This is an amazing upgrade, I love the new aesthetic! Also some really cool feature additions. :3

Surprisingly it's still around somehow (and the company behind it makes Games I guess?) lol. But I think these days what it's capable of is a lot less than it used to with Microsoft changing so much with the recent W11 updates.

Hi! Haven't posted in a while and don't have anything project worthy to yap about, so I figured I'd share some screenshots of this little transformation project I've undertaken! And my reason as to why I'd do such a thing to begin with. Experiencing this is really exciting for me because Windows 7 represented a little pocket of happiness in my life. Some of my fondest memories are playing Conquer Online, jamming to whatever songs I had downloaded from some sketchy site/app in my Windows Media Player. Studying programming on the weekends. Giving people like Spirited headaches with my irritating teenage-level understanding questions via forums. I even remember using Visual Studio Express 2008, back when light themes were your only option so writing C# came at the cost of your retinas! Frutiger aero/skeuomorphism design, to me, had an element to it that in hindsight felt so happy. So promising. Like the future contained an infinite set of possibilities and whatever those were, were potentials to look forward to. For some reason, embracing that gives me a little bit of that feeling back. It also provides me a sense of rebellion towards a company who continues to steer their OS in a direction I genuinely do not agree with. There's an element of magic in being able to say: This is *my* Windows, and I've crafted my experience to be something that makes me feel good. So I plan on holding onto that magic and letting it be a source of motivation. Anyway, life story over. Without further ado, Windows 10: Aero Edition! :3 Not pictured: Action center, other flyouts with proper theming, Windows 7 style alt-tabbing, start menu, various control panel applets Disclaimer: I have not developed any of the applications, modules, or themes to make this happen. This is just me stitching together the various works of the fine people over at WinClassic.net - Doing such a thing puts you at a security risk, may break parts of your operating system, or worse: renders your system inoperable. Please be cautious if you attempt anything like this. Do not run any code you're not able to audit or cannot be confident in the source of. Firefox theme credit belongs to the Echelon team.