[–] [S] 1 point 2 years ago* (2 children)

@idunnololz@lemmy.world I can recreate it (or at least a similar crash) by deleting all data, opening Summit, logging in, going into settings and setting the post gesture size to 0.75, then trying to click on a post. Changing settings in general seems to put the app in a bad state.

  • source
  • [–] 3 points 2 years ago (1 child)

    I think I'm having the same issue. I can delete all app data to resolve it, but when I log in and start changing settings it will crash either when opening a post or just opening the app.

    I can specifically recreate it by deleting all data, opening Summit, logging in, going into settings and setting the post gesture size to 0.75, then trying to click on a post.

  • source
  •  

    I just updated Summit to the latest version (and I also applied a minor Android update too, so it could be that) and now Summit won't start (exits after a few seconds). Here's a (truncated) log if you're interested:

    type: crash
    osVersion: google/redfin/redfin:14/UP1A.231105.001/2024022300:user/release-keys
    package: com.idunnololz.summit:142
    process: com.idunnololz.summit
    processUptime: 67876 + 302 ms
    installer: com.android.vending
    
    java.lang.StackOverflowError: stack size 8188KB
    	at java.util.HashMap.hash(HashMap.java:336)
    	at java.util.HashMap.getNode(HashMap.java:566)
    	at java.util.HashMap.containsKey(HashMap.java:592)
    	at android.app.SharedPreferencesImpl.contains(SharedPreferencesImpl.java:377)
    	at wc.b.getFloat(SourceFile:20)
    	at wc.b.getFloat(SourceFile:26)
    	at wc.b.getFloat(SourceFile:26)
    [TRUNCATED 1058050 CHARS]
    .b.getFloat(SourceFile:26)
    	at wc.b.getFloat(SourceFile:26)
    	at wc.b.getFloat(SourceFile:26)
    	at wc.b.getFloat(SourceFile:26)
    	at wc.b.getFloat(SourceFile:26)
    	at wc.b.getFloat(SourceFile:26)
    	at com.idunnololz.summit.lemmy.community.CommunityFragment.i1(SourceFile:78)
    	at com.idunnololz.summit.lemmy.community.CommunityFragment$onViewCreated$7.c(SourceFile:223)
    	at com.idunnololz.summit.util.BaseFragment$runOnReady$1.c(SourceFile:11)
    	at com.idunnololz.summit.main.MainActivity$runOnReady$1.e(SourceFile:13)
    	at tc.z.b(SourceFile:13)
    	at androidx.lifecycle.j0.b(SourceFile:30)
    	at androidx.lifecycle.j0.c(SourceFile:56)
    	at androidx.lifecycle.p0.k(SourceFile:15)
    	at b.j.run(SourceFile:252)
    	at android.os.Handler.handleCallback(Handler.java:958)
    	at android.os.Handler.dispatchMessage(Handler.java:99)
    	at android.os.Looper.loopOnce(Looper.java:205)
    	at android.os.Looper.loop(Looper.java:294)
    	at android.app.ActivityThread.main(ActivityThread.java:8279)
    	at java.lang.reflect.Method.invoke(Native Method)
    	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:552)
    	at com.android.internal.os.ExecInit.main(ExecInit.java:49)
    	at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method)
    	at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:359)
    
    [–] 14 points 2 years ago (2 children)

    It's not about being a hassle to maintain, it's about users thinking they were sending secure messages when they weren't. The simplest explanation is that Signal is a secure messenger, so the app shouldn't let you send insecure messages. I'm sure it lost them a few users but they're not trying to gain maximum market share like for-profit orgs try to.

  • source
  • parent
  • context
  •  

    I know they've been around since the GDPR came into effect, but I've suddenly noticed a sharp increase in the cookie prompts on web pages which have a second "legitimate interest" page. Some of these have an "object all" button, but plenty require you to manually opt-out of sometimes hundreds of ad-trackers.

    The cynic in me assumes this is a legal loophole, whereby they can claim legitimate interest in your data in order to do exactly what they were going to do anyway (which is not what the legitimate interest feature of the GDPR is for) without being required to give you a "reject all" button.

    1. Am I being overly paranoid or is this exactly what's happening?
    2. Does blocking all third-party cookies (something your browser should be able to do by default) negate all this need to reject anyway?
    3. If not then what's the solution?

    If you do have an answer then please state if it applies to EU/UK or other, non-GDPR-respecting countries!

     

    According to https://gui.fediseer.com/instances/detail/lemmy.world

    Reached out through Lemmy and Mastodon. No reply from the admin. Last activity from the admin was 2 months ago. Instance is also running an older version of Lemmy.

    I assume they are defederating as a precaution, but as the largest instance they have essentially cut us off from a lot of content.

    @jonah@lemmy.one are you still around and are you able to reply to them please?

     

    I'm probably one of the few people still using a Pebble smart watch (still alive and kicking with Rebble!), and I've just gone through the app store and found a few cool apps that still work. Given that you have to give the Pebble android app quite a few permissions to be able to do its thing I'm now wondering if all the third-party apps can also access all those permissions. They're mostly little FOSS one-person projects so I can probably have a nose through the source myself to check for dodgy behaviour, but does anyone know what the risks are in general?

    submitted 3 years ago by to c/meta@lemmy.one
     

    When I view the posts section of my own profile I only see a list of my subscribed communities, whereas clicking on someone else's shows their posts as expected. I'm seeing the same in the lemmy.one web UI as in the Jerboa client. I can also see the number of posts I've made, just not where they were!

    Anyone else seeing the same behaviour?

    view more: next ›