Unable to skip login page #5444

kallisti5 · 2022-05-25T13:37:13Z

Describe the bug
Suddenly unable to skip the login page.

To Reproduce
Steps to reproduce the behavior:

Open application

Expected behavior
Able to skip. I can't even close the window given the lack of a close button 👎

Workaround
Use OpenLens found here: https://github.com/MuhammedKalkan/OpenLens

Screenshots

Environment (please complete the following information):

Lens Version: Lens-5.4.6-latest.20220428.1.x86_64
OS: Linux
Installation method (e.g. snap or AppImage in Linux): AppImage

alex-berger · 2022-05-25T13:44:58Z

Same problem here.

kallisti5 · 2022-05-25T13:47:07Z

Here's a workaround. Add the following to your /etc/hosts file:

127.0.0.1       app.k8slens.dev

That will break the login page, and let you click the skip button in Lens 5.4.x

Lens 5.4, last known version to allow skipping login page with hack above:
https://gateway.pinata.cloud/ipfs/QmVVpMtbecfsyofgKZ2buHM7Xd6Shcr6HFJWNciRLeMPVx

davidspek · 2022-05-25T13:50:29Z

@kallisti5 Thanks for the workaround. After getting past the login page with your workaround and then configuring lens to not show the login page, I could remove the entry in my /etc/hosts file and no login screen is showed.

Guess it will only be a matter of time before the option to disable the login page is removed as well.

PeteH-SeriouslyRAD · 2022-05-25T13:51:07Z

Here's a workaround. Add the following to your /etc/hosts file:
127.0.0.1       app.k8slens.dev
That will break the login page, and let you click the skip button.

I'm afraid this doesn't work, you get this error screen with no way to skip or close, only retry:

kallisti5 · 2022-05-25T13:52:16Z

Oof. Maybe it only works for the older 5.4 version.

Lens developers, hear me. You are accepting pull requests for your project.

The community is helping develop the application... going anti-user like this is a huge mistake if it's on purpose.

EDIT. It's on purpose, confirmed via Tweet. Take a look at k9s, kubenav, or octant for alternatives.

npasken · 2022-05-25T13:57:03Z

As someone who tested the latest beta, this was not present and I don't see any issue referenced that should have caused this. Maybe we give them a chance to respond before assuming? I too am disappointed the release version seems to force me to be stuck at this screen, but I have to believe this was not their intent.

kallisti5 · 2022-05-25T14:02:28Z

@npasken that's fair, I updated my comment to include "if it's on purpose" :-)

npasken · 2022-05-25T14:06:06Z

We do need a better way to fall back to the prior version we were using when things like this happen.
@nevalla @Nokel81 @jim-docker - users who updated today with prompt are unable to use Lens.
I found the last beta I was using: https://api.k8slens.dev/binaries/Lens%20Setup%205.5.0-beta.2.20220520.2.exe and without any modification to hosts file, am back up and running.

PeteH-SeriouslyRAD · 2022-05-25T14:15:33Z

Oof. Maybe it only works for the older 5.4 version.

Lens developers, hear me. You are accepting pull requests for your project.

The community is helping develop the application... going anti-user like this is a huge mistake if it's on purpose.

