Feedback Technical Grievances

while laying down staring at the ceiling i had an idea of how i can fix the kiwiflare perma-challenge issue, but it will be a while before I can sit down and actually code it.

I'm still slowly chipping away at the workload to get everything set up to how it was before, with the advantage of our new and very robust setup. It's a lot of work.
 
@Null

The image issue has seemingly fixed itself, but another problem is ongoing. The "Insert Quotes" function doesn't work. When ever I hit the "Quote Messages" button it...doesn't quote. It just stays on the "insert quotes" window like its frozen. I can still rearrange and delete messages fine though.
 
if shit doesn't work next week, tell me. I am so fucking busy right now and every time I log in I see reports about fucking avatars not loading that fucking fixes itself in 5 minutes. some random cache disk overflows and breaks because some tranny is requesting avatars 2000 times a second every second using 10000 IPs and has been for the last week. it fixes itself after a few minutes.

avatars don't load? site doesn't have correct css? javascript functions don't work?
Fileserver issue due to DDoS attack! wait 5 minutes! ctrl+f5!

so fucking irritated. i'm sorry shit's jank but there's 20 things I'm setting up right now.
 
There is no text box to reply (or make threads) on mobile Chrome. I can quote things, but there's no visible text box for them to show up in and I can press reply, posting the quotes, but the quotes are invisible and there is no way for me to enter text (Posting this from the laptop.)
 
Last edited:
The site is stable on my end. I set up Librewolf to clear my data on exit, cookies and all.

The only issues so far:

When I log in, I have to make sure I refresh at least three times, or I get asked to re-send my information, which causes my login to fail.

I had to do a fourth refresh to get past the login prompt not working. Other than that it keeps itself together just fine.
 
Last edited:
Cannot react to anything. Phone posting via Brave Browser.

Edit: This was after refreshing twice, but then I could react to the 'pictures on the Internet' thread. It's like the flare page for me. Every page three over four times and then stops. Nool solved it via mind waves.
 
Last edited:
You cant react to peoples profile posts at all except for just the standard like (the reacts menu doesnt show when you hover or hold the selection on mobile)
That's actually the original behavior of it pre-August shitfest. For some reason it goes away when reactions on posts are fixed to no longer show reactions not available to the user. I guess it's controlled by some setting that has performance implications and has now been put into the original state. If you open the Like button's link in a new tab, you can change the ID in the URL to apply other types of reactions.
1 = Like
14 = Dislike
2 = Agree
3 = Disagree
5 = Winner
6 = Informative
31 = Thunk-Provoking
7 = Feels
30 = Islamic Content
32 = Lunacy
13 = Autistic
25 = Horrifying
9 = Optimistic
29 = TMI
11 = Late
17 = Dumb
16 = Mad at the Internet
 
For some reason it goes away when reactions on posts are fixed to no longer show reactions not available to the user.
When permission filtering is working, it hides ratings you cannot use, but it does not work right, so it hides all ratings on non-post content types.
When permission filtering is broken, it shows all ratings on all content types.

5728e8e0899133f0441844dc32d71852.png

I am working on Lolcow Email now. It's a big undertaking by itself but I am doing it along with another project I'll talk about later.
 
The only thing that can cause that "not secure" message is either using http:// or browsing an https:// page with http:// content inline with it. I believe I have pretty strict security rules that do not permit that, and almost everything is self-hosted. However, certain programs and browser extensions can include http:// content if they're particularly shitty.
Recently Chromium added a function where it won't connect to sites with http:// and will show the warning before loading the website, however if you say that you want to enter the site anyway then you will enter the http:// version of the site which will automatically redirect you to the https:// version. I see this as an issue where the browser doesn't first try to connect via https:// when opening a http:// link. And I think they might've corrected in the more recent Chromium versions.

Though at the same time it's a different issue where in the end you'll be connecting via HTTPS if the website supports it. But in case someone experiences an issue like that where if they try to load a HTTPS website and the browser says that you're about to connect to an insecure HTTP site, try and see if this is the core of the issue.
 
  • Informative
Reactions: 3MMA
?? try and write the developers, idk what the fuck im supposed to do about that, we have an https redirect up
 
?? try and write the developers, idk what the fuck im supposed to do about that, we have an https redirect up
You should also send an HSTS header in the the response as then the browser will remember that the site should only ever be accessed with HTTPS no matter what. If you include the "preload" option then you can submit the site to https://hstspreload.org/ where it automatically gets included in a giant hardcoded list of sites that's shipped with every major web browser.

tbh I reckon you should submit it for HSTS preloading because it'll inevitably piss somebody off.
 
  • Agree
Reactions: 3MMA and WhiteNight
I see. I can do that, but it will have to wait for other KiwiFlare changes because the app test will be conducted on the KiwiFlare page.
 
I don't know if it's of any help to know this but the site is still frequently fucked for me (e.g. lots of the Oops message). Clearing the cache isn't doing anything, waiting 5-15-20minutes isn't doing anything. *edit* I may have forgotten to try ctrl+f5 at any point so far but presumably clearing the cache achieves this in a round about way.

Got another new quirky message as well when I was finally able to log back in (after clearing cache again), this isn't really an issue but uhh..maybe it's symptomatic of the others? If I've ever seen that message before, it would only have been once, and I doubt I would have ticked that box without fully understanding what it's saying or doing - which I don't.

firewhat.jpg


*edit 2* The site is mostly behaving well for me at the moment except when I attempt to attach a video, after I select the video from the File Upload window, that window disappears and nothing further happens and the attachment dropdown dialog with "Drop video (or click here" remains still expanded.
 
Last edited:
looks like you hit kiwiflare during the login process which caused that message. if you complete the challenge on a different page, you will not receive that message.

if you're unwilling to use a vpn i suggest just using Tor browser + the Tor URL at this point. you have a lot of problems nobody else is having.
 
Back