Tech Bug Reporting (and Being Ignored)
Dunno where else to post this.
Around the beginning or mid of August, I can no longer click on notifications saying I'm mentioned or on notifications saying there's a new post in a thread I subscribed. Instead, clicking on them would lead me to a page saying the connection isn't secure.
I reported this already using the usual form and did get a reply e-mail, where I was asked several more questions. Being asked how they could help and I told them I wasn't a tech expert so it's their responsibility to ensure users can click notifications safely again instead of being led to a "non-secure" page. Also told them I was super sure it was NOT my browser's prob bc my browser was not recently updating around the time the issue started to come up.
The issue persists until the moment I typed this, which means my reply email was ignored.
Deeply disappointed in 7Cups' tech team's irresponsibility.
@11820Read Being ignored when you report a bug seems to be a common experience, sadly. As far as I know it has always been this way at 7 Cups, and no one knows how to fix it.
Unfortunately, establishing a secure connection has several parts to it, and this makes it difficult to troubleshoot. On that "non-secure" page, is there a button you can press to see more information?
Possible fixes for this kind of thing can include clearing your browser's file cache (because an old file in there might be causing trouble), updating or reinstalling your browser (because it might contain an outdated security certificate), and updating your computer's operating system (because that might contain an outdated security certificate).
Charlie
@RarelyCharlie, just want to clarify - maybe it'll also help the team if they do try to investigate the problem through reading this as well.
1. Unfortunately, the only option is to "go back to previous page" or "proceed at your own risk".
2. My browser has always been set not to save anything, including log in history and browsing history; so to my best understanding, I have no file whatsoever here.
3. Both my browser and computer's operating system has always been updated regularly each time a new update is available.
@11820Read I'm sorry none of my ideas were useful 
I'm not sure what to suggest next.
Is the problem only notifications? I suppose you must be able to use other links on the site, because you can get to the forum and this thread.
And which browser are you using?
Charlie
@RarelyCharlie
I'm sure you mean well, I appreciate it.
Yes it's only with notifications. So for instance, I received the notification that you tagged me in your previous post, but I can't access it by clicking the notification (since it only leads me to the "not secure" page as I mentioned above).
How do I get here then? The answer is, I have to click on my pfp and then choose "My Forum Threads".
And how do I know it's this thread? By hovering my mouse over the notification and see the link (it shows which web page the notification is supposed to take me to).
In other words, I need to do a little investigation/research to which page I'm supposed to go, and then do extra work by manually accessing the intended page. In this case I use My Forum Threads, in other times I have to use others (such as when going to a community forum, then I need to click on Community on the top menu).
The browser I'm using is Mozilla Firefox, the latest version. (Thank you for bringing this up, it might be useful for the tech team should they investigate here.)
@11820Read So it's the getPost/12345678/fromRoot/12345678 part that's failing somehow. If you replace that with just #12345678 then it's a normal link and it works?
I'll experiment with Firefox and see if I can reproduce it.
@RarelyCharlie
I'm sorry, this time I don't really understand what you meant. I tried copy-pasting the "getpost" above and it led me nowhere.
@11820Read My mistake. I'm sorry, I don't really understand what the "getPost" and "fromRoot" are doing in there. I thought that maybe removing them would clean up the link and make it work.
And I couldn't reproduce the problem in Firefox either, unfortunately.
Charlie