Ok I found an old 5.4 windows installer still available (grab it while it's there! https://api.k8slens.dev/binaries/Lens%20Setup%205.4.6-latest.20220421.1.exe). I've installed this version with the hosts file modification in place, and been able get past the login.

bpd1069 · 2022-05-25T14:30:10Z

Can I skip the Lens Spaces login dialog on the application start-up?
Yes, you can. Click the Skip button in the lower-right corner of the dialog. You can also disable the login dialog. See Preferences for details.

Where is the skip button?

b2un0 · 2022-05-25T14:31:42Z

macOS:
M1: https://api.k8slens.dev/binaries/Lens-5.4.6-latest.20220428.1-arm64.dmg
Intel: https://api.k8slens.dev/binaries/Lens-5.4.6-latest.20220428.1.dmg

source: https://github.com/Homebrew/homebrew-cask/blob/HEAD/Casks/lens.rb

harryjms · 2022-05-25T14:49:26Z

Seems it is intentional https://twitter.com/k8slens/status/1529470612380344321?s=21&t=yvydstNYJkrBPcKI_PTrwQ

rlex · 2022-05-25T14:49:34Z

I had login page disabled in settings and looks like it was forcefully disabled after update. Now i'm getting kicked to login page with no ability to skip it.

jhoelzel · 2022-05-25T14:54:29Z

I believe, that the twitter post and the "you are not online, you cant use lens" screen confirm that, with the new version, a lens ID is in fact required.

zerowebcorp · 2022-05-25T15:05:20Z

Next twitter announcement would say we are taking lens out of github and starting to charge users $$ for license fee.

kallisti5 · 2022-05-25T15:05:58Z

Yeah.. it feels like it's time to fork Lens. Any nodejs developers interested?

npasken · 2022-05-25T15:07:42Z

Kinda sad - the login screen doesn't even work for me. It just spins and spins...

kallisti5 · 2022-05-25T15:08:12Z

https://www.boatsafe.com/boating-glossary-terms/ Fun nautical terms for a fork rebrand 😆

opsydev · 2022-05-25T15:26:43Z

Just adding to the voices, this is leading to an immediate removal of lens from my system.

taz77 · 2022-05-25T15:30:35Z

Yup bad move. The reasons are not justified IMHO what does me making an account have anything to do with collaboration, I work alone.

d3clan · 2022-05-25T15:45:28Z

Rendered completely useless. Tried logging in with Github, I get a "Invalid credentials" against the cluster. Registered a new account, same "Invalid credentials" error. What a shame. I use Lens to do my work. I guess it's back to kubectl for me.

lenalebt · 2022-05-25T15:50:51Z

Having a look for alternatives, I found https://github.com/vmware-tanzu/octant (through https://twitter.com/disconn3ct/status/1529487362828509184) - not yet into the details and unsure whether it's a good replacement, but I think it should be somewhere here that anyone can find it to try.

rlex · 2022-05-25T15:52:09Z

k9s is another good option, if you're OK with cli interface https://github.com/derailed/k9s

HighWatersDev · 2022-05-25T15:52:47Z

Here's another option which is pretty good: https://kubenav.io/

PhilippKuntschik · 2022-05-25T15:53:31Z

why can't we just fork the Lens repository?

0dragosh · 2022-05-25T15:54:50Z

It's getting SaaSified, the writing's been on the wall a while now.

I recommend the k9s alternative for anyone looking for a similar product.

kallisti5 · 2022-05-25T15:58:06Z

why can't we just fork the Lens repository?

We definitely can.. however we need someone well versed in nodejs to step up to maintaining it. It's probably a moderate project to maintain, but whomever did would have a lot of support via pull requests and community contribution.

I jokingly forked it, but pretty quickly realized there are a bunch of weird node requirements (really old nodejs 14.x, etc) to even build it. You would think the developers would be more focused on maintaining the app instead of just trying to turn it into a profit center... but here we are.

Hell, if someone steps up and maintains it without a login page and the SaaS crap, i'd gladly donate $5 - $10 a month.

Here's another option which is pretty good: https://kubenav.io/

I just installed it and gave it a try. Definitely a solid competitor (and it's written in go which is nice). The UI definitely needs some work though, and the "open a quick shell in a pod" feature is missing.

respectTheCode · 2022-05-25T16:25:24Z

Based on this I have uninstalled and looks like Octant is a better fit for me anyways.

disconn3ct · 2022-08-05T12:38:20Z

Git cloning means never having to say "omg where did that repo go?" Count me as a vote for @MuhammedKalkan's existing solution using official upstream source. It also keeps Mirantis honest; if they break builds, they can't claim it is a result of the fork.

Forking can come when it is needed, not just because you want your name on it..

Anticom · 2022-08-05T12:45:15Z

Also IMHO it's super annoying to now having to coup with multiple forks that are available via brew taps etc. Although everyone is of course free to fork the repo for themselves and do whatever the heck they please with it (as long as it doesn't violate the license), I don't think it's maximizing productivity in our efforts to obtain a well-maintained offshoot.

I'm not the one to decide it but from what I've read in this discussion so far OpenLens by @MuhammedKalkan seems to be the most popular fork right now. So maybe if this suggestion get enough votes @kallisti5 could consider adding a reference to OpenLens in his initial issue description to avoid even more forks popping out of the ground adding to the mess.

kallisti5 · 2022-08-05T13:15:42Z

@Anticom done

WolfspiritM · 2022-10-02T02:38:17Z

@jakolehm

I would like to also clear some misunderstandings in the comments. This repository is for OpenLens which is open source and is under very permissive MIT license (this is also mentioned in the repository README.md). Lens IDE (Lens Desktop) is the binary distribution which is built upon on OpenLens. It's not a fork.

And now the confusion is complete. Good job from the people who maintain this project and don't even care about this issue here. v6.1.1 has been released a few days ago by @Nokel81 and it DOES contain a binary release on the Release page of this repository. I thought FINALLY this has been resolved by creating releases from this repository but I ended up looking on a login screen after installation. This binary release is NOT Openlens but the mentioned distribution. This is another step in the wrong and bad direction by releasing a binary release in THIS repository which is not build by the actual sourcecode of this repository but by adding proprietary stuff to it. I actually thought about creating a Lens ID before all of that happened however now I'm NEVER going to create a lens id and I'm telling everyone to stop using Lens and move to a third party distribution of OpenLens cause of that. This is still the worst decision I've ever seen from an opensource project.

jskrzypek · 2022-10-02T02:48:29Z

Honestly, I gave up on the whole thing and just switched to www.k9scli.io which provides everything I need and nothing I don't want and never will

…

On Sat, Oct 1, 2022, 22:38 Adrian ***@***.***> wrote: @jakolehm <https://github.com/jakolehm> I would like to also clear some misunderstandings in the comments. This repository is for OpenLens which *is* open source and is under very permissive MIT license (this is also mentioned in the repository README.md <https://github.com/lensapp/lens#the-repository>). Lens IDE (Lens Desktop) is the binary distribution which is built upon on OpenLens. It's not a fork. And now the confusion is complete. Good job from the people who maintain this project and don't even care about this issue here. v6.1.1 has been released a few days ago by @Nokel81 <https://github.com/Nokel81> and it DOES contain a binary release on the Release page of this repository. I thought FINALLY this has been resolved by creating releases from this repository but I ended up looking on a login screen. This binary release is NOT Openlens but the mentioned distribution. This is another step in the wrong and bad direction by releasing a binary release in THIS repository which is not build by the actual sourcecode of this repository but by adding proprietary stuff to it. I actually thought about creating a Lens ID before all of that happened however now I'm NEVER going to create a lens id and I'm telling everyone to stop using Lens and move to a third party distribution of OpenLens cause of that. This is still the worst decision I've ever seen from an opensource project. — Reply to this email directly, view it on GitHub <#5444 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AALROMK3R25DWB2OEV4IB3TWBDYSRANCNFSM5W5FJMYQ> . You are receiving this because you commented.Message ID: ***@***.***>

zerowebcorp · 2022-10-13T14:19:18Z

Hello,
I was able to build lens using windows + git bash for previous versions, but the newer versions are not building the .exe file. It builds the linux binaries just fine. Also anybody having luck in integrating this with their Azure DevOps pipeline for automated building?

dcole-gsn · 2022-10-24T11:06:04Z

Hi,
Apprecaite all the work people have been doing to support OpenLens. Please correct me if I'm posting in the wrong location, but I've tried using both OpenLens and LibreLens on Windows and get the same error

F1024 11:58:03.241094 4252 main.go:82] failed to initialize proxyunable to load root certificates: unable to parse bytes as PEM block
goroutine 1 [running]:
k8s.io/klog/v2.stacks(0x1)
C:/Users/runneradmin/go/pkg/mod/k8s.io/klog/[email protected]/klog.go:1140 +0x8a
k8s.io/klog/v2.(*loggingT).output(0x2345140, 0x3, 0x0, 0xc0001ebab0, 0x1, {0x1b1c0b5, 0x20}, 0x2346020, 0x0)
C:/Users/runneradmin/go/pkg/mod/k8s.io/klog/[email protected]/klog.go:1088 +0x66f
k8s.io/klog/v2.(*loggingT).printDepth(0xc00059e901, 0x0, 0x0, {0x0, 0x0}, 0x0, {0xc000404440, 0x2, 0x2})
C:/Users/runneradmin/go/pkg/mod/k8s.io/klog/[email protected]/klog.go:735 +0x1ae
k8s.io/klog/v2.(*loggingT).print(...)
C:/Users/runneradmin/go/pkg/mod/k8s.io/klog/[email protected]/klog.go:717
k8s.io/klog/v2.Fatal(...)
C:/Users/runneradmin/go/pkg/mod/k8s.io/klog/[email protected]/klog.go:1622
main.main()
D:/a/lens-k8s-proxy/lens-k8s-proxy/main.go:82 +0x7cc

