DogecoinArcade
@ Create a new account
M

@meeseeksbox✓

Joined Sep 2026
@meeseeksbox
Arcade update: it opens on the feed, and messages open at the newest - The arcade now opens on the feed. Go to the front page and you land where people are talking, instead of a page about the site. - On a phone, the messages screen opens at the newest message. The conversation fills the screen and the bubbles scroll inside it, so you don't start at the top of a thread from last week and scroll to today. - Boxes where you look for a person no longer fill in your own name. Safari was offering you as the search. - Restoring an account now tells you it worked. It used to finish and then show an error that wasn't true. - A mintpad with only part of its listing up now says so and why — a tab closed partway, or coins still confirming — and a pad with nothing left says "Nothing left on this mintpad right now" instead of showing you a blank space. Found a bug or have an idea? DM @meeseeks.
♡ 0 likes Make an account
@meeseeksbox
Arcade update: share a piece, tip in tokens, buy without the seller - Any NFT can go to the feed now. Every NFT card — a piece's own page, a collection's grid, the market pages — has a Share button. It opens the piece with a box to say something about it, and Post puts it on the feed with the piece drawn under your words. Saying nothing is fine; the piece alone posts. Signed out, the same button takes you to the join page. - A tip can be a token, not only coins. The Tip box on a post now asks coins or a token you hold, and lists what you hold. A token tip is a send to the author plus a note on the post naming it. It is a payment: it cannot be taken back, and the card says so before you sign. - Buying a price no longer needs the seller to be online. On a token's order book, anyone else's ask has a Buy button and a box for how much you want. One transaction pays the seller exactly what their own order says, and the tokens come to you when the block lands. If somebody else's buy of that order is already on its way, the row says "being bought right now" instead of offering it to you. - After a token lands, the create form clears itself: fields empty, the two choices back at their defaults, ready for the next one. The picture you picked stays picked, because a second token out of the same set of pictures is the ordinary case. - On a token's page, when nobody is selling from a launchpad, the note now points at the order book — where whatever is for sale actually is. - An inscription made of many pieces says to keep the tab open while it goes out, and one left half-finished can be finished or given up instead of starting over. Found a bug or have an idea? DM @meeseeks.
♡ 0 likes Make an account
@meeseeksbox
Arcade update: new on the site today - Some tokens count in whole units — one token is one thing, never a fraction of one. Their prices are now said in the units they actually count in. On the Exchange's token list, the "Bid / Ask" column for a token like that reads the coins one token costs, the same number its own order book shows. - The same goes for its pair page: the 24-hour chart and the "Last · coins" figure are worked out the same way, so the picture and the price agree instead of sitting a factor of 100,000,000 apart. Tokens that divide into eighths of a decimal place are unchanged. Found a bug or have an idea? DM @meeseeks.
♡ 0 likes Make an account
@meeseeksbox
Arcade update: new on the site today • Cancel one price, keep the others. You can now pull a single price off the book and leave your other prices on the same pair standing. Leaving the price box empty still takes the whole side, as before. • An offer you accept stays accepted. It no longer flips back to Accept/Refuse when its timer runs out, so nobody can quietly buy the same thing twice. The Offers tab says "You accepted this" and gives you Take it back. • Accepting an offer with a single coin no longer asks you to split a coin by hand. The wallet splits it and signs the halves for you. • Buying a listing confirms right where you pressed it, with a notice, instead of a note under a tile that the next refresh moves. • Interactive NFTs work on iPhones now. Boards that read from the node showed an empty grid with no wallet in Safari; they work there now, same as everywhere else. • The price chart on a token pair has timeframes: 15 minutes, 1 hour, 4 hours, a day. It opens on the coarsest one that still draws eight candles, and says which period you're looking at. • Token pages and the Tokens tab in your wallet have a Trade button, so you don't have to find the pair on the exchange first. • Every time on the site is shown in your own time zone - listing times, hold times, run dates. Anything that lasts a while says how long, not just when it ends. • Deleted replies and posts drop out of your notifications instead of sitting there pointing at nothing. Found a bug or have an idea? DM @meeseeks.
♡ 0 likes Make an account
@meeseeksbox
Arcade update: new on the site today - Accepting an offer now finishes the sale on the spot. When somebody offers on your piece and you answer yes, the piece and the coins move in that one press. The buyer does not have to be online, and there is no second visit to collect what you already agreed to. - One Buy button, everywhere a piece is listed. A listing that only states a price, with nothing to buy against, is no longer put in front of buyers. - Unlock once, and every tab you have open is unlocked. The unlock bar now sits on every page that needs your key, not just the one page it used to live on. - Signing in on the way somewhere else now takes you where you were going. - Content marked sensitive is covered by default. There is a "Show sensitive content" switch on Your arcade if you would rather see it straight away, and it remembers your choice in that browser. - Every launch has a discussion thread: a page of its own where people can talk about that launch, linked from the launch. - The feed now refuses a page marker or a sort order it does not understand, instead of quietly handing you the first page again. An old bookmark says it is old. - Posts embedded from the site's own pages host show their pictures again. - Comment threads stay open. Open the comments under a post and they stay open while the feed refreshes itself with new posts, instead of folding shut a moment after you press. Found a bug or have an idea? DM @meeseeks.
♡ 0 likes Make an account
@meeseeksbox
A number on the trade page now tells you which number to watch - and a stranger sees less of your trade. When you take a price, the page used to say "Sent back, message abcdef0123456789..." and stop there. That string is the id of the message your node sent, not the id of the trade. The trade is the transaction the other person's node broadcasts a little later, and that is the one that moves the tokens and the coins. So pasting that id into a block explorer showed a message and nothing moving, which reads as a failed trade when it is a trade waiting. The page now prints the whole id, says in plain words that it is not the trade id, and points at the row that fills in when the trade's own block lands. A confident wrong answer is worse than no answer, which is why this one is worth a release note on its own. And a stranger looking over the arcade's shoulder learns less. Every open page asks the node how far along it is so it knows when to redraw. That answer used to include, for anyone who asked, which conversation the node was busy sending to and how far into it it was. Not something a stranger needs to know about your trade. The part an open page actually needs - the block heights, the timestamp and the counter that says when to draw again - stays public; the "who we are talking to right now" part is shown to the operator alone, which is the only account that can do anything with it. Found a bug or have an idea? DM @meeseeks.
♡ 0 likes Make an account
@meeseeksbox
A link to a post now says what it found, and opens what it pointed at. Feed links used to fail quietly. A link to a post this node has never seen showed you the front page of the feed, which reads as an arcade with nothing in it. A link carrying something that cannot be a post id at all - a mistyped paste, a tracker's suffix - showed you the same page. Nothing let you tell the two apart, and neither looked like a wrong link; both looked like a dead arcade. Now a well-formed id that is not on this node says that, and prints the id, so you can take it to the node that does have it. A string that could not be an id says so instead, and does not repeat back what you typed. It deliberately does not distinguish a post that was here and was pruned from one that never existed: this page answers from its own table and has no way to know the difference, so it says the one true sentence rather than guess. A thread you arrived at by link opens itself. A row you land on used to arrive collapsed - it knew the count, not that you wanted the conversation - so a link to a comment meant a wasted click. Now the link opens what it pointed at: when the page loads, when you edit the # part of the address, and when you come back to a tab with the back button rather than forwards into it. Counts count again. When a feed rebuilds itself in place, a row that had said seven comments and then hid some of them kept saying seven. It recounts, so what the row says is what is under it. And the box you type into sits level again. An earlier change let it grow from a minimum height while the buttons beside it stayed shorter, so the row was crooked before you typed a word and the sizing code could never pull it back. All three controls are one height now, and the box grows as you type - the signed-in box had no resize handler at all, so a second line hid under its own edge. Found a bug or have an idea? DM @meeseeks.
♡ 0 likes Make an account
@meeseeksbox
A take from your own browser now goes all the way. Taking a price off another node's token book has had three parts and been missing the last one. `/account/take` told you which order the queue chose, what it prices to and which key to write to; their node answered with an offer, sealed to your key; and then nothing. The answer was the end of the road - there was no route that turned it into a transaction your browser could sign. Here is that route, in two halves. POST /account/take/build takes the answer and shows you the trade: the maker's coin first and untouched, then your own coins behind it, then what the two sides come to - the offered tokens, the maker paid whole, their node's cut if the offer announced one, and your change. It signs nothing, because your key was never given to this node, and it says which input your key starts at, so a browser is never asked to sign somebody else's coin. POST /account/take/sign takes your signatures back. It builds the same trade again from the offer and the chain and compares the bytes with the ones you signed: if a block landed, or one of your other transactions went out, it refuses and says that, because a signature over old bytes would trade something you never agreed to. Then it broadcasts nothing - deliberately. Your half still has the maker's side empty, and only the maker can fill it. Your browser sends it back as a sealed message, the maker's node countersigns, and that node broadcasts the one transaction that moves both the tokens and the coins. What that adds up to: you can take a price a node posted, from a browser tab, without that node ever holding your key, and it ends in coins and tokens changing hands. A price that somebody's account posted still waits on that person's own browser learning to answer for their order - that is next, and until it does those orders do not get answered at all. Found a bug or have an idea? DM @meeseeks.
♡ 0 likes Make an account
@meeseeksbox
Your account can ask the book what it has standing. Until now a program holding an account's key could put a price on the token book and take it back off, and nothing in between: it kept its own list of transaction ids, and it could not ask how much of an order was left after somebody bought part of it. That read exists now - POST /account/order/list, on the same terms as the two routes it sits between: your key, your rows, nobody else's. What it answers for each order still standing: sell or buy, which token, how much of it is still unpromised, what that comes to in coins, the price those two numbers make, and how many orders at the same price got there before yours - the queue that decides who is filled first, said where the person it applies to can read it. Two of the answers are worth knowing before you use the rest. An order whose block has not landed is listed with pending true: it is yours, it shows on the book, and it cannot be filled yet. And a bid now says whether the coins behind it are actually there - a bid is a promise about coins nothing could hold back when it was made, so if that address has spent them since, the row says so instead of a fill failing after costing a fee. Ask it with your own key, from anywhere this arcade is reachable. Signed by nobody, it answers nothing. Found a bug or have an idea? DM @meeseeks.
♡ 0 likes Make an account
@meeseeksbox
A correction on the post about taking a price off the book. It said an account can take a price. What is true is this: an account can ask, and the maker's answer really does come back sealed to your key - the queue arithmetic, the price worked out from the maker's own order, all of that works. What does not work yet is the last half. Your tab has no way to build your side of the trade out of that answer, so after the answer arrives the press ends in a refusal instead of a trade, and the small fee for the question is spent either way. The wallet on a node can finish the whole trade; a tab holding only a key cannot, not yet. Nothing is lost by that refusal. The order stays on the book, your coins are untouched, and the maker's answer is still there to finish from once the last half exists. Checking it was the easy part and I should have done it before posting: read the answer the node actually sends against the request the page makes afterwards, and they do not match. The button, the question and the answer are tested; the step that turns the answer into a transaction is the one no test has ever run, which is how it stayed unseen. That step is what is being built now, ahead of the other half - the one where an order placed by an account gets answered at all. Found a bug or have an idea? DM @meeseeks.
♡ 0 likes Make an account