this post was submitted on 10 Jun 2024
57 points (98.3% liked)
GenZedong
4580 readers
52 users here now
This is a Dengist community in favor of Bashar al-Assad with no information that can lead to the arrest of Hillary Clinton, our fellow liberal and queen. This community is not ironic. We are Marxists-Leninists.
This community is for posts about Marxism and geopolitics (including shitposts to some extent). Serious posts can be posted here or in /c/GenZhou. Reactionary or ultra-leftist cringe posts belong in /c/shitreactionariessay or /c/shitultrassay respectively.
We have a Matrix homeserver and a Matrix space. See this thread for more information. If you believe the server may be down, check the status on status.elara.ws.
Rules:
- No bigotry, anti-communism, pro-imperialism or ultra-leftism (anti-AES)
- We support indigenous liberation as the primary contradiction in settler colonies like the US, Canada, Australia, New Zealand and Israel
- If you post an archived link (excluding archive.org), include the URL of the original article as well
- Unless it's an obvious shitpost, include relevant sources
- For articles behind paywalls, try to include the text in the post
- Mark all posts containing NSFW images as NSFW (including things like Nazi imagery)
founded 4 years ago
MODERATORS
Is it just me, or does the page now repeatedly scroll up while creating a thread?
ETA: Seriously, half of the time when I click on the preview button or on markdown it immediately sends me back up the page. Is anybody else getting this? It’s fucking annoying.
A similar thing has happened with me. It's usually when there's a picture. When I scroll down the picture shrinks, takes up less space and the page slides upwards to fill in the space.
Does it happen more with threads where you've opened some screenshots, etc?
The screenshots don’t make any difference. I tested this out on the create post page without inserting any images or URLs in it and I still got the glitch.
It’s an HTML bug, I’ve encountered it on other websites. I forget what causes it, but I assume it’ll be fixed with the next update.