The module imports feeds in a whole new entity now. I wonder why that is, and doesn't is make more sense to use a content type in stead? Imo it would make a lot of sense if the user could define a content type to be used by twitter (like "tweets"). It would be even better if any "tweet" created separately on the Drupal site could be tweeted directly on Twitter.

Anyway, that's just to point out that it makes sense to use a content type in stead of a separate entity. I probably have to do this anyway, so if the maintainers agree I'll create a patch. If not, I'll probably fork the module.

Comments

Fidelix’s picture

Fidelix commented

Honestly, it doesn't make any sense for the twitter module to use another content type. Entities are here so modules don't have to do that, having to deal with a lot of overhead that nodes bring.

juampynr’s picture

juampynr commented
Status: Active » Closed (won't fix)

Obsolete. Closing.