"Classic Teams will soon be unavailable for use" warning header #1156

rslagmolen · 2024-03-26T10:21:53Z

Describe the bug
Since this morning, this build of teams start with a warning header :
Classic Teams will soon be unavailable for use. To use the new Teams, update your browser to meet requirements or contact your IT admin. See requirements

NB: I'm still on 1.4.14 as the 1.4.15 is not yet in the AUR

To Reproduce
Simply open the client

Expected behavior
We should be on the new Teams (if possible)

Screenshots

Desktop (please complete the following information):

OS: GNU/Linux - Manjaro (based ArchLinux)
Installation package: AUR (it use the tar.gz source archive then build from source using "yarn electron-builder")
Version: 1.4.14

elhennig · 2024-03-26T10:34:07Z

Same here, see #1141

jbauerrfid · 2024-03-26T13:57:33Z

I am getting the same deprecation warning as well:

OS: Ubuntu 22.04 LTS
app: teams-for-linux 1.4.14, provided by snap

It would be sad to lose teams-for-linux, I really like it, and I don't want to use the PWA from Microsoft.

bymck · 2024-03-26T15:58:33Z

I have the same problem.
Classic Teams will soon be unavailable for use. To use the new Teams, update your browser to meet requirements or contact your IT admin. See requirements

ChristoSnake · 2024-03-27T07:44:18Z

I used this method (shared in various threads here) to force Teams v2.

Right-click the Teams icon in the taskbar, then select the Debug option. Select the Console tab at the top of the debug screen. Type the following in the console at the bottom of the debug screen, then hit Enter:

document.location.href = 'https://teams.microsoft.com/v2/'

If that does not work, follow the same steps but type both of the following commands (with an Enter after each):

window.localStorage.setItem("tmp.isOptedIntoT2Web", true)
document.location.href = 'https://teams.microsoft.com/v2/'

It should automatically load Teams v2 after a restart..

grizewald · 2024-03-27T07:52:25Z

Same message for me, with the latest 1.14.15 version of Teams for Linux
but fixed by the second set of commands in ChristoSnake's message.
Thanks!

christoph-teichmeister · 2024-03-27T07:54:15Z

I used this method (shared in various threads here) to force Teams v2.

Right-click the Teams icon in the taskbar, then select the Debug option. Select the Console tab at the top of the debug screen. Type the following in the console at the bottom of the debug screen, then hit Enter:

document.location.href = 'https://teams.microsoft.com/v2/'

If that does not work, follow the same steps but type both of the following commands (with an Enter after each):
window.localStorage.setItem("tmp.isOptedIntoT2Web", true)
document.location.href = 'https://teams.microsoft.com/v2/'
It should automatically load Teams v2 after a restart..

The fix proposed by @ChristoSnake worked for me! Thanks a lot! ❤️

elhennig · 2024-03-27T08:13:05Z

I used this method (shared in various threads here) to force Teams v2.

Right-click the Teams icon in the taskbar, then select the Debug option. Select the Console tab at the top of the debug screen. Type the following in the console at the bottom of the debug screen, then hit Enter:

document.location.href = 'https://teams.microsoft.com/v2/'

If that does not work, follow the same steps but type both of the following commands (with an Enter after each):
window.localStorage.setItem("tmp.isOptedIntoT2Web", true)
document.location.href = 'https://teams.microsoft.com/v2/'
It should automatically load Teams v2 after a restart..

Works for me. Is this is change persistent?

dom976 · 2024-03-27T08:41:01Z

How can the debug option be accessed from Gnome with the Flatpak app version?

christoph-teichmeister · 2024-03-27T08:44:12Z

How can the debug option be accessed from Gnome with the Flatpak app version?

@dom976

madzaf · 2024-03-27T08:47:37Z

How can the debug option be accessed from Gnome with the Flatpak app version?

In teams, you can also press Alt and a gnome window menu will appear. The Debug menu is in "Application"

christoph-teichmeister · 2024-03-27T08:49:28Z

Alternatively, in Teams, hit CTRL+D

dom976 · 2024-03-27T09:12:44Z

Thank you all, I cannot see the icon in the toolbar because an extension hides it. Anyway, both CTRL+D and Alt trick work.

mburkeSencon · 2024-03-27T09:15:34Z

As per other comments, I had this issue on the 1.4.15 version. Using the steps @ChristoSnake put out has fixed the issue.