goroutine 19 [chan receive]:
k8s.io/klog/v2.(*loggingT).flushDaemon(0x0)
C:/Users/runneradmin/go/pkg/mod/k8s.io/klog/[email protected]/klog.go:1283 +0x6a
created by k8s.io/klog/v2.init.0
C:/Users/runneradmin/go/pkg/mod/k8s.io/klog/[email protected]/klog.go:420 +0xfb

goroutine 10 [syscall]:
os/signal.signal_recv()
C:/hostedtoolcache/windows/go/1.17.8/x64/src/runtime/sigqueue.go:169 +0x98
os/signal.loop()
C:/hostedtoolcache/windows/go/1.17.8/x64/src/os/signal/signal_unix.go:24 +0x19
created by os/signal.Notify.func1.1
C:/hostedtoolcache/windows/go/1.17.8/x64/src/os/signal/signal.go:151 +0x2c

proxy exited with code: 255

Failed to start connection: Error: failed to retrieve port from stream

Failed to start connection: Error: failed to retrieve port from stream

I've tried compiling the Windows locally and encounters the same error. However when I use lens it doesn't encounter the same error. Please forgive if I'm being silly.

If anyone has any suggestions on what I could try to resolve it, I would appreciate it.
Kind regards.

paulius-valiunas · 2022-10-24T11:07:57Z

