Then leave that to every one else to deal with; don't make other people wear your tin-foil hat. Or just start your own community and call it "Dot's Offbrand Extravaganza" or something.
Ugh. Just link to Reuters.
Black Mirror didn't do that one, but American Horror Stories did:
https://screenrant.com/american-horror-stories-season-3-episode-2-daphne-ending-explained/
Which is surprising because that show normally kinda sucks. Got roped into watching it last year, and I forgot I was watching AHS halfway through and almost thought it was a new Black Mirror.
It's like we're on a speed run toward the near-future Charlie Brooker warned us about.
But TBF, "Hang the DJ" was one of the few Black Mirror episodes that wasn't a total downer.
Maybe I'm remembering early/beta Teams with rose tinted spectacles, but at the very least the silver lining was that I no longer needed to keep a separate Windows machine running just for work IM.
I even tried adding it to Citrix, but it refused to install on a server version of Windows.
We used to use it before switching to Google Workspace (don't get me started on how much I hate that), and Teams wasn't too bad. But it had two things going for it then:
- It was replacing Skype for Business which never should existed because it was so awful. Compared to SfB, literally anything was an improvement.
- At the time, it was basically a Slack clone that didn't have everything and the kitchen sink bolted on yet and was decently lightweight if you used the browser version.
The community banner and icon are both broken and seem to be hosted away from Lemmy World on fry.gs which I believe is/was the home instance for one of the original mods. That instance appears to be no longer functional.
Not sure how long they've been broken; I just noticed that when I flushed my cache recently they weren't working and then realized the banner and icon links the API returns no longer work.
"icon": "https://fry.gs/pictrs/image/c6832070-8625-4688-b9e5-5d519541e092.png",
"banner": "https://fry.gs/pictrs/image/1a1e9226-87cb-4499-94a7-d43b1e520e50.png",
Update: I did find the banner. ~~I don't have a copy of the banner~~, but I do have the icon in my instance's proxy/cache if you want to save it and re-apply it from Lemmy World.
Icon
Banner
Reddit is dead to me and blocked in my router, so I'm good sharing knowledge and cool stuff here.
Matrix also is close to checking all the boxes, but it wasnt clear how it works on mobile (Element seemed like the mobile app that was recommended).
I run Matrix, and it's pretty great. Though I would recommend Schildichat over Element for the mobile app. I had all kinds of issues with Element Mobile somehow screwing up the E2EE keys for my other sessions. Nothing seemed to fix it except removing my account from it completely. Switched to Schildichat and haven't had that issue since.
I read the PR. It seems more like a hacky bandaid rather than addressing the actual issue. But I digress.
It's also possible I misunderstood where/how the limit was being applied. My understanding was that it was limiting the response to 50 per depth (50 seems to be the arbitrary limit for most of the API's list endpoints). What I really don't want to do is have to paginate the request for the top level comments.
e.g. if a post has 100 comments, and say, 60 of them are top-level, I much prefer to be able to get all 60 in one go. Depending on the total number of comments provided in the getPost call, I dynamically set max_depth higher (3-5) or lower (as low as 1) and fill in the deeper comments manually with a "show more" button. The exception is if linking directly to a comment where it uses the path to calculate the exact depth to fetch.
finding one with a chain of over 50 in a row is even more rare. Such a thread would be clunky to display in the main comment tree anyways
I'm working around that without pagination, but it's a low priority fix since Patrick's Law come into play. It's like Godwin's Law except it says that once a comment thread gets deeper than 9, it's a slapfight that's best avoided.
I've got a laundry list of reasons, but suffice it to say that pretty much every third party client I've ever used has been miles ahead in UX and polish.
One example is that if the API throws any error response and lands you on an "Error" page (post removed, user deleted, etc), the whole UI is stuck there until you refresh the whole page (e.g clicking "back" updates the URL to your previous page, but you're still seeing the error).
293
Giuliani shows up to vote in Mercedes he was supposed to give to poll workers
(www.theguardian.com)
259
Marjorie Taylor Greene is now adding lasers to her Hurricane Helene conspiracy
(www.thedailybeast.com)
view more: next ›
I don't use the desktop app, but the mobile app has a setting for what to do with the original file:
I have different sync folders setup differently depending on use case, but I typically use option #1 as my "default".
Maybe when you setup the sync folder, you set it to delete the local files?
Also, is the OneDrive folder a "real" folder or virtual one? I've only used Google Drive for things like that, and the local folder just holds a skeleton of the contents and pulls from the network on-demand. It...does not play well with other sync utilities or even copying through robocopy.