Thank you!

riccardo94p · 2024-03-27T09:27:02Z

I used this method (shared in various threads here) to force Teams v2.

Right-click the Teams icon in the taskbar, then select the Debug option. Select the Console tab at the top of the debug screen. Type the following in the console at the bottom of the debug screen, then hit Enter:

document.location.href = 'https://teams.microsoft.com/v2/'

If that does not work, follow the same steps but type both of the following commands (with an Enter after each):
window.localStorage.setItem("tmp.isOptedIntoT2Web", true)
document.location.href = 'https://teams.microsoft.com/v2/'
It should automatically load Teams v2 after a restart..

This worked for me as well, thank you! 🥇

ChristoSnake · 2024-03-27T09:48:45Z

Works for me. Is this is change persistent?

Yes, it is.

Be aware that the taskbar icon will not show a notification count after switching. I'm using KDE's built-in notifications as a workaround:.

jbauerrfid · 2024-03-27T11:53:27Z

I can confirm #1156 (comment) is working in the Teams snap on Ubuntu

Edit: it appears this also survives restarts of the Teams snap.

jd-philips · 2024-03-27T12:56:27Z

I'm getting this message in the web version under Linux. I'm on Fedora 39, Chrome 122.0.6261.128 (Official Build) (64-bit). The requirements page don't mention browser requirements.

Bartwillemsen · 2024-03-27T13:00:50Z

The fix of @ChristoSnake works and is persistent, until you log out to switch account. I am working from 2 Teams accounts and whenever I need to switch I also need to apply the V2 fix again.

Can't this fix somehow be integrated in Teams for Linux? Because without it, soon the application will not work out of the box.

jd-philips · 2024-03-27T13:05:56Z

I can't believe Microsoft is in the midst of removing ALL SUPPORT for Linux, even in the web version. Just goes to show that they haven't changed at all.

jbauerrfid · 2024-03-27T13:29:30Z

I see it in our company:

all the management is working on Microsoft Windows and using Teams
all devs are working on Mac or Linux (UI prefers Mac, and backend prefers Linux), they use mostly Slack, and Teams only if they must because they don't like it

so Microsoft should consider why this is the case...

antimatter84 · 2024-03-27T13:43:11Z

I can't believe Microsoft is in the midst of removing ALL SUPPORT for Linux, even in the web version. Just goes to show that they haven't changed at all.

I am confused. Where did you get the info that they would remove all Linux support? I thought the PWA was created for all sorts of operating systems.

jd-philips · 2024-03-27T13:46:02Z

I am confused. Where did you get the info that they would remove all Linux support? I thought the PWA was created for all sorts of operating systems.

I'm on the web version and I still got that message. It may be just a technical mistake by Microsoft.. but this is the requirements page I'm pointed to: requirements and I see a lot of references to unsupported OS. Hopefully Microsoft clarifies this.

christoph-teichmeister · 2024-03-27T13:50:26Z

I'm on the web version and I still got that message. It may be just a technical mistake by Microsoft.. but this is the requirements page I'm pointed to: requirements and I see a lot of references to unsupported OS. Hopefully Microsoft clarifies this.

But if the fix suggested by ChristoSnake works for this Electron client, shouldn't you be able to just do the same in your browser and you're good to go again? 😄

Microsoft is not necessarily dropping any support for linux, it is "dropping support" for the Teams classic version

jmergy · 2024-03-27T13:53:43Z

confirmed here the debug commands worked. I have multiple organizations in Teams and looks good. Debian 12.5 on XFCE

window.localStorage.setItem("tmp.isOptedIntoT2Web", true)
document.location.href = 'https://teams.microsoft.com/v2/'

misha-grigorov · 2024-03-27T13:59:06Z

I'm on the web version and I still got that message. It may be just a technical mistake by Microsoft.. but this is the requirements page I'm pointed to: requirements and I see a lot of references to unsupported OS. Hopefully Microsoft clarifies this.

But if the fix suggested by ChristoSnake works for this Electron client, shouldn't you be able to just do the same in your browser and you're good to go again? 😄

Microsoft is not necessarily dropping any support for linux, it is "dropping support" for the Teams classic version

Thanks for the idea. I can confirm that the fix works for Linux PWA as well.

ChristoSnake · 2024-03-27T14:17:09Z

