default shield-on option lost since a recent update #23214

fche · 2022-06-02T17:30:48Z

Description

In versions prior to an update ~2-3 weeks ago (unknown exactly where this broke), my former default-shields-up setting (orange lion) has been broken. Now, new websites default to shields-down (grey lion), and I can't find a setting to turn it back on. This makes my browsing less secure than it was and than it should be.

Brave version (brave://version info)

brave-browser-1.39.111-1.x86_64 (fedora 35)

Brave 1.38.119 Chromium: 101.0.4951.67 (Official Build) (64-bit)
Revision 8888ee7a24e2c36661ddb9536c35b7d4852a3a98-refs/branch-heads/4951@{#1230}
OS Linux

rebron · 2022-06-03T17:48:59Z

@fche Shields is on by default for all sites and there's no global setting to turn it off on new sites. We do have shields disabled on internal pages like the new tab page and settings. Sounds like you're saying every site you visit has Brave Shields off by default though?

fche · 2022-06-03T17:56:23Z

Yup, that's right, it's off by default on any new site I visit.
I can flick it on, and it stays on for future visits.
I wonder if some brave configuration item got messed up after many years of use & upgrading?

rebron · 2022-06-03T18:48:11Z

We were thinking it was just a UI issue where the icon was greyed out but Shields is still on so an issue with front end icon. But sounds like truly having Shields turned off for all new sites you visit.

fche · 2022-06-03T18:54:46Z

Yup, it is truly off (javascript crap works, even though global defaults are to block), etc.

fche · 2022-06-03T18:58:49Z

A possibly related phenomenon: my brave://settings has become very short indeed:

rebron · 2022-06-03T19:09:09Z

@fche That one above is an issue with minimum window, we're working on addressing it. If you expand window size, should see the rest of settings.

MadhaviSeelam · 2022-06-04T00:42:54Z

I couldn't reproduce the above issue for fresh install and upgrade profile. Shields toggle ON and OFF behavior works as expected in Win 11x64 and Ubuntu.

Tested on Win 11x64 as below:

Installed 1.38.119 Chromium 101.0.4951.67 and then upgraded to 1.39.111 Chromium: 102.0.5005.61 and both the versions have V2 Shields

Install 1.38.119 Chromium 101.0.4951.67
Launch brave
open few websites (CNN.com, BBC.com, theguardian.com)
Verified all three websites opened with default Shields ON
Toggle OFF for one of the sites (theguardian.com)
Close and relaunch the browser
CNN and BBC sites Shields setting correctly shows 'ON"
Guardian site Shield displayed 'OFF'
Upgrade to 1.39.111 Chromium: 102.0.5005.61
All 3 tabs are preserved
Shields icon is 'ON' for CNN and BBC sites
Shields icon is 'OFF' for Guardian
Open two more new sites brave.com or nyimes.com and the toggle is 'ON`

Couldn't reproduce the issue with fresh install of 1.39.111.

Tested upgrading V1 Shields>>V2 Shields with same above steps

Upgrade from 1.37.116 Chromium: 100.0.4896.127 to 1.39.111 Chromium: 102.0.5005.61
Results were same as above

fche · 2022-06-04T00:44:39Z

Thanks! I wouldn't be surprised if it were some sort of corruption in my local settings, but have no idea where to look. ISTR shield default-on vs. default-off being a user selected option a while ago, but can't find that now. Maybe some configuration migration broke it?

ziggiesandvik · 2022-06-11T17:52:35Z

I'm having the same issue - I tried clearing "Site and Shields Settings" but that did not help.

1.39.122 Chromium: 102.0.5005.115 (Official Build) (x86_64)
--
Revision | 174dbe6e33bc81994fceb71d751be201d0b4803d-refs/branch-heads/5005_109@{#3}
OS | macOS Version 12.3.1 (Build 21E258)

alexandrpunk · 2022-06-13T16:52:05Z

I have the same issue
`

Brave	1.39.122 Chromium: 102.0.5005.115 (Build oficial) (64 bits)
Revisión	174dbe6e33bc81994fceb71d751be201d0b4803d-refs/branch-heads/5005_109@{#3}
Sistema operativo	Linux

`

Werve · 2022-06-17T10:42:39Z

I think this problem is linked with #23113

gpowers01 · 2022-06-20T15:53:40Z

I'm having the same problem. Shields are down unless I manually enable them on each site I visit - then the setting persists. How does one fix this issue? This issue seems to have surfaced in the past few weeks. Currently on Release Notes V1.39.122 (June 10th, 2022), which is the latest update. Do I need to somehow reset my local settings?

UPDATE: I first disabled sync in the Brave browser, completely uninstalled Brave checking the option to clear the local browsing history (Windows 10 Pro fully updated) and then downloaded an reinstalled Brave. I then re-enabled the sync. Now shields seem to be up by default for everything.

leotm · 2022-06-21T12:56:00Z

if you want to avoid re-installing, this did the trick for me

Brave randomly turning off shield for random websites #23113 (comment)

fche · 2022-06-21T13:11:29Z

(Clearing shields/sites settings did not work for me.)

leotm · 2022-06-21T13:31:38Z

gotcha, i wonder if a reinstall on 1.39.122 works for you too (then re-sync) as a temp workaround

fche · 2022-06-22T12:45:16Z

Another odd observation: on my linux/fedora brave installation, since the default-shield breakage, it often happens that visiting a new site HANGS with the lion-greyed, just waits while loading. If during this time, I turn the shields on via the lion icon, the site load completes right away.

FWIW, on this browser, I also run a copy of ublock-origin.

dacioAlvira · 2022-06-25T01:17:04Z

Same issue with Windows 11

r-erd · 2022-06-25T15:03:29Z

I had the same issue on MacOS Monterey 12.4 and my Android phone using Brave (synced).
I managed to fix it by leaving the sync chain and deleting the site and shield settings.
I also often had the issue of websites loading very slowly / hanging with the grey lion, which doesnt seem to happen anymore.

I also run ublock-origin in the same browser.

Tested it with random websites from google search results.

eduncan911 · 2022-06-29T19:55:40Z

Version 1.39.122 Chromium: 102.0.5005.115 (Official Build) (64-bit)

Exact same issue for days as OP. I thought it was an extension and removed all - nope.
All shields is off / ads show up! Manually enabling shields hides the ads on pages.
There was nothing to "clear" in Shields, as suggested above.
Ubuntu 21.10

kjozwiak · 2022-07-10T00:49:45Z

The above will require 1.41.95 or higher for 1.41.x verification.

eduncan911 · 2022-07-10T14:39:50Z

It would be nice to know what exactly "broke" with the last update of Brave. I have never, not once, entered anything into the Shields Down manually: including no "wildcards" that this commit seems to have addressed as a "fix." Did wildcards somehow get automatically added, and break? Ok, that makes sense - but how did that happen?

As a follow-up to my "Confirmation" post above where I had the same issue, I was able to resolve my issue with the instructions below - even though at first I had "nothing to clear."

It's the subtle but key dropdown menu on that Advanced tab, at the very top that SCROLLS AWAY when you SCROLL DOWN to look for and select "Sites and Shields Settings."

You must SCROLL BACK UP that checkbox list, and change the Time range DropDownList to All Time to get all the sites to show up. Then I had a list of 100+ sites that needed to be "cleared."

Most concerning though: Why do I have an exception list of over 100 sites? That seems, unusually high when I barely ever disable a shield. And when I do disable shields, it's briefly until I flip it back on as it didn't fix the site.

This was not in any of the directions or suggested fixes.

bridiver · 2022-07-10T15:12:41Z

Most concerning though: Why do I have an exception list of over 100 sites? That seems, unusually high when I barely ever disable a shield. And when I do disable shields, it's briefly until I flip it back on as it didn't fix the site.

Toggling a shields value back to the original does not unset it, it just changes the value of the override. This is a long-standing issue I've wanted addressed and I believe @petemill is working on a change to differentiate between changing the override and unsetting it.

As far as the actual cause, we don't know how this is happening so we added some debugging to give us more information to help track it down. Fortunately because there should never be a wildcard value for shields this was easy to address without knowing the root cause.

GeetaSarvadnya · 2022-07-11T15:43:24Z

Verification PASSED on


Brave | 1.41.95 Chromium: 103.0.5060.114 (Official Build) (64-bit)
-- | --
Revision | a1c2360c5b02a6d4d6ab33796ad8a268a6128226-refs/branch-heads/5060@{#1124}
OS | Windows 10 Version 21H2 (Build 19044.1766)

Verified the test plan from Do not allow wildcard content settings entries for "shields enabled" brave-core#14031
Added the testing notes default shield-on option lost #23988 (comment)

Additional testing

Case 1: Install 1.37.x with bunch of sites with shields ON/OFF, extensions installed and rewards and sync enabled and then upgrade to 1.41.96_PASSED

Clean profile 1.37.x
Visited several sites and modified shield configurations (some up, some down, some with various changes to individual settings like Aggressively Block Ads, Aggressively Block Fingerprinting, etc)
Enable brave rewards
Establish sync between devices and import bookmarks
Install a few extensions
Upgrade the profile to 1.41.96
Confirmed shield settings are retained for the opened sites in 1.41.96

Case 1.1: Install 1.37.x with few sites opened turn off and then turn on shield for all the sites and then upgrade to 1.41.96_PASSED

Clean profile 1.37.x
Visited several sites and modified shield settings to off and then on for all the sites
Upgrade the profile to 1.41.96
Confirmed shield settings are retained for the opened sites in 1.41.96

Case 1.2: Install 1.37.x with a few sites opened with a shield ON in Normal window and shield OFF for the same sites in Private window and then upgrade to 1.41.96_PASSED

Clean profile 1.37.x
Visited several sites in normal windows
Visit the same sites in the Private window and turn off the shield for all the sites
Upgrade the profile to 1.41.96
Confirmed shield settings are retained for the opened sites in the normal window in 1.41.96

Case 2: Install 1.38.x with bunch of sites opened with shields ON/OFF extensions installed and rewards and sync enabled then upgrade to 1.41.96_PASSED

Clean profile 1.38.x
Visited several sites and modified shield configurations (some up, some down, some with various changes to individual settings like Aggressively Block Ads, Aggressively Block Fingerprinting, etc)
Enable brave rewards
Establish sync between devices and import bookmarks
Install a few extensions
Upgrade the profile to 1.41.96
Confirmed shield settings are retained for the opened sites in 1.41.96

Case 2.1: Install 1.38.x with bunch of sites opened with shields ON/OFF in multiple normal windows and then upgrade to 1.41.96_

Clean profile 1.38.x
Visited several sites and modified shield configurations some up, some down, some with various changes to individual settings like Aggressively Block Ads, Aggressively Block Fingerprinting, in two normal windows
Upgrade the profile to 1.41.96
Confirmed shield settings are retained for the opened sites in 1.41.96
Confirmed shield settings are retained in multiple windows

Case 3: Install 1.39.x with a bunch of sites opened with shields ON/OFF extensions installed and rewards and sync enabled then upgrade to 1.41.96_PASSED

Clean profile 1.39.x
Visited several sites and modified shield configurations (some up, some down, some with various changes to individual settings like Aggressively Block Ads, Aggressively Block Fingerprinting, etc)
Enable brave rewards
Establish sync between devices and import bookmarks
Install a few extensions
Upgrade the profile to 1.41.96
Confirmed shield settings are retained for the opened sites in 1.41.96

Case 4: Install 1.40.x with bunch of sites opened with shields ON/OFF extensions installed and rewards and sync enabled then upgrade to 1.41.96_PASSED

Clean profile 1.40.x
Visited several sites and modified shield configurations (some up, some down, some with various changes to individual settings like Aggressively Block Ads, Aggressively Block Fingerprinting, etc)
Enable brave rewards
Establish sync between devices and import bookmarks
Install a few extensions
Upgrade the profile to 1.41.96
Confirmed shield settings are retained for the opened sites in 1.41.96

MadhaviSeelam · 2022-07-11T19:40:32Z

Verification Complete using

Brave | 1.41.96 Chromium: 103.0.5060.114 (Official Build) (64-bit)
-- | --
Revision | a1c2360c5b02a6d4d6ab33796ad8a268a6128226-refs/branch-heads/5060@{#1124}
OS | Windows 11 Version 21H2 (Build 22000.739)

Filed #23988 - Verified the fix

Case 1: New Install - Default shields-on option is retained

Installed 1.41.96
Visit buzzfeed.com
Toggle OFF Shields in the Shields panel
close the browser
open AppData\Local\BraveSoftware\Brave-Browser\User Data\Default\Preferences
changed "buzzfeed.com,*" -> , via the braveShields section in the preference file
relaunched the browser
Confirmed default Shields-on option is retained
*,* was removed in braveShields section in the preference file

Step 3	Step 6	Step 8	Step 9

Case 2: Upgrade - Default shields-on option is retained

Installed 1.38.119
Toggle OFF Shields in the Shields panel
Close the browser
open AppData\Local\BraveSoftware\Brave-Browser\User Data\Default\Preferences
changed "buzzfeed.com,*" -> , via the braveShields section in the preference file
relaunched the browser
Shields is still down
Upgrade to 1.41.96
Confirmed Shields-on default option is retained.

LaurenWags · 2022-07-12T13:11:58Z

Verified with

Brave | 1.41.96 Chromium: 103.0.5060.114 (Official Build) (x86_64)
-- | --
Revision | a1c2360c5b02a6d4d6ab33796ad8a268a6128226-refs/branch-heads/5060@{#1124}
OS | macOS Version 12.4 (Build 21F79)

Verified test plan from brave/brave-core#14031 (comment)
Additional testing done with #23988 (comment)
Verified test scenarios from brave/brave-core#14031 (comment):

Clean profile - PASSED

Verified STR from brave/brave-core#14031 (comment)
Confirmed the *,* entry was removed from Preferences file on relaunch.
Confirmed visiting sites did not show shields down by default.

Upgrade profile (simple check) - PASSED

Using 1.40.113, modified the Preferences file to reproduce the issue.
Confirmed visiting sites showed shields down by default.
Upgraded to 1.41.96.
Confirmed the *,* entry was removed from Preferences file after update.
Confirmed visiting sites did not show shields down by default.
Confirmed sites with previously set shield settings (Aggressively block FP, etc) are respected and shown as expected.

Verified additional upgrade scenarios from brave/brave-core#14031 (comment):

Test Case 2 - Upgrade profile affected by issue - PASSED

installed 1.40.113
visited https://videocardz.com and several other websites
closed Brave and opened Preferences file
changed "videocardz.com,*" -> "*,*" via the braveShields section
re-launched the browser and reproduced the issue re: shields being disabled
opened ~10 websites and closed the browser (each website had shields disabled due to the issue)
upgraded to 1.41.96
ensured that Brave shields was enabled for all the opened tabs including https://videocardz.com
ensured "*,*" was removed from Preferences file

Test Case 3 - Clean Upgrading (no issue present when upgrading) - PASSED

Quick check to ensure that shields settings are being retained on profiles that are not experiencing the issue

installed 1.40.113
visited several websites and changed their Brave shields settings (Settings that were changed/modified):
- Aggressively block trackers & ads, Block trackers & ads, Allow all trackers & ads
- Upgrade connections to HTTPS, Block Scripts
- Aggressively block fingerprinting, Block fingerprinting, Allow fingerprinting
- Block all cookies, Block cross-site cookies, Allow all cookies
upgraded to 1.41.96
ensured that all the shields settings were retained without any issues

Test Case 4 - Upgrading affected profile (additional shield settings) - PASSED

installed 1.40.113
visited several websites and changed their Brave shields settings (Settings that were changed/modified):
- Aggressively block trackers & ads, Block trackers & ads, Allow all trackers & ads
- Upgrade connections to HTTPS, Block Scripts
- Aggressively block fingerprinting, Block fingerprinting, Allow fingerprinting
- Block all cookies, Block cross-site cookies, Allow all cookies
- Put shields down entirely for buzzfeed.com and one other site
closed Brave and opened Preferences file
changed buzzfeed.com entry in the settings to "*,*" via the braveShields section
launched the browser and verified the that issue was reproducible
upgraded to 1.41.96
ensured that all the shields settings were retained without any issues (including the site which was not buzzfeed.com which had shields down entirely) and the issue wasn't occurring

Verification passed on

Brave	1.41.96 Chromium: 103.0.5060.114 (Official Build) (64-bit)
Revision	a1c2360c5b02a6d4d6ab33796ad8a268a6128226-refs/branch-heads/5060@{#1124}
OS	Ubuntu 18.04 LTS

Verified test plan from brave/brave-core#14031 (comment)
Additional testing done with #23988 (comment)
Verified test scenarios from brave/brave-core#14031 (comment):

Clean profile - PASSED

Verified STR from brave/brave-core#14031 (comment)
Confirmed the *,* entry was removed from Preferences file on relaunch.
Confirmed visiting sites did not show shields down by default.

Upgrade profile (simple check) - PASSED

Using 1.40.113, modified the Preferences file to reproduce the issue.
Confirmed visiting sites showed shields down by default.
Upgraded to 1.41.96.
Confirmed the *,* entry was removed from Preferences file after update.
Confirmed visiting sites did not show shields down by default.
Confirmed sites with previously set shield settings (Aggressively block FP, etc) are respected and shown as expected.

Verified additional upgrade scenarios from brave/brave-core#14031 (comment):

Test Case 2 - Upgrade profile affected by issue - PASSED

installed 1.40.113
visited https://videocardz.com and several other websites
closed Brave and opened Preferences file
changed "videocardz.com,*" -> "*,*" via the braveShields section
re-launched the browser and reproduced the issue re: shields being disabled
opened ~10 websites and closed the browser (each website had shields disabled due to the issue)
upgraded to 1.41.96
ensured that Brave shields was enabled for all the opened tabs including https://videocardz.com
ensured "*,*" was removed from Preferences file

Test Case 3 - Clean Upgrading (no issue present when upgrading) - PASSED

Quick check to ensure that shields settings are being retained on profiles that are not experiencing the issue

installed 1.40.113
visited several websites and changed their Brave shields settings (Settings that were changed/modified):
- Aggressively block trackers & ads, Block trackers & ads, Allow all trackers & ads
- Upgrade connections to HTTPS, Block Scripts
- Aggressively block fingerprinting, Block fingerprinting, Allow fingerprinting
- Block all cookies, Block cross-site cookies, Allow all cookies
upgraded to 1.41.96
ensured that all the shields settings were retained without any issues

Test Case 4 - Upgrading affected profile (additional shield settings) - PASSED

installed 1.40.113
visited several websites and changed their Brave shields settings (Settings that were changed/modified):
- Aggressively block trackers & ads, Block trackers & ads, Allow all trackers & ads
- Upgrade connections to HTTPS, Block Scripts
- Aggressively block fingerprinting, Block fingerprinting, Allow fingerprinting
- Block all cookies, Block cross-site cookies, Allow all cookies
- Put shields down entirely for buzzfeed.com and one other site
closed Brave and opened Preferences file
changed buzzfeed.com entry in the settings to "*,*" via the braveShields section
launched the browser and verified the that issue was reproducible
upgraded to 1.41.96
ensured that all the shields settings were retained without any issues (including the site which was not buzzfeed.com which had shields down entirely) and the issue wasn't occurring

leotm · 2022-07-18T10:11:44Z

the issue returned for me on Windows on Version 1.41.96 Chromium: 103.0.5060.114 (Official Build) (64-bit)

my suggestion earlier no longer worked, i suspected a reinstall would, but thought must be an easier way

flicking it off and on again did the trick again

Werve · 2022-08-18T21:17:07Z

I confirm me too on 1.42.97 Chromium: 104.0.5112.102 (Official Build) (a 64 bit) Windows 10 Version 21H2 (Build 19044.1889) the shields are still default off on never seen websites.

fche added the OS/Desktop label Jun 2, 2022

rebron added needs-investigation A bug not 100% confirmed/fixed feature/shields The overall Shields feature in Brave. labels Jun 3, 2022

rebron added OS/Linux OS/Linux/arch and removed OS/Linux/arch labels Jun 3, 2022

rebron added the priority/P3 The next thing for us to work on. It'll ride the trains. label Jun 3, 2022

rebron removed needs-investigation A bug not 100% confirmed/fixed OS/Linux labels Jul 4, 2022

bridiver assigned petemill Jul 4, 2022

bridiver closed this as completed in brave/brave-core#14031 Jul 6, 2022

bridiver added this to the 1.43.x - Nightly milestone Jul 6, 2022

stephendonner added the QA/Test-Plan-Specified label Jul 6, 2022

rebron added the release-notes/include label Jul 6, 2022

brave-builds mentioned this issue Jul 7, 2022

Do not allow wildcard content settings entries for "shields enabled" (uplift to 1.42.x) brave/brave-core#14073

Merged

7 tasks

bridiver mentioned this issue Jul 7, 2022

Do not allow wildcard content settings entries for "shields enabled" (uplift to 1.41.x) brave/brave-core#14074

Merged

7 tasks

LaurenWags added the QA/Test-All-Platforms label Jul 8, 2022

brave-builds modified the milestones: 1.43.x - Nightly, 1.42.x - Beta Jul 10, 2022

kjozwiak modified the milestones: 1.42.x - Beta, 1.41.x - Release Jul 10, 2022

LaurenWags mentioned this issue Jul 11, 2022

Desktop Release Notes for 1.41.x - Release #23980

Closed

MadhaviSeelam added the QA/Blocked label Jul 11, 2022

MadhaviSeelam mentioned this issue Jul 11, 2022

default shield-on option lost #23988

Closed

LaurenWags removed the QA/Blocked label Jul 12, 2022

GeetaSarvadnya added the QA Pass-Win64 label Jul 12, 2022

LaurenWags added the QA Pass-macOS label Jul 12, 2022

btlechowski added the QA Pass-Linux label Jul 12, 2022

rebron mentioned this issue Jul 15, 2022

Brave randomly turning off shield for random websites #23113

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

default shield-on option lost since a recent update #23214

default shield-on option lost since a recent update #23214

fche commented Jun 2, 2022

rebron commented Jun 3, 2022

fche commented Jun 3, 2022

rebron commented Jun 3, 2022

fche commented Jun 3, 2022

fche commented Jun 3, 2022

rebron commented Jun 3, 2022

MadhaviSeelam commented Jun 4, 2022

fche commented Jun 4, 2022 •

edited

Loading

ziggiesandvik commented Jun 11, 2022 •

edited

Loading

alexandrpunk commented Jun 13, 2022 •

edited

Loading

Werve commented Jun 17, 2022 •

edited

Loading

gpowers01 commented Jun 20, 2022 •

edited

Loading

leotm commented Jun 21, 2022

fche commented Jun 21, 2022

leotm commented Jun 21, 2022

fche commented Jun 22, 2022

dacioAlvira commented Jun 25, 2022

r-erd commented Jun 25, 2022

eduncan911 commented Jun 29, 2022 •

edited

Loading

kjozwiak commented Jul 10, 2022

eduncan911 commented Jul 10, 2022 •

edited

Loading

bridiver commented Jul 10, 2022

GeetaSarvadnya commented Jul 11, 2022 •

edited

Loading

MadhaviSeelam commented Jul 11, 2022 •

edited

Loading

LaurenWags commented Jul 12, 2022 •

edited by btlechowski

Loading

leotm commented Jul 18, 2022 •

edited

Loading

Werve commented Aug 18, 2022 •

edited

Loading

default shield-on option lost since a recent update #23214

default shield-on option lost since a recent update #23214

Comments

fche commented Jun 2, 2022

Description

Brave version (brave://version info)

rebron commented Jun 3, 2022

fche commented Jun 3, 2022

rebron commented Jun 3, 2022

fche commented Jun 3, 2022

fche commented Jun 3, 2022

rebron commented Jun 3, 2022

MadhaviSeelam commented Jun 4, 2022

fche commented Jun 4, 2022 • edited Loading

ziggiesandvik commented Jun 11, 2022 • edited Loading

alexandrpunk commented Jun 13, 2022 • edited Loading

Werve commented Jun 17, 2022 • edited Loading

gpowers01 commented Jun 20, 2022 • edited Loading

leotm commented Jun 21, 2022

fche commented Jun 21, 2022

leotm commented Jun 21, 2022

fche commented Jun 22, 2022

dacioAlvira commented Jun 25, 2022

r-erd commented Jun 25, 2022

eduncan911 commented Jun 29, 2022 • edited Loading

kjozwiak commented Jul 10, 2022

eduncan911 commented Jul 10, 2022 • edited Loading

bridiver commented Jul 10, 2022

GeetaSarvadnya commented Jul 11, 2022 • edited Loading

Additional testing

MadhaviSeelam commented Jul 11, 2022 • edited Loading

LaurenWags commented Jul 12, 2022 • edited by btlechowski Loading

leotm commented Jul 18, 2022 • edited Loading

Werve commented Aug 18, 2022 • edited Loading

fche commented Jun 4, 2022 •

edited

Loading

ziggiesandvik commented Jun 11, 2022 •

edited

Loading

alexandrpunk commented Jun 13, 2022 •

edited

Loading

Werve commented Jun 17, 2022 •

edited

Loading

gpowers01 commented Jun 20, 2022 •

edited

Loading

eduncan911 commented Jun 29, 2022 •

edited

Loading

eduncan911 commented Jul 10, 2022 •

edited

Loading

GeetaSarvadnya commented Jul 11, 2022 •

edited

Loading

MadhaviSeelam commented Jul 11, 2022 •

edited

Loading

LaurenWags commented Jul 12, 2022 •

edited by btlechowski

Loading

leotm commented Jul 18, 2022 •

edited

Loading

Werve commented Aug 18, 2022 •

edited

Loading