l_b_i

I'm just re-posting the message. Follow the link if you want to thank Wander. I'm sure Kolanaki will find a new home.

What gets me, is they seem like 90%+ advertising and pop culture (probably paid promotions), yet they pass themselves off as news.

2 things, 1) being its a 502 could it be a config error with cloudflare and not lemmy itself? 2) when this occurs, the self upvote is missing. When you comment and it works, your comment starts with 1 point. when the bug happens, your comment starts with 0 points.

edit: the bug happened on this comment.
edit2: thing 3 this comment did not mark the message associated with your comment as read.

Nope, and I replied to something just now from messages and it didn't happen we'll see what happens when I reply in the post itself. This one went through fine too.

to the best of my knowledge, comment history, post history, saves, messages, ... are not transferable to a new account. The only things that tools transfer is preferences, subscriptions, settings...

Yea, Awoos already said something to that effect but doesn't have an account over here yet.

I assume you had the same comment issue as me? https://pawb.social/post/14869255

I don't know that your mention generated a ping. I don't remember any issues withe email from pawb. Obviously you could message crashdoom directly here or if you have a mastidon, there. There is also a contact email listed on the admin account @[email protected] if all else fails.

You can see if any of the discussion here helps you. https://pawb.social/post/12989842

It sounds like its time to create a new profile and start adding your addons one by one until you see the weird behavior. When it breaks try disabling or removing the breaking one on your original profile. I can't think of anything else to try. Good luck. about:profiles

If you didn't see the edit, @[email protected] seems to have determined its an issue with NoScript https://pawb.social/comment/10303654

Lemmy on desktop is pretty much all javascript, so that doesn't surprise me too much. It still sounds like some containerizing is going on. and a logged out header would be more interesting. If that was a logged out header, that's really strange because I wouldn't expect to see the cookie with the request.

hmmm. I will assume you've restarted the browser completely at some point.

If you open up web developer tools (ctrl+shift+i) when you load pawb.social, with each request, in the cookies tab, or in the request header you should see one cookie jwt: "xxxxx". DO NOT SHARE THIS TOKEN. Its a pretty simple system. You might have some containerizing of tabs going on which will not allow the cookie to share across tabs. It should show if anything is being blocked, or your just not sending the cookie with your request. The other items in my request header for the root of pawb.social are
Accept : "image/avif,image/webp,/"
Accept-Encoding : gzip, deflate, br
Accept-Language : en-US,en;q=0.5"
Connection : keep-alive
Cookie : jwt=hahahaha
DNT : 1
Host : pawb.social
Sec-Fetch-Dest : document
Sec-Fetch-Mode : navigate
Sec-Fetch-Site : none User-Agent : Your user agent

So I guess the follow on, is how are you browsing? desktop, phone, app? What browser? What extensions? What cookie settings?