post could be first posted on twetch at 6:27,
the tx gets broadcast at some point
hits the mempool
then BB picks up the tx at 6:31
Post by 1JcRRk…79XP
oh boy mempool must be alcohol
twetch#15875 6.7y
no-one ever mentions He only admits to loving you when He is drunk
What the chain says
- Block
- 967 554
- Time
- 2026-09-20T06:48:54Z
- Signer
- 1JcRRksn5vgR4266FX7Dyx5xyZq28G79XP
- App
- twetch
- Type
- reply
- Content type
- text/markdown
Fields the transaction did not carry are omitted. Open the payload to see the bytes as stored.
Signed by
1JcRRksn5vgR4266FX7Dyx5xyZq28G79XP UnverifiedReplies (16)
for twetch broadcasting tx's is not a duper priority TBH
or should not be
I even think it would be nice to have a 30 second edit time delay before comment gets broadcast, just for typos
but then
I also don't understand why twetch are still chasing social on chain instead of crypto social
this is a huge problem
Ironshirtz 2w
computers very easily have 10 seconds time difference
even when they sync to the same clock
time is not perfect across the internet
data transfer is not instant
God wills it
We went through it all with ANNE
and now literally have ANNE time to keep nodes in sync
234 879 sat
@0 what is a huge problem is this screenshot is 52KB
the cost to post is 1,398 sats
the image in the screenshot is just 6KB big
but costs 2.191 sats to post
make it make sense
235 155 sat
I even think it would be nice to have a 17 min time delay on when an entry was actually made.
i thought UTC was +12 @5937
This thread is longer than one page shows. Open a reply to see what follows it.