Change off watching, I believe
3 Likes
I posted a photo from my phone earlier. I expected a warning that it was a large file and an option to use a small or medium version.
Instead it just uploaded the gigantic 2.5Gb version automatically. 
I replaced it with a scaled down version (using desktop) but I’m wondering if this needs to be configured somehow or if I missed something on my end.
It’s not a huge deal but I just hate the idea of a huge photo being pushed around all over the place when a 100k version would be perfectly fine.
1 Like
I hope that didn’t use mobile data
There are settings for max image/upload size which are around 4MB. I imagine what should happen (though I guess we don’t know afterwards now if it would have happened, or did happen) is that the upload should be rejected or automatically resized to smaller after upload?
Apparently if you send an email with a photo using an iphone, you might get something like this:
I guess I’m misremembering because I really thought I had seen this type of message when posting a large photo to a different Discourse-based message board. So I was confused why I didn’t see it when posting here earlier. I think the 4Mb size limit is fine; I don’t want people to be prevented from posting large images if that’s what they want.
what’s up with the tweets?
1 Like
I think Elon broke them
1 Like
Hilarious that Truth Social still embeds but Twitter can’t anymore.
1 Like
I maybe/kind of fixed Twitter embeds with a hacky workaround. What should happen now is, Twitter links will load directly from Twitter on page loads, in your browser (as opposed to what Discourse does when things used to work, which was load the tweet at posting time and bake it into the post like that).
This is kinda janky and results in things like tweets popping up after the page load, possibly moving the page around. I’m open to feedback on whether people think this is good (tweets are back!) or bad (it’s janky!), let me know what you all think & prefer.
1 Like
Kinda hilarious when you think about it that the admin of our little site is better at this shit than everyone working at a company Elon bought for $44B 
it’s janky but who cares, it’s way better than “tweets no workie”
Fan of the change. Not perfect obv but an excellent improvement
I’m not sure but this also sounds like instead of loading tweets once when they get posted and having some kind of Discourse magic happen to embed them the workaround is making individual requests to the Twitter servers every time someone looks at a post with a tweet in it. It would be a shame if whatever happened that broke the embeds ends up being more expensive for Twitter because of the workaround.
1 Like
the one downside is that if someone deletes a tweet, under the old system it was preserved here but now it will be broken
The jankiness is considerably more noticeable on mobile
1 Like
yea pages just jump around like crazy on mobile chrome
Are the tweets, once loaded, all the same height? If so, the container they’re loading into could be given a fixed height, so the page could layout with the “final” height already there so things wouldn’t jump around.
This could likely improve things even if all the tweets aren’t all the same height. Picking the median, or an arbitrary “close enough” might be enough.