I'm on the web version and I still got that message. It may be just a technical mistake by Microsoft.. but this is the requirements page I'm pointed to: requirements and I see a lot of references to unsupported OS. Hopefully Microsoft clarifies this.

It seems that they support Firefox (except WPA) and Chrome/Edge (including WPA):

This extension will do the trick if you really want to run it as a Firefox WPA.

jd-philips · 2024-03-27T14:19:56Z

But if the fix suggested by ChristoSnake works for this Electron client, shouldn't you be able to just do the same in your browser and you're good to go again? 😄

The issue is not whether or not the fix works, the fix should work in the browser though for the web app I'm assuming you load it from ms servers every time (more or less). The issue is: is this a sign that Microsoft is dropping Linux support altogether?

Microsoft is not necessarily dropping any support for linux, it is "dropping support" for the Teams classic version

The requirements page it is pointing me to isn't mentioning Linux or a path forward for me using their web app. It might just be confusing Microsoft language but it's suspicious.

jd-philips · 2024-03-27T14:21:27Z

It seems that they support Firefox (except WPA) and Chrome/Edge (including WPA):

This extension will do the trick if you really want to run it as a Firefox WPA.

where did you see this?

jijojosephk · 2024-03-27T14:23:33Z

Trust the devs here 😄 we'll find something out. The app will not stop. It will have the basic functionality. At least clearing the local storage and start over. The new teams will be loaded. But just like I mentioned you can do the basic things like in the web browser, we'll study the react implementation and fix the broken pieces. Until then relax 👍

aaronfjerstad · 2024-04-03T23:55:44Z

I used this method (shared in various threads here) to force Teams v2.

Right-click the Teams icon in the taskbar, then select the Debug option. Select the Console tab at the top of the debug screen. Type the following in the console at the bottom of the debug screen, then hit Enter:

document.location.href = 'https://teams.microsoft.com/v2/'

If that does not work, follow the same steps but type both of the following commands (with an Enter after each):
window.localStorage.setItem("tmp.isOptedIntoT2Web", true)
document.location.href = 'https://teams.microsoft.com/v2/'
It should automatically load Teams v2 after a restart..

This is a good short-term solution, but doing this causes Teams to silently crash on almost a daily basis.

IsmaelMartinez · 2024-04-04T07:29:56Z

1.4.17 pre-release has this as a config option. Can you open another ticket with the crash information and any steps to reproduce? Ideally with debug logs (from starting the app with --webDebug and whatever you get on the terminal window). Ta

jhoermann · 2024-04-04T08:57:08Z

Thanks @IsmaelMartinez and @mhenselin for the update. So those are the steps to use it with Ubuntu & Snap currently:

Update to the edge channel of the snap with sudo snap refresh teams-for-linux --edge
Set the config option optInTeamsV2 to true by editing the config file ~/snap/teams-for-linux/current/.config/teams-for-linux/config.json with { "optInTeamsV2": true } . For more info see https://github.com/IsmaelMartinez/teams-for-linux/tree/develop/app/config.

araccaine · 2024-04-04T10:05:33Z

Update to the edge channel of the snap with sudo snap refresh teams-for-linux --edge

The Flatpak is still on version 1.4.13. Is it reasonable to wait a few days longer or should I just switch to the snap version? Thx :)

Edit:
Nevermind, I see you are already working on it. Big thank you!
#1174
PR #96

elhennig · 2024-04-04T10:48:02Z

Update to the edge channel of the snap with sudo snap refresh teams-for-linux --edge

The Flatpak is still on version 1.4.13. Is it reasonable to wait a few days longer or should I just switch to the snap version? Thx :)

You could also use the AppImage instead with almost no extra effort to run it (besides +x permissions).

IsmaelMartinez · 2024-04-04T10:51:07Z

for the flathub, see #1151 . We are working on it and it should be released at some point, but is now on the flathub side as they review each release manually.

geckolinux · 2024-04-04T13:48:28Z

Looks like 1.4.16 made it into Flathub:

However just FYI after restarting Teams I'm still getting the warning header described in this issue, and no toggle to switch to v2. I know I can manually switch the Teams URL to v2 in the debug settings, but I'd prefer to stick to the the classic version for now because #1172 is a major issue for my needs. But it looks like there's still a bit of time left, at least for my account, as my IT department has notified us that classic Teams will continue to work through the end of June. Not sure why others have reported that classic Teams stopped working already for them.