Hi, Apprecaite all the work people have been doing to support OpenLens. Please correct me if I'm posting in the wrong location, but I've tried using both OpenLens and LibreLens on Windows and get the same error

F1024 11:58:03.241094 4252 main.go:82] failed to initialize proxyunable to load root certificates: unable to parse bytes as PEM block
goroutine 1 [running]:
k8s.io/klog/v2.stacks(0x1)
C:/Users/runneradmin/go/pkg/mod/k8s.io/klog/[email protected]/klog.go:1140 +0x8a
k8s.io/klog/v2.(*loggingT).output(0x2345140, 0x3, 0x0, 0xc0001ebab0, 0x1, {0x1b1c0b5, 0x20}, 0x2346020, 0x0)
C:/Users/runneradmin/go/pkg/mod/k8s.io/klog/[email protected]/klog.go:1088 +0x66f
k8s.io/klog/v2.(*loggingT).printDepth(0xc00059e901, 0x0, 0x0, {0x0, 0x0}, 0x0, {0xc000404440, 0x2, 0x2})
C:/Users/runneradmin/go/pkg/mod/k8s.io/klog/[email protected]/klog.go:735 +0x1ae
k8s.io/klog/v2.(*loggingT).print(...)
C:/Users/runneradmin/go/pkg/mod/k8s.io/klog/[email protected]/klog.go:717
k8s.io/klog/v2.Fatal(...)
C:/Users/runneradmin/go/pkg/mod/k8s.io/klog/[email protected]/klog.go:1622
main.main()
D:/a/lens-k8s-proxy/lens-k8s-proxy/main.go:82 +0x7cc

