Any way to mark a record as unread? about unread HOT 15 CLOSED

+1 for mark_as_unread!

from unread.

I've tried to wrap my head around this, but it feels like the solution proposed by @arusa should work, even with .cleanup_read_marks!, except for the fact that this method is now private.

@ledermann, could you chime in on this again?

The way I see it the read_mark(reader) method returns the latest read mark (actually, this is not true, it doesn't use .order on the relation and thus no order is guaranteed in e.g. PostgreSQL:

If sorting is not chosen, the rows will be returned in an unspecified order.

https://www.postgresql.org/docs/9.5/static/queries-order.html)

If we delete that ReadMark, a record is unread for that user. Isn't that correct?

I might be wrong because I don't exactly know how the Garbage Collector class of this gem works completely.

from unread.

@aried3r, @arusa The garbage collector .cleanup_read_marks! searches for the oldest unread record (if there is any). Then all read_marks before its timestamp are deleted and the global timestamp is moved. The cleanup is essential for this gem, because it keeps the number of read_marks as low as possible. I recommended to run it once a day (via a CRON job or similar).

Because old read_marks are deleted this way, we cannot mark a record as unread after a cleanup was done. Note: There are situations where it does work. Example: If you have an old unread record, the garbage collector cannot remove newer read_marks, so you can delete them manually to mark records as unread. But in a real world app, it's unlikely that a user keeps an old record unread for a long time.

So: Without big changes in the algorithm it's not possible to mark a record as unread.

from unread.

The gem manages a timestamp and a list of read items (which were read after the timestamp) for a every user. This is efficient for marking items as read. Sadly, marking items as unread is hard with this approach: If we want to mark an old item as unread, we have to move the timestamp to the past and have to insert lots of items into the list of read items. This is not efficient.

But perhaps the approach can be enhanced by managing an additional list of unread items. This would be a big change, but perhaps it's worth it.

from unread.

For a while, i found a way to do that: instead of set a model to acts_as_readable on created_at, i set it on updated_at. When i want to set a record as unread, i update your "updated_at" with Time.now. It worked perfectly.
@ledermann , what do you think?

from unread.

@leonardoafpinto I don't think your approach will work, because changing updated_at marks the record as unread for all readers, not for the current one only.

from unread.

My readable is a shared model among other readers, such as an email, for example. In this context, it worked for me, in this scenario.
But I agree with you that this will not work another business model.

from unread.

@leonardoafpinto You are right, if every reader is accessing his own scope of records (fully separated from other readers), changing updated_at should work.

from unread.

I suggest .mark_as_unread(for: :all), .mark_as_unread(for: current_user) and also .read_by(current_user). Right now I am going to destroy records matching current message.id and current_user.id.

Here is what I did:

  def mark_as_unread_except current_user
    ReadMark.where(readable_type: self.class.class_name, readable_id: id).each(&:destroy!)
    mark_as_read!(for: current_user)
  end

from unread.

For .mark_as_unread, why not just delete the record in read_marks table?
Use user_id readable_type and readable_id to locate the record and delete it.

from unread.

In the end, just wrote my own readmarks that sort by unread, don't need cleanups and basically just work. Here it is if you interested: readmarkable.rb

This is an optimized version where I removed polymorphic relation due to speed concerns since I needed it only for one model. But you get the idea.

from unread.

@sysout That approach doesn't work because cleanup_read_marks! will delete the record and set a global timestamp for the user. If cleanup_read_marks! has already been run, there's no ReadMark to delete.

from unread.

I am using devise for Users.
But when I register a new user, all the Posts are READ for the new user.
So I am looking for the mark_as_unread method for the new user.
I knew this is so wrong ....

How come?
Did I miss something?

from unread.

Seems like the best way to go about it for items that are shared between users is to use a join table as the model for determining whether or not something is read.

For example, you might have the following (p.s. none of this is tested so it may not work):

class User
  acts_as_reader
  has_many :participations
  has_many :conversations, through: :participations

  def unread_conversations
    Conversation.find(Participation.where(user: self).unread_by(self).pluck(:conversation_id))
  end
end

class Participation
  acts_as_readable on: :updated_at
  belongs_to :user
  belongs_to :conversation
end

class Conversation
  has_many :participations
  has_many :users, through: :participations

  def mark_unread_for(user)
    participations.where(user: user).first.touch
  end
end

from unread.

For me it works this way:
post.read_mark(current_user).destroy!

from unread.