SRNissen · 2024-04-05T07:34:26Z

For reference, the problem is (probably) not local to this project

I use teams as a website in plain Chromium* and I get the same banner message (Searching for solutions to use in Chromium is how I found this issue tracker.)

* I'm on Version 123.0.6312.86 (Official Build) (64-bit)

IncandescentChrysalis · 2024-04-05T12:17:51Z

With v1.4.17 I had to specify the added config option to get into v2 again: I was by default reverted to v1, following the quick & dirty fix provided early in this issue

newptcai · 2024-04-08T02:51:18Z

web

I just figured out that for web version you can directly go to https://teams.microsoft.com/v2/
This is the new version and seems to work well in Firefox. 😄

jijojosephk · 2024-04-08T03:29:56Z

web

I just figured out that for web version you can directly go to https://teams.microsoft.com/v2/
This is the new version and seems to work well in Firefox. 😄

Are you using Firefox or this app?

juandavidg890121 · 2024-04-08T11:40:30Z

Thanks @IsmaelMartinez and @mhenselin for the update. So those are the steps to use it with Ubuntu & Snap currently:

Update to the edge channel of the snap with sudo snap refresh teams-for-linux --edge

Set the config option optInTeamsV2 to true by editing the config file ~/snap/teams-for-linux/current/.config/teams-for-linux/config.json with { "optInTeamsV2": true } . For more info see https://github.com/IsmaelMartinez/teams-for-linux/tree/develop/app/config.

what to do if config file ~/snap/teams-for-linux/current/.config/teams-for-linux/config.json does not exist

andreaippo · 2024-04-08T11:47:08Z

Thanks @IsmaelMartinez and @mhenselin for the update. So those are the steps to use it with Ubuntu & Snap currently:

Update to the edge channel of the snap with sudo snap refresh teams-for-linux --edge

Set the config option optInTeamsV2 to true by editing the config file ~/snap/teams-for-linux/current/.config/teams-for-linux/config.json with { "optInTeamsV2": true } . For more info see https://github.com/IsmaelMartinez/teams-for-linux/tree/develop/app/config.

what to do if config file ~/snap/teams-for-linux/current/.config/teams-for-linux/config.json does not exist

I think you can just create it.

That's what I read in some README of the project, IIRC.

geckolinux · 2024-04-08T13:15:31Z

what to do if config file ~/snap/teams-for-linux/current/.config/teams-for-linux/config.json does not exist

I think you can just create it.

Yep, that's what I had to do: #1172 (comment)

newptcai · 2024-04-09T02:26:58Z

web

I just figured out that for web version you can directly go to https://teams.microsoft.com/v2/
This is the new version and seems to work well in Firefox. 😄

Are you using Firefox or this app?

I am using Firefox. For Chromium it does not seem to work. I get redirected to the old version.

IsmaelMartinez · 2024-04-09T09:07:13Z

Hi @newptcai , nice to know but I would appreciate it if we just keep this for the teams-for-linux app, as otherwise it gets really confusing. Thanks again

andreaippo · 2024-04-11T07:18:46Z

Hi, I keep getting the banner proposing to enable the new version, but although I keep doing that, it seems that at each restart the setting is lost, I go back to v1 and see the banner again.

I don't recall having this problem with the previous version (I'm using the flatpak package), where I was just applying the workarounds suggested in the debugger.

Any ideas?

IsmaelMartinez · 2024-04-11T09:04:23Z

I think all versions of this app default to v1 but you can opt in to V2. Just create a config file with the optIn..., useMutation... and url ending in /v2 and let us know if that sorts your problem. Be aware that Flatpack is a bit behind (I don't think the useMutation.. is there yet) and the config file is in another location

…

On Thu, 11 Apr 2024, 08:19 Andrea Ippolito, ***@***.***> wrote: Hi, I keep getting the banner proposing to enable the new version, but although I keep doing that, it seems that at each restart the setting is lost, I go back to v1 and see the banner again. I don't recall having this problem with the previous version (I'm using the flatpak package), where I was just applying the workarounds suggested in the debugger. Any ideas? — Reply to this email directly, view it on GitHub <#1156 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AADJHEEHFUQE4ZSQ5IUP4N3Y4Y2OZAVCNFSM6AAAAABFIUDCHGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANBZGA3DSNZSGM> . You are receiving this because you were mentioned.Message ID: ***@***.***>

