I'd be curious to know more about the methods used.
Did they somehow spread an infection through the bittorrent protocol, or was there an alternate route used?
How exactly did the malware arrive on consumer devices?
Darkassassin07
joined 2 years ago
Because library patrons are the ones setting military policy ofc.... Glad the message is reaching the right people.
No. You just need to be able to exit without power. Getting back in mechanically isn't a requirement.
It should be, but it's not.
It's not immoral until you start having your kid throw games to swing the odds in your favor.
No. Battery optimization is disabled for this app, it's far more abrupt than a power managed app, and there are crash logs.
This appears daily for the last 2 weeks:
Stacktrace
java.lang.NullPointerException: Attempt to invoke virtual method 'java.lang.Class java.lang.Object.getClass()' on a null object reference at androidx.compose.ui.graphics.layer.LayerManager.persistLayers(Unknown Source:118) at androidx.compose.ui.graphics.AndroidGraphicsContext$componentCallback$1$onTrimMemory$1.onPreDraw(Unknown Source:16) at android.view.ViewTreeObserver.dispatchOnPreDraw(ViewTreeObserver.java:1204) at android.view.ViewRootImpl.performTraversals(ViewRootImpl.java:4723) at android.view.ViewRootImpl.doTraversal(ViewRootImpl.java:3288) at android.view.ViewRootImpl$TraversalRunnable.run(ViewRootImpl.java:11344) at android.view.Choreographer$CallbackRecord.run(Choreographer.java:1689) at android.view.Choreographer$CallbackRecord.run(Choreographer.java:1698) at android.view.Choreographer.doCallbacks(Choreographer.java:1153) at android.view.Choreographer.doFrame(Choreographer.java:1079) at android.view.Choreographer$FrameDisplayEventReceiver.run(Choreographer.java:1646) at android.os.Handler.handleCallback(Handler.java:958) at android.os.Handler.dispatchMessage(Handler.java:99) at android.os.Looper.loopOnce(Looper.java:230) at android.os.Looper.loop(Looper.java:319) at android.app.ActivityThread.main(ActivityThread.java:8919) at java.lang.reflect.Method.invoke(Native Method) at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:578) at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1103)
END of stacktrace
Thread info
Name: main ID: 2 State: RUNNABLE Priority: 5 Thread group name: main Thread group parent: system Thread group active count: 32 Thread time: 0 hr 5 min, 5 sec
END of thread info
Device info
Report ID: 14f3b073-a751-49aa-9a7b-222db9bf0e15 Device ID: 88a115ded4d03269 Application version: 69 Default launcher: com.sec.android.app.launcher Timezone name: Pacific Standard Time Timezone ID: America/Vancouver Version release: 14 Version incremental : A546WVLS7CXE1 Version SDK: 34 Board: s5e8835 Bootloader: A546WVLS7CXE1 Brand: samsung CPU ABIS 32: armeabi-v7a, armeabi CPU ABIS 64: arm64-v8a Supported ABIS: arm64-v8a, armeabi-v7a, armeabi Device: a54x Display: UP1A.231005.007.A546WVLS7CXE1 Fingerprint: samsung/a54xcs/a54x:14/UP1A.231005.007/A546WVLS7CXE1:user/release-keys Hardware: s5e8835 Host: SWDK6120 ID: UP1A.231005.007 Manufacturer: samsung Product: a54xcs Build time: 1715231961000 Build time formatted: 08-05-2024 22:19:21 Type: user Radio: A546WVLS7CXE1,A546WVLS7CXE1 Tags: release-keys User: dpi User IDs: N/A Is sustained performance mode supported: No Is in power save mode: No Is in interactive state: Yes Is ignoring battery optimizations: Yes Thermal status: STATUS_NONE Location power save mode: MODE_NO_CHANGE Is device idle: No Battery percentage: 91 Battery remaining time: 31-12-1969 16:00:00 Is battery charging: No Is device rooted: No CPU Model: N/A Number of CPU cores: 8 Up time with sleep: 509 hr 22 min, 56 sec Up time without sleep: 340 hr 53 min, 28 sec
END of Device info
Exit reasons
Exit reason #1
Description: crash
Importance: FOREGROUND
Reason: CRASH
Timestamp: 22-06-2024 10:50:05
END of exit reason #1
Exit reason #2
Description: crash
Importance: FOREGROUND
Reason: CRASH
Timestamp: 22-06-2024 06:08:27
END of exit reason #2
Exit reason #3
Description: crash
Importance: FOREGROUND
Reason: CRASH
Timestamp: 21-06-2024 19:44:57
END of exit reason #3
END of exit reasons
Application info
App name: Jerboa Version code: 69 Version name: 0.0.69 Package name: com.jerboa Short package name: jerboa Flavor: N/A Signatures: nORRaWmGNmrBj18PL/p3svEr/s4= Is debuggable: No First installed: 27-09-2023 19:04:21 Last updated: 15-06-2024 01:37:51 Requested permissions: android.permission.ACCESS_NETWORK_STATE, android.permission.INTERNET, android.permission.READ_MEDIA_AUDIO, android.permission.READ_MEDIA_IMAGES, android.permission.READ_MEDIA_VIDEO, com.jerboa.DYNAMIC_RECEIVER_NOT_EXPORTED_PERMISSION, android.permission.READ_MEDIA_VISUAL_USER_SELECTED Default prefs: N/A Default prefs: N/A
END of Application info
Currently running foreground/background processes
N/A
END of running foreground/background processes info
Both the client and server connect to plex.tv which then brokers the connection between them. They essentially work as a very limited vpn between your clients and server.
This also gives them unrestricted access to the entirety of data passed between devices; and the ability to request any and all info from your server to be handed to whoever they chose.
This is also how they allow you to 'share' content/libraries with each others servers; through their public infrastructure that's collecting your information. Information they then sell to third parties to support their development and broker content agreements.
Yes. Emby was originally open source, but people would regularly fork it to remove the licensing. When they chose to go closed source; jellyfin forked that final release and has built from there.
Emby has a premier licencing system to support their development, instead of selling user data and making deals with content providers like Plex, or depending on OSS development/contributions like Jellyfin.
As far as I understand almost 80% of jellyfins current code is the original Emby code (called 'media browser' or 'MB' at the time), though to be fair, I haven't verified that claim.
The number of people I've come across that are absolutely baffled by the concept of port forwarding....
Then you add CGNAT ontop and things can get really complicated for someone unfamiliar.
Plex is a privacy nightmare that's slowly trying to faze out you having a server all together in favor of feeding you commercialized content from other providers; and many people find Jellyfin is far too unpolished/disorganized for a lot of debatable reasons I won't go into.
I've been quite happy with the middle ground: Emby. It's not FOSS, but is well polished with consistent development, great feature parity across platforms, excellent clients for pretty much every device I'd want to use, and a helpful community ready to assist with any problems you come across. They also have a heavy focus on privacy; with no third party partners collecting your info like Plex, and no telemetry sent from servers/clients.
The lifetime premier license I bought 7 years ago was well worth it.
Unless you are behind CGNAT; you would have had the same plug+play experience by using your own router instead of the ISP supplied one, and using DDNS.
At least, I did.