Post #1417550

2022-11-10 14:40 UTC

In the olden days, people in charge of institutional IT probably would have just gone ahead, give it a try, see what happens. In today’s “professionalized” IT setups, that likely requires a feasibility assessment, a user requirement study, a policy draft, a multi-year budget prognosis, and endless meetings (probably forgetting some) before the first stone can be laid. By which time Microsoft 365 offers Mastadon instances, which defeats the whole centralization idea. Apologies for the sarcasm.

Replies (3)

@emmatonkin@mstdn.social 2022-11-10 15:33

@hvdsomp Very nearly exactly this except also a) they first insist we already have a solution b) they then rather smugly argue that for security reasons they can't share and which we wouldn't understand, decentralised online anything is right out anyway and c) the Microsoft "solution" turns out to be Sharepoint/Teams wearing a funny hat and disguised in the manner of a Scooby-Doo villain, and if it isn't instantly forgettable it is only because using it gives you nightmares.

Open ##1417551
@jasongreen@mastodon.social 2022-11-10 15:49

@hvdsomp As somebody who works in higher ed IT, data governance rules create an environment where decentralization is hard to deal with. Auditors will hold you accountable for the security policies of systems you connect to. Unless you make completion of a security and data governance questionnaire a precondition of federating with an instance, you have a potentially big mess.

Open ##1417552
@olyerickson@fosstodon.org 2022-11-10 15:50

@hvdsomp Occasionally the institutional "process" stumbles into good decisions. Example: recently our university adopted #DSpace; much laughing all around as the team started to explain it to me and I cut them off, telling them I was there at its beginning! 😜

Open ##1417553