andreaippo · 2024-04-11T09:22:15Z

I think all versions of this app default to v1 but you can opt in to V2. Just create a config file with the optIn..., useMutation... and url ending in /v2 and let us know if that sorts your problem. Be aware that Flatpack is a bit behind (I don't think the useMutation.. is there yet) and the config file is in another location
…
On Thu, 11 Apr 2024, 08:19 Andrea Ippolito, @.> wrote: Hi, I keep getting the banner proposing to enable the new version, but although I keep doing that, it seems that at each restart the setting is lost, I go back to v1 and see the banner again. I don't recall having this problem with the previous version (I'm using the flatpak package), where I was just applying the workarounds suggested in the debugger. Any ideas? — Reply to this email directly, view it on GitHub <#1156 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AADJHEEHFUQE4ZSQ5IUP4N3Y4Y2OZAVCNFSM6AAAAABFIUDCHGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANBZGA3DSNZSGM . You are receiving this because you were mentioned.Message ID: @.>

Thanks, my config.json now looks like this, I'll monitor the situation for the V1 banner in the next days:

{
    "followSystemTheme": true,
    "optInTeamsV2": true,
    "url": "https://teams.microsoft.com/v2/"
}

(file path for those interested, at least on opensuse: ~/.var/app/com.github.IsmaelMartinez.teams_for_linux/config/teams-for-linux/)

cl0ne · 2024-04-12T14:51:33Z

web

I just figured out that for web version you can directly go to https://teams.microsoft.com/v2/ This is the new version and seems to work well in Firefox. 😄

didn't work for me without setting
window.localStorage.setItem("tmp.isOptedIntoT2Web", true)

SRNissen · 2024-04-13T12:32:58Z

For reference, the problem is (probably) not local to this project

I use teams as a website in plain Chromium* and I get the same banner message (Searching for solutions to use in Chromium is how I found this issue tracker.)

I'm on Version 123.0.6312.86 (Official Build) (64-bit)

Recently I received a message on logging in.

I didn't think to write it down but it was something like "Your organization is moving to v2 click here to change."

Since then, things have been fine and the banner disappeared (from, again, the chromium website version of teams.)

So this'll be my last message here except: I hope your projects' issue will solve automatically as well.

dxps · 2024-04-16T14:44:08Z

With the current version - at least 1.4.25 - this issue can be closed.
No need for CSS tweaks.

jmcastagnetto · 2024-04-17T19:25:09Z

FYI - the change described in #1156 (comment) is not persistent if you are using the Appimage version, and as of 1.4.27 the workaround is still need to be enter manually, unless you create the file ~/.config/teams-for-linux/config.json (Ubuntu 22.04LTS), using the info from #1156 (comment) which makes it a permanent workaround.

Works for me. Is this is change persistent?

Yes, it is.

Be aware that the taskbar icon will not show a notification count after switching. I'm using KDE's built-in notifications as a workaround:.

jmcastagnetto · 2024-04-17T19:25:47Z

With the current version - at least 1.4.25 - this issue can be closed. No need for CSS tweaks.

On Ubuntu 22.04LTS and using the Appimage for 1.4.27, the workaround mentioned in #1156 (comment) is still needed

Creating the file ~/.config/teams-for-linux/config.json, using the info from #1156 (comment) makes it a permanent workaround.

IsmaelMartinez · 2024-04-18T09:04:37Z

@jmcastagnetto I would also add useMutationTitleLogic to the list of config options if you want to get the number of unread messages in the systray. At some point we will make them the default options, but only once v1 is been fully deprecated (and/or if we sort all the angular to react issues)

{
    "followSystemTheme": true,
    "optInTeamsV2": true,
    "url": "https://teams.microsoft.com/v2/",
    "useMutationTitleLogic": true
}

dtantono · 2024-04-25T12:19:47Z

v1 still available until July 2025. So, there is still lot of time for adjustment
https://learn.microsoft.com/en-us/microsoftteams/teams-classic-client-end-of-availability

jmcastagnetto · 2024-04-25T14:28:00Z

