Listen to this Post
Introduction: When Checking the Weather Becomes a Performance Test
There is something strangely frustrating about opening a weather app and discovering that the weather itself is the least interesting thing happening on your screen.
A weather application should be one of the simplest utilities on a modern operating system. You open it, glance at the temperature, check the rain forecast, and close it. Yet Windows 11’s built-in Weather experience can feel like something much heavier: a web-powered MSN experience wrapped inside the operating system, complete with advertising and a surprisingly large memory footprint.
That becomes especially noticeable when you are already watching system resources. In the experience described in the original report, the Windows 11 Weather app climbed beyond 1.2GB of RAM while essentially sitting idle. That is difficult to ignore when a native macOS Weather process reportedly used only around 246.7MB under the comparison conditions.
The issue is not simply that one application consumes more memory than another. The deeper question is what Microsoft believes a built-in operating-system utility should be.
Should an app that comes with Windows behave like a lightweight system tool, or should it behave like an MSN website monetized through advertising?
That distinction matters.
The Original Experience: A Simple Weather Check Turns Into a Resource Investigation
The problem started with something completely ordinary: checking whether heavy rain was going to continue.
After weeks of severe rainfall, the need was simple. The phone was charging, so the Windows 11 PC became the quickest way to look at the forecast before heading outside.
The weather information itself was useful. Microsoft’s Weather experience provides plenty of practical information, including hourly forecasts, precipitation details, wind conditions, radar imagery, air-quality information, moon phases and severe-weather alerts.
But while the forecast was doing its job, something else was happening in the background.
Task Manager revealed that the application was consuming more than 1.2GB of memory without requiring extensive interaction from the user.
That immediately raises a reasonable question: why does a relatively simple weather dashboard need that much memory?
The Advertising Problem: Windows Is Already a Paid Product
Memory consumption is only half of the criticism.
The other issue is advertising.
Windows 11 is not traditionally presented to consumers as a free, ad-supported operating system. Users purchase Windows licenses, buy PCs that include Windows, or subscribe to licensing arrangements through businesses and organizations.
That makes advertising inside built-in utilities particularly controversial.
Microsoft has increasingly experimented with promotional content across its ecosystem, including Windows, Bing, MSN, Microsoft Edge and various built-in experiences. From Microsoft’s perspective, these placements can help fund services and keep users inside its ecosystem.
From the
If someone has already paid for Windows, why should a basic system utility resemble an advertising-supported website?
The MSN Connection Explains a Lot
The Weather experience becomes easier to understand once you recognize its MSN connection.
Rather than functioning purely as a lightweight native Windows utility, Windows 11’s Weather experience is closely tied to Microsoft’s MSN ecosystem.
That explains why users can encounter sponsored content alongside forecast information.
The result is an unusual mixture: a system application that looks like part of Windows but behaves in many respects like a web-based content platform.
That distinction is important because Microsoft is not merely displaying weather data. It is building an environment where weather information, news, recommendations and advertisements can coexist.
When an Advertisement Looks Like Weather Data
One particularly questionable design choice is how promotional tiles can visually blend into the forecast interface.
Imagine opening the application and seeing temperature, wind and precipitation cards arranged neatly across the screen. Then, among those cards, you encounter a sponsored promotion such as an Adobe Acrobat advertisement.
The problem is not necessarily that advertising exists.
The problem is context and presentation.
When advertisements are designed to resemble the visual language of genuine system information, the boundary between utility and commercial content becomes less obvious.
A weather app should make the weather the star.
It should not make users wonder which parts of the interface are forecasts and which parts are marketing.
Microsoft Does Have a Defense
To be fair, there is a legitimate argument on Microsoft’s side.
High-quality weather information is not free to produce or distribute. Weather platforms rely on data from numerous meteorological organizations and commercial providers, and Microsoft’s credits have referenced sources such as Foreca and the European Centre for Medium-Range Weather Forecasts.
The Windows Weather experience also provides considerably more information than a basic temperature widget.
Radar maps, precipitation predictions, wind data, air-quality information and severe-weather alerts all require infrastructure.
So there is a reasonable argument that Microsoft needs ways to support the service.
But that still does not completely explain the memory footprint.
The Bigger Concern Is the RAM Usage
Advertising may be irritating, but excessive memory consumption can have a measurable effect on the computer.
According to the reported test, Windows 11’s Weather app exceeded 1.2GB of RAM while idle.
That is an enormous amount of memory for something whose primary function is displaying weather information.
For comparison, the macOS Weather application reportedly used approximately 246.7MB in the same broader investigation.
That means the Windows experience was using nearly five times as much memory under the reported conditions.
The exact numbers can vary depending on operating-system versions, application versions, background services, cached data and system configuration, so they should not be treated as a universal benchmark.
But the magnitude of the difference is still worth discussing.
Deep Analysis: Why Is a Weather App Using So Much RAM?
The explanation becomes clearer when examining the application architecture.
The Windows 11 Weather experience uses Microsoft’s WebView2 technology, which is based on the Chromium browser engine.
That means the application can essentially behave like a website while appearing to users as a normal Windows application.
The architecture has advantages.
Developers can reuse web technologies, update content quickly and maintain a common experience across different platforms and services.
But there is also a cost.
A browser-based application can require multiple processes for rendering, networking, graphics, JavaScript execution and other tasks.
That is why opening Task Manager and expanding the Weather application’s process tree can reveal several Chromium-related processes rather than one compact native application.
Deep Analysis: Investigating Weather with Task Manager
Windows users can examine the
Press:
Ctrl + Shift + Esc
Then:
Processes → Weather
Expand the process if Windows exposes child processes.
You can also inspect memory consumption from the Details tab.
For deeper investigation, PowerShell can help identify processes associated with WebView2 or Chromium-based applications:
Get-Process |
Where-Object { $_.ProcessName -match "msedge|webview|weather" } |
Select-Object ProcessName, Id, WorkingSet64, CPU
To display memory usage in megabytes:
Get-Process |
Where-Object { $<em>.ProcessName -match "msedge|webview|weather" } |
Select-Object ProcessName, Id,
@{Name="RAM_MB";Expression={[math]::Round($</em>.WorkingSet64 / 1MB, 1)}}
These commands do not prove that every byte belongs exclusively to the Weather interface, because WebView2 infrastructure can involve shared processes and components.
They are nevertheless useful for understanding why a seemingly simple application can produce a surprisingly large process footprint.
Deep Analysis: Web Apps Are Not Automatically Bad
It is important not to turn this into an argument that every web application is poorly designed.
Web technologies are extremely powerful.
Microsoft can update a web-based interface without rebuilding an entire native application architecture. Developers can share components, deploy content rapidly and maintain sophisticated interfaces without writing everything using traditional Windows technologies.
The problem appears when the architecture becomes disproportionate to the task.
A weather application does not need to behave like a full browser tab with multiple layers of content, advertising, tracking, recommendations and dynamic components.
A native application can potentially be much more tightly optimized for the operating system.
Why WebView2 Can Become Heavy
WebView2 is built around Microsoft
Chromium’s multi-process architecture is one of its strengths because process separation can improve stability and security.
But it also introduces overhead.
A web-based Windows application may need processes handling:
Browser
Renderer
GPU
Network
Utility
Web content
Not every application will create the exact same process structure, and some processes may be shared.
Still, the architecture explains why a web wrapper can consume substantially more memory than users expect from a small utility.
This is where
Native Windows Apps Could Change the Equation
Microsoft has been working toward a broader modernization of Windows applications.
The
That makes the Weather application an interesting example.
If Microsoft genuinely wants Windows
It is visually simple enough to become a showcase.
WinUI Could Be the Better Path
A modern WinUI-based Weather application could potentially provide the same core information without requiring the interface to operate primarily as a web experience.
That does not automatically guarantee lower memory usage.
Native applications can also be poorly optimized.
But Microsoft would have greater control over the application’s integration with Windows, rendering pipeline, lifecycle and resource management.
The goal should not simply be replacing WebView2.
The goal should be building an application that uses the right technology for the job.
The Problem Extends Beyond Weather
Weather is only one example of a broader Windows design philosophy.
For years, Microsoft has increasingly relied on web technologies to deliver experiences that users perceive as traditional desktop applications.
That approach can be practical from a development perspective.
But when every utility starts carrying browser-style overhead, the cumulative effect becomes more significant.
One application consuming an extra few hundred megabytes may not matter on a high-end PC with 32GB or 64GB of RAM.
On a laptop with 8GB or 16GB, however, unnecessary background consumption can become much more noticeable.
Windows 11 Already Has a Performance Reputation to Protect
Windows 11 has made significant progress since its launch, but performance and efficiency remain sensitive subjects among PC users.
People notice when an operating system feels heavier than it should.
They notice startup applications.
They notice background processes.
They notice Microsoft Edge processes.
They notice widgets.
They notice advertising.
And they certainly notice when a basic utility consumes hundreds of megabytes or more.
The Weather application therefore becomes symbolic of a larger problem: Windows should not make users feel like they are running a web browser simply to check the temperature.
Ads and Performance Create a Double Frustration
Either issue alone would be easier to defend.
Advertising can be justified as a way to support online services.
Resource consumption can be justified as the unavoidable cost of a sophisticated application.
Put them together, however, and the user experience becomes harder to defend.
The user is effectively giving Microsoft two things: attention and system resources.
In return, the user receives weather information that could theoretically be delivered through a much lighter interface.
That imbalance is what makes the criticism resonate.
Apple Provides an Interesting Comparison
The comparison with
Apple has a fundamentally different business model from Microsoft.
Apple makes enormous amounts of money from hardware, services and its broader ecosystem, whereas Microsoft’s consumer Windows strategy has historically involved a wider mixture of software, services, subscriptions and advertising.
So the companies cannot be compared perfectly.
Nevertheless, Apple demonstrates that a mainstream operating-system vendor can provide a polished weather experience without turning the core interface into an advertising surface.
Windows Users Should Not Have to Pay Twice
There is a psychological difference between an application you voluntarily download for free and an application that arrives as part of the operating system.
When a free website shows advertisements, most people understand the bargain.
The website provides a service.
The advertiser pays for exposure.
The user pays with attention.
But when advertisements appear in an operating system that the user already paid for, the relationship feels different.
It can create the impression that Microsoft is monetizing the same customer twice.
Microsoft Account Integration Raises Another Question
The Weather experience also encourages users to sign into a Microsoft account.
This fits
From
For privacy-conscious users, however, every additional login requirement raises another question:
Why does checking the weather need an account?
A simple forecast should ideally remain a simple forecast.
The Bigger Microsoft Strategy: More Services Inside Windows
Microsoft has spent years turning Windows into a gateway for its broader ecosystem.
Bing, Edge, OneDrive, Microsoft 365, Copilot, MSN and other services increasingly appear throughout the operating system.
There is a commercial logic behind this strategy.
Windows has an enormous installed base, and Microsoft wants to convert that audience into recurring engagement with its services.
But there is a point at which integration becomes intrusion.
Weather is a particularly sensitive example because users expect it to be a utility rather than a portal.
Why Microsoft Should Make Weather a Showcase App
A redesigned Weather application could demonstrate what Microsoft wants modern Windows software to become.
Imagine opening Weather and seeing:
Instant startup.
Low memory usage.
No advertisements.
No unnecessary account requirement.
Fast radar rendering.
Clear hourly forecasts.
Excellent accessibility.
Native Windows animations.
Efficient background updates.
Minimal CPU activity when idle.
That would send a powerful message.
It would tell developers that Microsoft is serious about performance.
The Opportunity for Microsoft
Microsoft does not need to abandon MSN.
The company could keep MSN as a separate content platform.
The Weather application could simply provide the forecast.
Users who want news, articles and additional content could visit MSN voluntarily.
That separation would create a cleaner product boundary.
Windows would provide a utility.
MSN would provide a content platform.
Advertising could remain where users expect it.
What Microsoft Should Fix First
The first priority should be memory consumption.
If a Weather process genuinely requires more than a gigabyte under ordinary idle conditions, Microsoft should investigate exactly where that memory is going.
The second priority should be advertising.
Sponsored content should not visually compete with critical weather information.
The third priority should be account requirements.
Users should be able to obtain basic weather information without signing into an online ecosystem.
The fourth priority should be startup and background behavior.
A weather application should remain quiet when the user is not using it.
What Users Can Do Right Now
If Windows
Open:
Settings → Apps → Installed apps
Find the relevant Weather/MSN application and review its available options.
Users can also examine:
Settings → Apps → Startup
and disable unnecessary applications from launching automatically.
Task Manager can also help identify whether Weather or related WebView2 processes remain active after closing the visible interface.
Windows Performance Commands Worth Knowing
For users who want to investigate their system more deeply, PowerShell provides useful information.
To identify high-memory processes:
Get-Process |
Sort-Object WorkingSet64 -Descending |
Select-Object -First 20 ProcessName, Id,
@{Name="RAM_MB";Expression={[math]::Round($_.WorkingSet64 / 1MB, 1)}}
To inspect CPU-heavy processes:
Get-Process | Sort-Object CPU -Descending | Select-Object -First 20 ProcessName, Id, CPU
To find Microsoft Edge/WebView-related processes:
Get-Process |
Where-Object {$_.ProcessName -match "msedge|webview"} |
Select-Object ProcessName, Id, CPU, WorkingSet64
These tools are especially useful when diagnosing whether a supposedly closed application is still leaving background components active.
Microsoft Is Already Moving Toward More Native Experiences
The criticism becomes even more interesting because Microsoft has been signaling a stronger focus on native Windows applications.
Recent Windows development efforts have touched several inbox applications, while Microsoft developers have publicly discussed improving native Windows software and reducing the performance penalties associated with modern application frameworks.
That creates a contradiction.
Microsoft wants Windows to become faster and more efficient, yet some of its own built-in experiences still resemble web pages packaged as applications.
Weather is therefore more than an isolated annoyance.
It is a test of whether
What Undercode Say:
1. Weather Should Be a Utility
A weather application has one primary responsibility: tell you what the weather is doing.
It should not feel like a portal.
It should not require a large browser engine to remain open.
And it should not compete with advertisements for the user’s attention.
- The RAM Figure Is the Real Warning
The reported 1.2GB memory footprint is much more concerning than the advertising itself.
Ads are annoying.
Excessive resource consumption can affect the entire machine.
3. Web Technology Is Not the Enemy
WebView2 is not inherently bad.
It gives developers flexibility and enables Microsoft to reuse modern web technologies.
The problem is using a heavyweight technology stack where a lightweight native solution could be more appropriate.
4.
Microsoft cannot realistically ask developers to optimize Windows applications while its own inbox applications appear inefficient.
The operating system vendor has to lead by example.
5. Native Does Not Automatically Mean Fast
A native application can still waste memory.
WinUI alone will not solve everything.
Microsoft would need to combine native architecture with aggressive performance engineering.
6. Advertising Needs Better Boundaries
Users generally understand advertising on free services.
They become less accepting when advertisements appear inside paid operating-system functionality.
Microsoft needs to recognize that distinction.
7. The Weather Interface Should Be Cleaner
Forecast cards should look like forecast cards.
Advertising should be clearly separated.
The current approach risks making commercial content feel like part of the operating system itself.
8. The MSN Brand Changes User Expectations
Calling the experience MSN Weather makes its advertising model easier to understand.
But embedding that experience into Windows changes what users expect.
Windows users expect built-in utilities to behave like system components.
9. Microsoft Account Requirements Should Be Limited
Checking the temperature should not require a cloud identity.
Account integration can be optional.
Basic functionality should remain accessible without unnecessary sign-in.
10. Memory Matters More on Affordable PCs
Not every Windows user has 64GB of RAM.
Many laptops still ship with relatively modest memory configurations.
A poorly optimized background application can therefore have a meaningful impact.
11. Windows Needs Fewer Invisible Costs
Modern operating systems already perform thousands of background tasks.
Every unnecessary process adds complexity.
Every extra browser process consumes resources.
Every background service makes troubleshooting harder.
12. Performance Is a User Experience Feature
Users do not care which framework an application uses.
They care whether it opens quickly.
They care whether it responds instantly.
They care whether it consumes excessive memory.
13. Microsoft Has an Opportunity
The Weather app could become a demonstration of Microsoft’s modernization ambitions.
Rebuild it properly.
Remove unnecessary advertising.
Reduce memory usage.
Make account integration optional.
Then ship it as an example for developers.
14. The Comparison With Apple Is Useful
Apple’s business model is different, but the comparison demonstrates an important point.
A weather application does not inherently need advertising to provide value.
Microsoft can choose a different strategy.
15.
Cloud integration is useful.
But not every local Windows utility needs to behave like a cloud-connected portal.
Some functions should remain simple and local.
16. Web Wrappers Have a Place
Web wrappers are excellent when speed of development and cross-platform content matter.
They are less attractive when used for tiny utilities that users expect to be lightweight.
17. Windows Needs an Inbox-App Philosophy
Microsoft should define clear performance budgets for built-in applications.
A weather app should have an expected memory ceiling.
If it exceeds that ceiling, the application should be investigated.
18. Advertising Should Never Obscure Information
Severe-weather warnings deserve priority.
Rain forecasts deserve priority.
Temperature deserves priority.
Commercial promotions should come last.
19. Users Notice Inconsistency
Windows tells developers to build modern applications.
Users then discover heavyweight built-in utilities.
That contradiction damages confidence.
- The Problem Is Bigger Than One App
Weather is simply the most visible example.
The same discussion applies to other Windows experiences that rely heavily on web technologies.
21. Microsoft Should Measure Idle Performance
The most important benchmark is not simply how much memory Weather consumes while displaying a radar map.
The real question is what happens when the application is doing almost nothing.
22. Background Activity Should Be Minimal
A weather application does not need to behave like a browser session after the user closes it.
Background updates should be controlled.
23. Better Caching Could Help
Weather data does not need to be reconstructed from scratch every time.
Smart caching could reduce network activity and potentially improve responsiveness.
24. Microsoft Should Separate Content From Utility
The Weather application should provide weather.
MSN can provide news.
Bing can provide search.
Microsoft Edge can provide browsing.
Clear boundaries would make Windows feel less cluttered.
- The Future of Windows Depends on Trust
Users need to trust that Windows is working for them.
Aggressive promotions can weaken that relationship.
Excessive resource usage can weaken it further.
- Windows Should Feel Like an Operating System
The operating system should disappear into the background when users are working.
It should not constantly demand attention.
27. Lightweight Design Is Still Valuable
More features do not automatically mean better software.
Sometimes the best upgrade is removing unnecessary complexity.
28. Microsoft Has the Engineering Talent
This is not an impossible engineering problem.
Microsoft operates one of the
It has the resources to rebuild a weather application properly.
29. The Question Is Prioritization
The challenge is whether Microsoft considers this problem important enough to fix.
That is ultimately a product decision.
30. WinUI Needs a Strong Showcase
A fast, polished Weather application would be an excellent demonstration of what modern Windows development can achieve.
Users would immediately understand the benefit.
31. Developers Watch
Third-party developers often follow
If Microsoft embraces lightweight native applications, developers have a stronger reason to reconsider excessive web wrappers.
32. Performance Should Be Measurable
Microsoft should publish meaningful performance targets for inbox applications.
Memory usage.
Startup time.
CPU utilization.
Background activity.
These numbers would create accountability.
33. Users Should Have Control
Windows should allow users to remove or disable optional experiences they do not want.
Not every Microsoft service needs to be permanently integrated.
34. Privacy and Performance Often Overlap
Reducing unnecessary cloud connections can sometimes improve both privacy and performance.
A simple local-first weather interface could achieve both.
35. The Weather App Is Symbolic
The real debate is not about rain forecasts.
It is about what Windows should become.
A platform.
A service marketplace.
An advertising channel.
Or a clean operating system.
- Microsoft Can Have Both Utility and Services
There is no reason Microsoft cannot maintain MSN as a profitable service while keeping core Windows utilities clean.
The two strategies do not have to conflict.
37. Advertising Should Be Opt-In Where Possible
Users who want recommendations can enable them.
Everyone else should receive the utility they asked for.
That would dramatically improve perception.
38. Performance Builds Loyalty
Users remember software that feels fast.
They also remember software that makes their computer feel slow.
Microsoft should understand the difference.
- Weather Could Become a WinUI Success Story
Instead of being criticized as an MSN web wrapper, Weather could become the application that demonstrates Microsoft’s native Windows ambitions.
That would turn a weakness into an opportunity.
40. The Forecast Is Not the Problem
Ironically, the weather information itself appears to be one of the strongest parts of the experience.
The problem is everything surrounding it.
The advertisements.
The web architecture.
The memory footprint.
The account integration.
And the feeling that a simple utility has become another gateway into Microsoft’s online ecosystem.
✅ Microsoft Weather Uses Web Technologies
The criticism that the Windows Weather experience relies heavily on web technology is consistent with its WebView2-based architecture.
That helps explain the presence of multiple Chromium-related processes and the application’s potentially larger memory footprint.
✅ Windows Weather Provides Detailed Information
The application offers more than a basic temperature reading, including forecasts, precipitation information, radar-related features, air-quality data and severe-weather information.
The service therefore has legitimate infrastructure and data requirements.
⚠️ The 1.2GB RAM Figure Is Not Universal
The reported 1.2GB+ figure should be treated as a test observation rather than a permanent specification of every Windows 11 installation.
Memory usage can change with Windows builds, Weather versions, cached content, system configuration and background processes.
⚠️ The “Five Times More RAM” Comparison Needs Context
The comparison with approximately 246.7MB on macOS illustrates the scale of the reported difference, but it is not a universal benchmark.
Different operating systems, versions, hardware and measurement conditions can produce different results.
❌ “Windows Weather Is Basically Adware” Is an Opinion
Calling the application “adware” is a characterization rather than a formal technical classification.
The application does contain promotional content, but that does not automatically make it malicious advertising software.
The criticism is primarily about
Prediction
(+1) Microsoft Will Continue Moving Toward More Efficient Windows Apps
Microsoft is likely to continue modernizing its inbox applications as Windows becomes more performance-conscious.
If the company follows through on its broader push toward native Windows development, applications such as Weather could eventually receive deeper architectural changes.
A future version could reduce its dependence on WebView2, improve startup performance and substantially reduce idle memory usage.
(+1) Advertising Will Become More Carefully Integrated
Microsoft is unlikely to abandon advertising across its consumer ecosystem completely.
However, pressure from Windows users may encourage the company to make advertisements less intrusive and more clearly separated from core system functionality.
(+1) Native Weather Could Become a Windows Showcase
A completely redesigned, lightweight, native Weather application would be a relatively small project with a highly visible payoff.
If Microsoft wants to prove that modern Windows applications can be fast, efficient and polished, Weather is one of the easiest places to demonstrate it.
(-1) Microsoft May Keep MSN Integration
The biggest obstacle is
MSN remains part of the
That means the commercial incentive to keep Weather connected to MSN is likely to remain strong.
Final Verdict: Windows 11 Deserves a Better Weather App
A Simple Utility Should Not Feel Heavy
The central criticism is difficult to dismiss.
A weather application can legitimately require sophisticated data sources, maps and live forecasts. It can also be built using modern web technology for perfectly valid engineering reasons.
But when a basic system utility reportedly consumes more than a gigabyte of RAM while displaying advertisements, Microsoft has a responsibility to ask whether the architecture has become unnecessarily complicated.
The answer should not simply be to optimize the existing web wrapper until it is slightly less heavy.
Microsoft should consider rebuilding the experience around the principles users actually expect from an operating-system utility: fast, lightweight, private, clear and unobtrusive.
The Forecast Should Come First
Windows 11 does not need to turn every built-in application into another advertising surface.
Microsoft already has enormous platforms for search, news, advertising and cloud services.
The Weather app has a simpler job.
Tell people whether they need an umbrella.
If Microsoft can deliver that experience without consuming a suspiciously large portion of system memory—and without placing advertisements between users and their forecast—it would be a small but meaningful victory for the future of Windows.
Because sometimes the best sign that an operating system is getting better is not another AI feature or another redesigned interface.
Sometimes it is simply opening an app, checking the weather, and watching the rain without watching your RAM disappear.
🕵️📝Let’s dive deep and fact‑check.
🎓 Live Courses & Certifications:
Join Undercode Academy for Verified Certifications
🚀 Request a Custom Project:
Secure, high-velocity infrastructure and disruptive technological engineering. Contact our engineering team for high-tier development and proprietary systems:
[email protected]
💎 Smart Architecture | 🛡️ Secure by Design | ⭐ Trusted by Thousands
References:
Reported By: www.windowslatest.com
Extra Source Hub (Possible Sources for article):
https://www.pinterest.com
Wikipedia
OpenAi & Undercode AI
Image Source:
Unsplash
Undercode AI DI v2
🔐JOIN OUR CYBER WORLD [ CVE News • HackMonitor • UndercodeNews ]
📢 Follow UndercodeNews & Stay Tuned:
𝕏 formerly Twitter 🐦 | @ Threads | 🔗 Linkedin | 🦋BlueSky | 🐘Mastodon | 📺Youtube