goroutine 19 [chan receive]:
k8s.io/klog/v2.(*loggingT).flushDaemon(0x0)
C:/Users/runneradmin/go/pkg/mod/k8s.io/klog/[email protected]/klog.go:1283 +0x6a
created by k8s.io/klog/v2.init.0
C:/Users/runneradmin/go/pkg/mod/k8s.io/klog/[email protected]/klog.go:420 +0xfb

goroutine 10 [syscall]:
os/signal.signal_recv()
C:/hostedtoolcache/windows/go/1.17.8/x64/src/runtime/sigqueue.go:169 +0x98
os/signal.loop()
C:/hostedtoolcache/windows/go/1.17.8/x64/src/os/signal/signal_unix.go:24 +0x19
created by os/signal.Notify.func1.1
C:/hostedtoolcache/windows/go/1.17.8/x64/src/os/signal/signal.go:151 +0x2c

proxy exited with code: 255

Failed to start connection: Error: failed to retrieve port from stream

Failed to start connection: Error: failed to retrieve port from stream

I've tried compiling the Windows locally and encounters the same error. However when I use lens it doesn't encounter the same error. Please forgive if I'm being silly.

If anyone has any suggestions on what I could try to resolve it, I would appreciate it. Kind regards.

this is unrelated to skipping the login page, please open a new issue...

jslay88 · 2022-11-05T03:23:39Z

Hello, I was able to build lens using windows + git bash for previous versions, but the newer versions are not building the .exe file. It builds the linux binaries just fine. Also anybody having luck in integrating this with their Azure DevOps pipeline for automated building?

Still works fine for me

curl -o- https://gist.githubusercontent.com/jslay88/bf654c23eaaaed443bb8e8b41d02b2a9/raw/install_openlens.sh | bash

kellen-miller · 2022-11-14T21:30:16Z

For macOS, pretty easy to install OpenLens via Homebrew.

brew install --cask openlens

The OpenLens cask is already registered in Homebrews repo and points to @MuhammedKalkan's repo.

I created an issue MuhammedKalkan/OpenLens#53 with an updated the readme pasted in there with the install command. Also will add clarifications around the difference between OpenLens vs Lens IDE since the difference is confusing.

Side note
Might be good to create a mirror repo at https://github.com/MuhammedKalkan/homebrew-OpenLens to follow the Homebrews preferred way of creating taps . Can then just call brew tap MuhammedKalkan/OpenLens without specifying the url.

edit: updated cask and homebrew command, thanks! @siko1056 @marafa-sugarcrm

siko1056 · 2022-11-15T00:56:10Z

Many thanks for all the efforts about OpenLens. In addition to @kellen-miller, I could install OpenLens by just typing:

brew install openlens

Without calling brew tab. Maybe the necessary steps were already performed: https://formulae.brew.sh/cask/openlens in any way many thanks!

vijaya-lakshmi-venkatraman · 2023-01-18T12:21:21Z

HI
A newbie to OpenLens here.

@jakolehm

I would like to also clear some misunderstandings in the comments. This repository is for OpenLens which is open source and is under very permissive MIT license (this is also mentioned in the repository README.md). Lens IDE (Lens Desktop) is the binary distribution which is built upon on OpenLens. It's not a fork.

And now the confusion is complete. Good job from the people who maintain this project and don't even care about this issue here. v6.1.1 has been released a few days ago by @Nokel81 and it DOES contain a binary release on the Release page of this repository. I thought FINALLY this has been resolved by creating releases from this repository but I ended up looking on a login screen after installation. This binary release is NOT Openlens but the mentioned distribution. This is another step in the wrong and bad direction by releasing a binary release in THIS repository which is not build by the actual sourcecode of this repository but by adding proprietary stuff to it. I actually thought about creating a Lens ID before all of that happened however now I'm NEVER going to create a lens id and I'm telling everyone to stop using Lens and move to a third party distribution of OpenLens cause of that. This is still the worst decision I've ever seen from an opensource project.

