81–90 of 137 posts
Earlier quoted context omitted.
"We're going to shut down the wiki starting xx/xx." Don't need to explain, don't need to make a fuss - just announce and move on.
Doesn't that also just open up a lot more community feedback/pushback? I'm thinking somebody saw it coming in any case and made the call.
This is bad, very bad. A complete and utter disrespect for people who poured in their blood and sweat in creating the content for them and for free. Migrating only "top" content is insufficient and so ignorant. The value of wiki is almost entirely in long tail. Vast majority of Unreal engine is undocumented where you get all kind of issues few have seen before. If it wasn't for the community creating content for them…
> Why can’t we put a read-only archive online currently? The Wiki, even in it’s read-only state, was presenting security risks, and it was deemed necessary to take it offline.
I always wonder why companies do stupid things—like this. At the very least, put it in read-only maintenance mode, with a big disclaimer at the top saying so. But to just destroy information, information about your own product , is…well, it's stupid. Profoundly so.
In my experience this sort of decision is always driven by sales / marketing people deciding they want to funnel the users into some other part of the site that nobody currently uses because it's not as good.
I never understand why companies do this. Its very developer hostile. Are they having financial problems? Surely Fortnite is keeping the lights on... Could be a signal of underlying management confusion/instability. Might need to reassess.
You could host that wiki for ten bucks a month.
This is bad, very bad. A complete and utter disrespect for people who poured in their blood and sweat in creating the content for them and for free. Migrating only "top" content is insufficient and so ignorant. The value of wiki is almost entirely in long tail. Vast majority of Unreal engine is undocumented where you get all kind of issues few have seen before. If it wasn't for the community creating content for them…
Looks like the post got updated with some reasoning: > Why can’t we put a read-only archive online currently? The Wiki, even in it’s read-only state, was presenting security risks, and it was deemed necessary to take it offline.
What am I missing here?
Earlier quoted context omitted.
It shouldn't be hard to save a static copy of the actual HTML and replace the dynamic site with that though. Or at least give others enough time to do the same.
Not that hard? You'd need to process each page then data mine it.
The thing that seems super strange to me is that they don't seem to have warned people they would do this, the first comment is > This isn't very helpful, Amanda! I know that the wiki wasn't optimal, but there were many wiki pages developers like me had bookmarked for years beacuse they contained comprehensive and easy information, which is now missing. Why not just keep the wiki read-only online? Just to retain the…
Lesson I've long learned: never bookmark anything. Bookmarks are to temporarily remember a URL, not to archive content. If the content is important or meaningful to you, save the page.
[0] https://addons.mozilla.org/en-US/firefox/addon/single-file/
Very frustrating.
Sounds like someone accidentally deleted it and they have no backup. Instead of admitting to not having a backup, they can just say it was intentionally shutdown, and ask their staff to salvage whatever is available from archives.
"After over a year in maintenance mode, the official Unreal Engine Wiki is now permanently offline."
It seems to have been a problem for some time.
"security risk" - So they're just trying to hand-wave a bluff at a huge community of developers? No one believes this. edit: also I feel bad for this community manager having to lie and apologize
I am the co-maintainer of an OpenSource project called AwesomeWM. I took down our wiki years ago due to: * Constant vandalism * Dubious user created content rendering computer non functional * Trolling edits to cause breakages to people copy/pasting shell commands * SPAM * Maintaining the wiki Before that we forced users to log-in for edits, then forced moderator approvals for everything, then forced moderator approv…
About maintaining wikis, that is indeed a problem. In addition, most wiki software I used has extremely clunky administrative tools which make moderation way more challenging than needed.
I used to maintain a tiny private wiki for a previous job, and even in a very small operation (10s of users), it was a disproportionately large maintenance burden.