'Famous [computer science] paper rejections' -- http://www.fang.ece.ufl.edu/reject.html
♲ @email@example.com: A tale of two fires that nails where we’re at right now. We can raise a billion dollars to rebuild a tourist attraction but we can’t take care of human beings who need help.
PRIORITIES people. Maybe it’s time to re-evaluate ours.
Wow. Just wow. If you’re using #GoDaddy it might be time to re-think that.
'Becoming a professional software developer is accumulating a back-catalogue of regrets and mistakes' -- https://programmingisterrible.com/post/139222674273/write-code-that-is-easy-to-delete-not-easy-to
Enterprise LARPing with Blockchain™
RT @firstname.lastname@example.org @email@example.com @firstname.lastname@example.org Or from here: https://email@example.com/the-heist-how-big-blue-stole-blockchain
@cwebber @AceNovo @Gargron I don't really understand how any of the arguements against AP C2S don't also apply to micropub C2S. Micropub has create and delete, but ALSO update, AND it can do all kinds of 'post types' - according to the *microformats 2* vocab (which is managed on a wiki by a small community, rather than a W3C Rec like AS2) - which still may not correspond with stuff a Mastodon server would expect.
AP clearly specifies how servers should federate incoming activities [ctd]
please destroy my draft idea for improving bitcoin fungibility by helping wallets interoperate more easily:
of the 4 listed options for serializing this data, I only think the first 2 are viable right now (bip 124 is a more general solution, but is incomplete). not sure which one is preferable, due to tradeoffs made
Server run by the main developers of the project It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!