Is the latest version of OpenLens having the login screen issue?

paulius-valiunas · 2023-01-18T12:26:55Z

@vijaya-lakshmi-venkatraman Lens (the commercial distribution) has this issue and it will never be fixed. OpenLens (the open source code and binaries) never had this issue and hopefully never will. The confusion comes from the fact that the binaries uploaded in the releases page of this repository are Lens, whereas the code is for OpenLens. So to get OpenLens you have to either build it yourself or use the automated builds by @MuhammedKalkan: https://github.com/MuhammedKalkan/OpenLens/releases

vijaya-lakshmi-venkatraman · 2023-01-19T03:32:37Z

Thanks @paulius-valiunas
So, the binaries in OpenLens do not force login upon launching the exe.
Is that right?

dragonfly-net · 2024-01-12T02:49:43Z

We do need a better way to fall back to the prior version we were using when things like this happen. @nevalla @Nokel81 @jim-docker - users who updated today with prompt are unable to use Lens. I found the last beta I was using: https://api.k8slens.dev/binaries/Lens%20Setup%205.5.0-beta.2.20220520.2.exe and without any modification to hosts file, am back up and running.

404...

jhoelzel · 2024-01-12T09:02:50Z

mirantis is no longer maintaining this repository. henceforth lens and open lens are basically dead.

(lens is now only closed source available and im not using my kubeconfig with that)

alernatives are:

headlamp https://github.com/headlamp-k8s/headlamp
?

Laurens-W · 2024-01-12T09:49:58Z

@jhoelzel What makes you say mirantis is no longer maintaining this repository?

tranvansang · 2024-01-12T09:53:20Z

Fyi

https://transang.me/how-to-install-latest-open-sourced-lens-bypassing-login-requirement/

horihel · 2024-01-12T10:08:38Z

@Laurens-W - last commit to this repo was 5 months ago.

jerch · 2024-01-12T13:27:04Z

Oh they finally did it. No one could have seen this coming. 🙈 And thx to the naysayers we dont have a working fork.

Time to move on, nothing to see here anymore.

kallisti5 · 2024-01-12T14:03:42Z

I mean... technically someone could manage a fork still. The code still exists under an open source license.

Mantis will bumble off into closed-software paid irrelevance... most of us saw this coming as soon as that login page appeared in 2022.

jerch · 2024-01-12T14:47:57Z

I mean... technically someone could manage a fork still. The code still exists under an open source license.

True, the issue is more about having a working team actually maintaining it. k8s is very fast paced, without proper maintenance the lens code is likely get outdated very fast.

mnorrsken · 2024-01-12T16:28:52Z

Sad news that openlens is abandoned. I tried the closed source lens and apart from constantly trying to get you to sign up for a subscription, they also jumbled up the UI making it less user friendly.

kallisti5 · 2024-05-09T19:23:41Z

I'm going ahead and closing this one. Lens is no longer interesting or relevant now that it is closed source. I regret the time I spent contributing to it and the Lens ecosystem.

Here's a list of other great open source applications to interactively manage Kubernetes clusters:

k9s, kdash, Headlamp or Seabird.

Highly recommend investing your energy and time into learning one of those awesome open source projects (and donating to them!)

kallisti5 added the bug Something isn't working label May 25, 2022

andrew-vdb mentioned this issue May 25, 2022

Why make lens id mandatory? #5443

Closed

smoyer64 mentioned this issue Aug 5, 2022

Replace Kubernetes Lens with an OSS alternative selesy/workstation#343

Closed

2 tasks

alebcay mentioned this issue Aug 7, 2022

No installation instructions for openlens #5972

Open