@dtantono Yes, but for some of the colleagues I work with, their institution has already migrated to the new API, and their setup is such that w/o the workaround mentioned here (#1156 (comment)), the Linux client would not be able to edit files in a collaborative manner.

elhennig mentioned this issue Mar 26, 2024

Faulty Calendar View in 1.4.12 (Appimage) and 1.4.10 (flatpak) #1116

Open

IsmaelMartinez mentioned this issue Apr 5, 2024

I'm using v.1.4.19 but Teams asks for browser update and gives a warning #1179

Closed

jijojosephk mentioned this issue Apr 11, 2024

"Your org is switching to the new Teams, and it's ready for you to use" #1189

Closed

IsmaelMartinez mentioned this issue Apr 24, 2024

Teams does not start from time to time #1216

Open

"Classic Teams will soon be unavailable for use" warning header #1156

"Classic Teams will soon be unavailable for use" warning header #1156

Comments

rslagmolen commented Mar 26, 2024

elhennig commented Mar 26, 2024

jbauerrfid commented Mar 26, 2024

bymck commented Mar 26, 2024

ChristoSnake commented Mar 27, 2024

grizewald commented Mar 27, 2024

christoph-teichmeister commented Mar 27, 2024 • edited

elhennig commented Mar 27, 2024

dom976 commented Mar 27, 2024

christoph-teichmeister commented Mar 27, 2024

madzaf commented Mar 27, 2024 • edited

christoph-teichmeister commented Mar 27, 2024

dom976 commented Mar 27, 2024 • edited

mburkeSencon commented Mar 27, 2024

riccardo94p commented Mar 27, 2024

ChristoSnake commented Mar 27, 2024

jbauerrfid commented Mar 27, 2024 • edited

jd-philips commented Mar 27, 2024

Bartwillemsen commented Mar 27, 2024

jd-philips commented Mar 27, 2024

jbauerrfid commented Mar 27, 2024 • edited

antimatter84 commented Mar 27, 2024

jd-philips commented Mar 27, 2024

christoph-teichmeister commented Mar 27, 2024 • edited

jmergy commented Mar 27, 2024

misha-grigorov commented Mar 27, 2024

ChristoSnake commented Mar 27, 2024

jd-philips commented Mar 27, 2024

jd-philips commented Mar 27, 2024

jijojosephk commented Mar 27, 2024

aaronfjerstad commented Apr 3, 2024 • edited

IsmaelMartinez commented Apr 4, 2024

jhoermann commented Apr 4, 2024

araccaine commented Apr 4, 2024 • edited

elhennig commented Apr 4, 2024

IsmaelMartinez commented Apr 4, 2024

geckolinux commented Apr 4, 2024

SRNissen commented Apr 5, 2024 • edited

IncandescentChrysalis commented Apr 5, 2024

newptcai commented Apr 8, 2024

jijojosephk commented Apr 8, 2024

juandavidg890121 commented Apr 8, 2024

andreaippo commented Apr 8, 2024

geckolinux commented Apr 8, 2024

newptcai commented Apr 9, 2024

IsmaelMartinez commented Apr 9, 2024

andreaippo commented Apr 11, 2024

IsmaelMartinez commented Apr 11, 2024 via email

andreaippo commented Apr 11, 2024

cl0ne commented Apr 12, 2024

SRNissen commented Apr 13, 2024

dxps commented Apr 16, 2024 • edited

jmcastagnetto commented Apr 17, 2024 • edited

jmcastagnetto commented Apr 17, 2024 • edited

IsmaelMartinez commented Apr 18, 2024 • edited

dtantono commented Apr 25, 2024

jmcastagnetto commented Apr 25, 2024

christoph-teichmeister commented Mar 27, 2024 •

edited

madzaf commented Mar 27, 2024 •

edited

dom976 commented Mar 27, 2024 •

edited

jbauerrfid commented Mar 27, 2024 •

edited

jbauerrfid commented Mar 27, 2024 •

edited

christoph-teichmeister commented Mar 27, 2024 •

edited

aaronfjerstad commented Apr 3, 2024 •

edited

araccaine commented Apr 4, 2024 •

edited

SRNissen commented Apr 5, 2024 •

edited

dxps commented Apr 16, 2024 •

edited

jmcastagnetto commented Apr 17, 2024 •

edited

jmcastagnetto commented Apr 17, 2024 •

edited

IsmaelMartinez commented Apr 18, 2024 •

edited