Put it in the Signal chat!
Hmm, maybe I need to take another look through my settings (or perhaps I didn't clearly enunciate my issue), because when I click a thumbnail in my main feed it opens the link, rather than a larger version of the image.
I miss Sync for that singular feature of press+holehold on a thumbnail in the feed to show a full size image of said thumbnail.
Same here, though I do have one thing I miss from Sync: press+hold on an image in feed to make it full screen. Happen to know if there is a voyager setting to enable this functionality?
I approve of this message.
Rawr!
That seems to have done the trick. Thank you!
Thank you, all! No luck with any of these troubleshooting tips but it is good to know that I am not alone in my need to dismiss notifications.
Red dot on the settings icon
Since the recent update I have had a red dot with a number 1 in it on top of my settings icon, as if to indicate a new feature or something. After looking through most of the options, the dot persists. Any ideas as to which menu I need to look into in order to clear the dot?
the lawsuit is targeting three patents in particular. These primarily cover throwing an object in a specific direction to either summon a battle character or to capture a creature in the field
Better watch out, Ghostbusters. Your ghost trap might be next.
Does Ghostbusters count?
I have seen Scepter mentioned a few times lately.
https://www.sceptre.com/TV/4K-UHD-TV-category1category73.html
No CI CD, sorry. Just like @JASN_DE@lemmy.world I use it purely to store/archive
I don't think I did more than spinning up the Forgejo container. Using the same db container and everything.
Experts have shared two competing theories as to how hundreds of pagers could have exploded simultaneously.
One theory is that there was a cybersecurity breach, causing the pagers’ lithium batteries to overheat and detonate.
Another is that this was a “supply chain attack,” where the pagers were tampered with during the manufacturing and shipping process.
Pictrs permission error after migrating to new hardware
After a migration to new hardware, I am receiving the following permissions error from Pict-rs.
The old hardware was using 991:991 and I did not catch it until after first run and the problem now persists after a chown -R 991:991 volumes/pictrs.
Can I salvage things? I'm not worried about saving any Pict-rs data, so I'd even go for some guidance as to the possibility of "resetting" Pict-rs.
undefined
lem-pictrs | Error:
lem-pictrs | 0: Error in database
lem-pictrs | 1: IO error: Permission denied (os error 13)
lem-pictrs |
lem-pictrs | Location:
lem-pictrs | src/repo/sled.rs:84
lem-pictrs |
lem-pictrs | ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ SPANTRACE ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
lem-pictrs |
lem-pictrs | 0: pict_rs::repo::sled::build with path="/mnt/sled-repo" cache_capacity=67108864 export_path="/mnt/exports"
lem-pictrs | at src/repo/sled.rs:78
lem-pictrs | 1: pict_rs::repo::open with config=Sled(Sled { path: "/mnt/sled-repo", cac
Ad blockers save lives!
Is this one of those 'username checks out' situations?
"mission accomplished" and what not.
I'd do the same 8 hours a day, but I'm taking Fridays off as well, tyvm.