carlreid mentioned this issue Sep 6, 2022

[Request] OpenLens ScoopInstaller/Extras#9177

Closed

2 tasks

kellen-miller mentioned this issue Nov 14, 2022

README Update MuhammedKalkan/OpenLens#53

Closed

Technetium1 mentioned this issue Apr 6, 2024

[Remove] lens chaotic-aur/packages#1673

Closed

4 tasks

kallisti5 closed this as completed May 9, 2024

Unable to skip login page #5444

Unable to skip login page #5444

Comments

kallisti5 commented May 25, 2022 • edited Loading

alex-berger commented May 25, 2022

kallisti5 commented May 25, 2022 • edited Loading

davidspek commented May 25, 2022

PeteH-SeriouslyRAD commented May 25, 2022

kallisti5 commented May 25, 2022 • edited Loading

npasken commented May 25, 2022

kallisti5 commented May 25, 2022

npasken commented May 25, 2022 • edited Loading

PeteH-SeriouslyRAD commented May 25, 2022

bpd1069 commented May 25, 2022

b2un0 commented May 25, 2022 • edited Loading

harryjms commented May 25, 2022

rlex commented May 25, 2022

jhoelzel commented May 25, 2022 • edited Loading

zerowebcorp commented May 25, 2022 • edited Loading

kallisti5 commented May 25, 2022

npasken commented May 25, 2022

kallisti5 commented May 25, 2022

opsydev commented May 25, 2022

taz77 commented May 25, 2022

d3clan commented May 25, 2022

lenalebt commented May 25, 2022

rlex commented May 25, 2022

HighWatersDev commented May 25, 2022

PhilippKuntschik commented May 25, 2022

0dragosh commented May 25, 2022

kallisti5 commented May 25, 2022 • edited Loading

respectTheCode commented May 25, 2022

disconn3ct commented Aug 5, 2022

Anticom commented Aug 5, 2022

kallisti5 commented Aug 5, 2022

WolfspiritM commented Oct 2, 2022 • edited Loading

jskrzypek commented Oct 2, 2022 via email

zerowebcorp commented Oct 13, 2022

dcole-gsn commented Oct 24, 2022 • edited Loading

paulius-valiunas commented Oct 24, 2022

jslay88 commented Nov 5, 2022

kellen-miller commented Nov 14, 2022 • edited Loading

siko1056 commented Nov 15, 2022 • edited Loading

vijaya-lakshmi-venkatraman commented Jan 18, 2023

paulius-valiunas commented Jan 18, 2023

vijaya-lakshmi-venkatraman commented Jan 19, 2023 • edited Loading

dragonfly-net commented Jan 12, 2024

jhoelzel commented Jan 12, 2024 • edited Loading

Laurens-W commented Jan 12, 2024

tranvansang commented Jan 12, 2024

horihel commented Jan 12, 2024

jerch commented Jan 12, 2024

kallisti5 commented Jan 12, 2024

jerch commented Jan 12, 2024

mnorrsken commented Jan 12, 2024

kallisti5 commented May 9, 2024

kallisti5 commented May 25, 2022 •

edited

Loading

kallisti5 commented May 25, 2022 •

edited

Loading

kallisti5 commented May 25, 2022 •

edited

Loading

npasken commented May 25, 2022 •

edited

Loading

b2un0 commented May 25, 2022 •

edited

Loading

jhoelzel commented May 25, 2022 •

edited

Loading

zerowebcorp commented May 25, 2022 •

edited

Loading

kallisti5 commented May 25, 2022 •

edited

Loading

WolfspiritM commented Oct 2, 2022 •

edited

Loading

dcole-gsn commented Oct 24, 2022 •

edited

Loading

kellen-miller commented Nov 14, 2022 •

edited

Loading

siko1056 commented Nov 15, 2022 •

edited

Loading

vijaya-lakshmi-venkatraman commented Jan 19, 2023 •

edited

Loading

jhoelzel commented Jan 12, 2024 •

edited

Loading