Codebuzz @www.codebuzz.nl

Follow

I'm going to stop putting things off, starting tomorrow.

Block / Report User

If this user/feed is violating this Pod's (yarn.meff.me) community guidelines as set out in the Abuse Policy, please report them immediately!

You are also free to Unfollow or Mute this user or feed. Muting will also remove that user/feed's content from your view and you will no longer see content from that user/feed anywhere.

@Codebuzz does not follow you (they may not see your replies!)

Recent Twts

Recent twts from Codebuzz

(#cs3mjwa) We cannot bulletproof it, no matter which solution we use. If somethings changes, most likely something breaks. However a Nick+Timestamp is fairly unique hash, even if someone for whatever reason had the same nick. For display nick@url would make that unique and recognizable again.


#gmctx4q

(#pqhbula) Well, as for a new UUID it’s a thought to combine the timestamp+username or timestamp+url to create a unique id. In this scenario I think the first would probably be favourable. This way if someone decides to use a different url (most likely they will stick to their nickname) UUID’s will still hold up.

Adding to that, we could implement a version variable in the meta, adapt code to either read the old or new format UUID, so older threads won’t break.


#zxzz7ta

(#lnlbnsq) Well I have been working on an update of Timeline, mainly improving speed. Getting a multiple of feeds can really become a big fetch. So I would advocate for ideas to maintain performance.

Regardings your points:

  1. Agreed, but at the moment date+txt creates the unique timestamp
  2. Preferably newest twt as the last line, will make for more structure.

#eween7q