←back to thread

433 points zdw | 2 comments | | HN request time: 0s | source
Show context
synapsomorphy ◴[] No.45659329[source]
Sharepoint is one of the worst, most bug-ridden softwares I've worked with.

It has a bug with Solidworks (3D design suite) that sporadically makes files completely un-openable unless you go in and change some metadata. They are aware of this, doesn't seem to be any limitation preventing them from fixing it, and it has sat unfixed for years.

Microsoft's cloud storage as a whole is an insane tangle where you never know where you'll find something you're looking for or whether it will work. Some things work only in browser, some only in the app, zero enumeration of these things anywhere.

Completely unsurprised and I'm sure there are many more vulnerabilities ripe for the picking.

replies(8): >>45659452 #>>45659548 #>>45659676 #>>45659769 #>>45659872 #>>45660153 #>>45660210 #>>45660325 #
eterm ◴[] No.45660325[source]
They've managed to mess up sharepoint even worse lately.

I went there to try to find where company meetings got recorded to.

I went to my sharepoint bookmark, which weirdly is www.office.com after some previous nightmare rebrand.

Except what used to be the way into your sharepoint files, is now just a full page copilot screen with no hint of where the fuck your files are.

Even though you've been visiting this bookmark for years, to get to your sharepoint files.

Ok, so you search bing sign into sharepoint.

Top result is office.com . You ignore it.

Next result is:

https://support.microsoft.com/en-gb/office/sign-in-to-sharep...

This links you to https://m365.cloud.microsoft/

Ok great. Nope! Redirects you back to copilot.

I do NOT want to ask copilot to dig out my files every time you want a file. I want to get back to the directory listing so I can find the directory listing to find the company meeting recording.

How does MS not understand that replacing all UX with copilot is not an improvement, and is not helping sell copilot.

replies(2): >>45665115 #>>45670971 #
1. cachius ◴[] No.45665115[source]
Did you find it eventually?
replies(1): >>45665352 #
2. eterm ◴[] No.45665352[source]
Yes, via an old way into the system that specified the correct subdomain and folder path that I found from an old teams conversation.

I've no idea how to find the "proper" way into the system.