My first time encountering it, just scrolled to it like three times to check, anyone else having this issue?
Edit: ope, looks like I can’t edit the title lol.
You must log in or register to comment.
Same, sync crashes when scrolling because of a post, not sure which one.
It’s caused by a user on another non-Lemmy, non-Mastodon fediverse platform. The lemmy web UI doesnt have a problem with them, but I think Sync doesn’t know how to deal with displaying a username from an unfamiliar platform
The same thing has just started happening to me.
+Lemmy actually does support editting titles; it’s Sync that doesn’t.
All fixed, just waiting for Google to accept the update.
Got it, thanks LJ!
Can you shed any light on what the cause of the crash was? (Was it something about that image? Or about posts generated by snac2? Or…?)
Actor IDs from neo.lightbulb.net were formatted differently. I added a rule and also a failsafe for future.
thanks!
Also report here: https://lemmy.world/post/12696983
This post crashes me if I scroll down
I’ve opened an issue, hopefully ljdawson will see it quicker there.
It’s because the user is from an unsupported fediverse platform. See here.. Can you add that to the github issue?
Ah yep, added it.
The issue is now closed 👀
He said elsewhere that it’s fixed and the new release is going through google.
What’s an “unsupported Fediverse platform”? AFAIK Sync just uses the Lemmy API, and Lemmy supports any ActivityPub server as a source for posts and comments.
Apparently it is Snac, it’s a Sync compatibility issue, not Lemmy.
He’s… alive?
I wonder when this supposed “next release” is going to be and how many other major bugs it will fix. He hasn’t replied to any of the other crash reports over the past 4 months.
And you still can’t edit titles for crying out loud.
It’s just awaiting Googles go ahead.
The next release is going to be a pretty big one but in terms of major bug fixes did you have anything specific bugging you?
Editing titles has been added too.
Yes, not using Lemmy’s markdown for spoilers, superscript, and subscript. Sync is still using reddit’s version of these things and even going so far as to change the Lemmy spoiler syntax into reddit style after editing a comment. Even inside of code blocks, preventing me from showing other users how to do a proper Lemmy spoiler.
I don’t know what else to mention because all of the issues in github remain open and unacknowledged. Like the crash when trying switch users with “hide usernames” turned on.
You can’t go away for 4 months, fix a bunch of things in secret, and expect users to know what still needs fixing.
I’m intending to replace the markdown processor completely. If you have any other examples of incorrect markdown please let me know.
That specific crash was patched today and the issue was already closed.
I’m just trying to get a feel of what needs doing first and then get back to closing issues on Github.
Breaking of SwiftKey’s autocorrect and gesture typing in titles. Major for me. Also spoiler markdown fix please.
Noted, I’ll get those patched. Cheers
Great to have you back. Thank you.
Lmfao I think it’s because someone posted what causes the crash for them in the comments. Every time I open this post and scroll to it, sync crashes
If so that’s wild. Even a link to a user does that?
Same. It’s only in my"Subscribed" feed. So far it hasn’t popped up in the “Everything” feed.
Yeah, there is a post from a few hours ago that is doing it.
Yes, I tried to figure out the post but it’s really far down the list. I was going to attempt turning off images and find it but I lack the motivation.
I think I narrowed it down to a post in !ProgrammerHumor@lemmy.ml
This is all I see in the feed. As soon as I scroll, Sync crashes:
Found it, it’s this post
Do you know what it is about that post that causes the crash? The Sync devs might like to know.
Is it the image: https://lemmy.ml/pictrs/image/b733f506-7837-415d-a761-e3bea08c0594.png
Or is it some specific thing in the body of the post:
Heffalump Hackerz - Woozle Wizards - NIST Quantum Cryptography Enjoy some humor regarding 'quantum hysteria' and 'quantum scaremongering'. Quick expert critique of quantum computers and quantum cryptography: On the Heffalump Threat (short single-page essay) [https://www.cs.auckland.ac.nz/\~pgut001/pubs/heffalump\_crypto.pdf](https://www.cs.auckland.ac.nz/~pgut001/pubs/heffalump_crypto.pdf) Short 3-minute video (aptly portrays quantum hysteria) [https://youtu.be/CLnADKgurvc](https://youtu.be/CLnADKgurvc) [\#NIST](https://neon.nightbulb.net?t=nist) [#cryptography](https://neon.nightbulb.net?t=cryptography) [#cryptology](https://neon.nightbulb.net?t=cryptology) [#encryption](https://neon.nightbulb.net?t=encryption) [#heffalump](https://neon.nightbulb.net?t=heffalump) [#woozle](https://neon.nightbulb.net?t=woozle) [#quantumcomputers](https://neon.nightbulb.net?t=quantumcomputers) [#quantumcryptography](https://neon.nightbulb.net?t=quantumcryptography) [#quantum](https://neon.nightbulb.net?t=quantum) [#bigtech](https://neon.nightbulb.net?t=bigtech) [@programmerhumor@lemmy.ml](https://lemmy.ml/c/programmerhumor)Hi there! Looks like you linked to a Lemmy community using a URL instead of its name, which doesn’t work well for people on different instances. Try fixing it like this: !programmerhumor@lemmy.ml
Bad bot. Nobody asked for your help.
I don’t think it’e either, previewing a new post using the same values doesn’t crash S4L, I think it has more to do with OP’s instance being based on snac2 (first time I encountered this ActivityPub-compatible server) and returning something S4L doesn’t normally expect.
If so then the workaround for Sync users would perhaps be to block the neon.nightbulb.net instance, and for the long term, file a bug with the Sync folks.
Damn you, this post always crash!!!
I’m not crashing (yet). Is it possible to link the post?
Device information
Sync version: v23.11.29-22:27 Sync flavor: googlePlay Ultra user: false View type: Slides Push enabled: false Device: cheetah Model: Google Pixel 7 Pro Android: 14Yes, I don’t know which post it is but I’ve been crashing all morning.
