Skip to main content

Site Navigation

Your Account

Choose Language

Discussion Topic

Feedback: Using FixBot in Answers

Hi! We've been noodling on using FixBot to help out with Answers, but I'd like to get all of your feedback on it.

Despite everyone's amazing efforts, we still don't have an answers to as many questions as we like. FixBot can help fill in the gaps where we have repetitive questions, low effort questions, or just didn't have the right expert on hand the day the question came in.

We are going to start with a few experiments:

  1. Prompting the user for more detail for their question
  2. Reformatting questions to be more useful
  3. Answering old, stale and unanswered questions. (Like this and this and this.)

When we answer questions as FixBot, we want to be respectful in how we do it. We're initially thinking of having FixBot post like any other community member, with posts that can be voted up and down.

What do you think? How can we make this helpful and additive to the community? What kind of safety checks would you like to see in place?

Reply to discussion Subscribe to discussion

Is this a worthwhile discussion?

Score 2
Add a comment

2 Replies

Most Helpful Answer

Historically I have always marked those weak posts as archive since nobody comes back. That said if I looked at those two I would consider the fridge one an archive and bury, the Xbox has potential. There needs to be sufficient context. The F3 code washer is borderline as it has something helpful, but not a lot of steps done - you'd need to assume no TSing.

As far as where I stand on it... As I have always said: there needs to be an AI disclosure, either if you give it a "profile" or make it standalone but include an AI disclosure stating it's to finalize a legacy answer. Beyond that, no harm no foul. However, I would propose one rule: it has to be old enough any moderator would agree the question is FUBAR aged. It shouldn't be done until the question is so old there's a 0% chance someone will do it organically. How I would approach it is something like this: Instead of automatically doing it at a threshold, we should have the option to do a ping like @fixbot to get it - it should not kick in automatically since a lot of posts with this issue were dead ends to begin.

As far as what I consider too old? 2-3 years in human land (with exceptions for posts with potential, but I will not touch them), but once it hits 4 years old I generally have always sent it to die via archive. If it hasn't been archived or a mod comes across it as a possible FixBot can do this post, I see no issue in bringing it back. HOWEVER I have one concession I want to see: Do not promote them to the top - a bot is filling the gap in. We should not be promoting AI answers as more valuable than a human response. This bot should also not earn reputation points. The results by far outperform anything from Gemini or SlopGPT, even Copilot.

One other point of concern: I have helped with things like BIOS passwords as I can and feel comfortable doing to - the machine has to be old enough I know it's a decommissioned unit. I will not reveal my threshold here, but I will say this much: I look at how many are on eBay. These require a lot of caution for theft assessment.

Was this reply helpful?

Score 3

2 Comments:

Thanks Nick! Yes, I agree that FixBot posts need to be clearly marked that way. We're planning on making a new user and having these posts come directly from the FixBot user.

In terms of not promoting these old posts to the top: that's reasonable, but we may have some system limitations to work through. I'll see what I can do.

I like the idea of tagging the bot to invoke it to weigh in, I'll look into that.

by

@kyle if it can’t be avoided that’s a concession I can live with. But ideally we avoid putting them on top because it might encourage bad ChatGPT answers competing with FixBot, as well as spam. Maybe it’s something we can lock right away if it becomes a pattern. Likewise if reputation points can not be avoid keep it off of the leaderboards and hard code it to stay off.

The bot should look at the age before answering to make sure it doesn’t take over something new. If it sees a post from 2018 with no helpful details it should refuse — likewise a 2018 era post with solid info gets an answer. I consider 2-3 years the limit of what is reasonable to fix as a human but if a bot is doing it I see little reason to not allow it to fudge 5+ years. It would save a lot of questions I personally would choose to condemn because it is old and will never see an accepted answer, or feedback.

If it is fresh all human options should be evaluated first. Even if it keeps a list of experts in certain matters that are known.

by

Add a comment

@kyle I actually like the idea. Let FixBot loose on the "old, stale and unanswered questions." That would tie up some loose ends and may actually still help people out by having solutions for their issues. I am sure you can "see" which one of the unanswered questions do still get looked at for an answers.

One of the concerns I have are the "low effort questions". I understand there are tons of those but those might be exactly what new users are looking for to answer in order to help them get their feet wet. Are you possibly running a chance of decreasing recruitment of human intelligence by having FixBot answer those? You know it's difficult to recruit new talent and the "regular " crowd is maturing quickly :)

Also, will you be monitoring the percentage of the current answer rate performed by human intelligence and compare that to the percentage once FixBot is fully integrated? My concern is that the answer rate could become even less. Do you have a cutoff for that so that iFixit Answers does not turn into something that is totally run by AI? How about giving the humans a month-long head start or something like that? Longer than that would really be of no value. Aside from cleaning up Answers, of course. If FixBot uses more energy than we (the Humans) do, make it work for it.

The older cousin iRobot has taken a lot of negative hits over the years for all those wrong deletion etc., I feel with should treat FixBot with a bit more respect and welcome the technology. Let's integrate and not segregate and let it earn its keep but show reward by treating it no different than any of us. Rep Points and all.

Like I said, I for one am all for it. As long as you all keep an eye on it so it doesn’t turn into a "human versus machine" and "I'm sorry, Dave, I'm afraid I can't do that" situation, let's go for it and see where it takes us.

Was this reply helpful?

Score 1

2 Comments:

Like I'm fine with rep points, but it shouldn't be competing with us. Use it as a way to clear stale questions, absolutely -- especially since the death rate is 100% once we get to a certain age bracket. If I can ping fixbot over moderate it out of existence (and it's a good quality base) I'm all for having a 2nd option.

There really needs to be a set of hardcoded limits - no questions under 3-5 years old when they're basically dead to us, and complex high risk ones are not touched. I would also say it's good to explain things like why you can't beat Chromebook MDM - we know (and I especially know!) but explaining how I pulled enough hackerman stunts in my teens on the early XP machines as context to validate the information is old. 2nd common covers the rest because of the character limit being fixed :/.

by

https://www.ifixit.com/Answers/View/9341... -- This is an example I consider too much for a bot - it needs the nuanced knowledge needed without being fed context like 3V 5.4L Triton, or having the poster tell us. Unless you know the series is 100% 3V or can use the VIN, you can't quickly tell from a glance.

The trick is this: “L” = 2V, “N” = 3V and the model year: 2V engines are typically before 2004; 3V engines are 2004 and newer, though some 2004 models may still be 2V.

As to the maturing part... I'm at the point I'm leaving most of the basic questions be for someone looking for credibility unless I can tell someone will be misled by a bad answer if it is likely going to be complicated somehow. I don't need it anymore -- I feel like me taking on a common question is an insult to some of the high level ones I've taken on at this point. I don't expect someone new to shrug at a 5.4 Triton and know about the 3V oil issue.

by

Add a comment

Join the discussion

Kyle Wiens will be eternally grateful.