I’m blue, da ba dee da ba daa Da ba dee da ba daa, da ba dee da ba daa Da ba dee da ba daa, da ba dee da ba daa Da ba dee da ba daa, da ba dee da ba daa
🇨🇦
I’m blue, da ba dee da ba daa Da ba dee da ba daa, da ba dee da ba daa Da ba dee da ba daa, da ba dee da ba daa Da ba dee da ba daa, da ba dee da ba daa
Depends on where I’m scrolling and how long.
In a specific community? Usually sorted by ‘new’.
‘Subscribed’/‘All’ feeds? Generally starting with ‘Hot’ then moving to ‘new’ if I start to run into a bunch of content I’ve already seen.
WOW.
I can understand making a mistake in the website design, leaving such a vulnerability; but to shove it under the rug and ghost the people that reported it???
The TSA and DHS are begging for an incident.
Glad Ian Carroll+Sam Curry made the info public. Maybe that’ll be the push needed to actually fix this.
So, for the slow people in the back… (me)
Copyleft = permanently open source? Ie, you can’t take the open source code/project and make it closed source? (or build a new closed project off of it?)
Or am I misunderstanding?
That’s a fair solution.
I’ve just got remote devices syncing to my local server. From there Borg handles encrypted historical backups of that server which can be sent offline/offsite.
I like borg because of its insane de-duplication and compression algorithms. I’ve currently got ~480GB of data being backed up, with 16 historical copies going back 6 months: that entire archive takes up 303GB of space currently. Without the de-duplication and compression that’s 7.76TB of data.
I used to use RDP from Android to my Windows 10 pc constantly. Since switching to Debian, I haven’t gotten around to getting that working again. (Debians out of the box RDP solution gives me a black screen on the remote device)
Instead I’ve been using ssh a ton with JuiceSSH for a terminal. X-Plore for GUI managing files between local(android), ssh, gdrive, dropbox, and many more locations all in two tabs you can swap between and copy/paste/move files as if it’s all one big file system.
Finally I use Folder Sync to keep all of the userdata files on my phone backed up to a folder on my server via SSH. Images are synced immediately on creation, and everything else is backed up on a schedule.
(my phone’s always connected to a private VPN keeping it within my LAN and able to reach things like my SSH server, without exposing them to WAN)
The only thing I really miss having RDP for is the occasional website that refuses to play with a mobile browser. Hotmail/Outlook (I know, I should really change to someone not trash for email) for example will not let you edit inbox rules via a mobile browser or their mobile app. (even with ‘request desktop site’ enabled). You have to use an actual desktop browser for that. :(
Otherwise I do pretty much everything from mobile.
Poorly.
Any idea when a fix might make it into Jerboa?
This is getting really frustrating to deal with every day…
/edit; ask and you shall receive… Woke up to a new update. Fingers crossed it fixes this crash :D
You only amass that kind of wealth and power by stepping on the backs of those you deem beneath you.
Billionaires are a cancer on society.
The IMEI is potentially useful as it’s a device identifier, but generally doesn’t matter to anyone except your carrier.
On that note; the carrier may be able to tell you when that IMEI first became associated with your phone plan. My phone plan long pre-dates the last like 6 devices I’ve had so they’d have that history for many of them.
That’s not a database you can search whenever you’d like though; that’s a call and ask nicely.
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
Been a while since it was updated; but I used to use Win32DiskImager for reading/writing rpi cards.
I had a couple cards fail where they wouldn’t throw any errors during the actual write process, but once on to the verify step (checking that what was written to the card matches the source file, after writing) then they’d fail. Data hadn’t been written correctly, but it wasn’t reporting failures during writes.
Perhaps this is your issue? Not sure I’d trust those cards regardless.
They aren’t offering to do it, just asking if it’s what you want.
Gotta check and be sure you’re being annoyed as much as possible.
Perhaps. Unless you consider multiverse theory: The idea that the act of traveling to the past splits the timeline into two realities. One containing the original (to your perspective) timeline with the event(s) that caused you to travel back, and a second where you’ve arrived in the past to alter those events and the results there of.
Not sure I believe it, but it’s a theory none the less.
Or maybe it’s only possible to travel forward in time. Closer to our current understanding of the universe.
Assuming time travel exists: is it possible to alter the past?
If an event occurs, and you decide to travel back in time to change/prevent that event: It has no longer occurred in the way that caused you to want to change it; thus you never travel back to change it, and it does occur…
deleted by creator
Perfect. Capping is the better long term solution, but an expansion plug will do the job.
“a crazy thing” thanks plumber… Real helpful.
As long as the vertical pipe above it isn’t plugged, you should be fine to just plug that offshoot. It’s part of the vent stack for that drain, which is why it smells like a sewer. Presumably there was something else plumbed in there to drain out at somepoint, but has since been removed.
Not when you’re terminated with cause.
Committing crimes on the clock is more than enough reason to fire someone. Dudes incredibly lucky he was asked to resign instead of being fired and charged.