Sean Tilley
Sean Tilley
Sean Tilley
  last edited: Fri, 22 Sep 2017 14:08:55 -0700  
I think this might be the next big thing I focus on for #Askwise:

bod favorited something by dsh: I think this might be the next big thing I focus on for #Askwise:
  last edited: Fri, 22 Sep 2017 14:11:15 -0700  
Yay! My app #Askwise is now up to 100 commits, and I was able to merge this feature branch:

Lots of trials and tribulations, and I still have 11 issues to go. But the basic functionality is there, and I haven't given up yet!

Don't forget, it's #FreeSoftware #AGPLv3
kai favourited a status by
  last edited: Fri, 22 Sep 2017 14:10:54 -0700  
Looks like I have my work cut out for me. :)

  last edited: Fri, 27 Oct 2017 20:15:43 -0700  
I think I'm up against a polymorphic association in #Rails, and Jesus Christ, is it ever daunting.


Trying to fetch all answers made by a user for a particular question. Fetching the answers works, fetching the questions works. But I can't seem to do this in a way that question.query and answer.body are displayed together in a coherent fashion.

What I need is to display a question title with a  link to the question, then display the body of the answer.

Here's the gnarly display that I'm working with. Answers are a nested resource of Questions:

So far, I'm just faking it by displaying the question body instead of the answer body.
  last edited: Fri, 27 Oct 2017 20:16:26 -0700  
Trying to understand the mystery of the acts_as_taggable_on gem in #Rails. I feel like a huge dummy; not quite able to get tags to work.
I managed to stumble through it on my own, but thanks for the tip. ;)

I was mostly hung up on the proper convention to use, where to call certain things out, and telling the app to route things correctly.
 from Diaspora
I getcha. I sometimes manage muddle through these things by trial and error, but probably on things that are about 10% the complexity of what you're doing. I mean, like running a website that I've built on PHP code. I'm impressed with what I've done, given that I'm not a technical type person, but I really don't have much of an idea of how it works; it just does, somehow. And now I need to try to integrate some Javascript functions to do something new the client wants, and oh my - I have no idea.

I look forward to seeing how your project turns out!

ps: I've been meaning for some time to ask you to explain Red/Hubz to me. The concept sounds really good, but I can't quite understand exactly what it is. I'd like to be involved in it. But that's a conversation for another thread, don't want to disrail(i) this one,
 from Diaspora
Stumbling through and getting something working is an incredibly satisfying thing, though!
  last edited: Fri, 22 Sep 2017 14:15:12 -0700  
Not bad for a day of work! :D

#AskWise now supports Markdown, user accounts, questions and answers, a landing page, and some basic fallbacks if no content exists or someone isn't signed in. You can see what else is on my roadmap here:

Cool, AskWise now supports tagging! Took a lot of revisions to figure out what I was doing wrong, but the index will now properly filter against a linked tag term.

I think the next thing on the agenda will be full-text search. Of course, the temptation to build a sidebar of related questions is pretty strong too...
In fact the Hubzilla voting system only supports yes, no, and maybe on top-level posts. I started to build a question/poll interface a few years back but at the same time Diaspora came out with a totally incompatible mechanism. Then a year or two ago GNU-Social came out with yet another incompatible mechanism with either of those. At one time I partially federated the Hubzilla and Diaspora mechanisms for at least a few simple cases; but I think that was wiped during a merge and it never was completed. ActivityStreams2 has its own incompatible way of doing this (naturally). So if we were to try and federate with AskWise questions it would be another incompatible mechanism. Though frankly, AskWise isn't technically a polling structure (answers can be voted up or down, but the overall data structure is just post/comments).

Ultimately, upvotes and downvotes and emjois and likes and dislikes and concensus and event attendance can all be categorised as 'reactions'. What all of these protocols lack is a generalised 'reaction' interface which specifies the allowed reactions (and a way to define these) and whether it allows a free-style reaction such as a kitten emoji or an answer like 'none of the above'. In other words these should all be the same thing. We shouldn't need different incompatible facilities for likes/dislikes/attend/notattend/yes/no/maybe/emoji-reactions/polls/q&a.  That's the direction I'm headed once I get pubcrawl to a working state. I'll need this kind of interface to federate many of our current reactions with activitypub; otherwise every type of reaction is going to map to some other kind of data structure or object format and it's a huge duplication of effort.
Latest progress update - questions can now be tagged, and an index exists for seeing all questions with a given term. I've also updated the view so that questions associated with a tag may be seen with one another. I need to figure out the offset value, so that a question is not recommended on its own page, but I'm certain that I will figure it out.

  last edited: Fri, 22 Sep 2017 14:15:34 -0700  
I'm writing a StackExchange clone in #Rails today. So far, most of it works, but I am now up against The Dreaded Thing I Suck At, which involves associations.

I've managed to tie Questions to Users, and it works without incident - every Question page will properly represent who asked it. Because this association has been figured out, I can also show every question a particular person has asked. That's good!

Now, I have to figure out how to correctly tie Answers to Questions. Answers are also tied to Users, so I have to be careful about how I hook this together. I've definitely screwed up on this kind of thing before, so I'm taking extra measures to do this work in a separate branch. It's easy to get a little bit too confused and tangle everything up incorrectly.

Once I get the association logic (and controller logic) figured out, I should be able to embed an Answer response form into the show page for questions, and it should Just Work™.

You can see it here: