Craig Small ๐Ÿ… is a user on social.dropbear.xyz. You can follow them or interact with them if you have an account anywhere in the fediverse. If you don't, you can sign up here.

Craig Small ๐Ÿ… @[email protected]

Here's an idea: a music album full of random collaborations between Mastodon musicians. Let me know if you're interested and I'll come up with a game plan.

#music #mastomusic

Quick note for new Mastodonians:

If you try to follow someone and get an hourglass, it means they have to approve your follows.

It is not a reflection on you if this doesn't happen immediately. Notifications about this aren't in the same window as the usual "someone followed you" default notifications.

It's not like Twitter's thing. It's Masto's own thing, and some of us are a bit more security-conscious than others, and some of us are slow to review our follow requests.

<3

#newbie #advice

Last Call of the year at #IETF:

The IESG has received a request from the Sunsetting IPv4 WG (sunset4) to
consider the following document: - 'IETF: End Work on IPv4'
<draft-ietf-sunset4-ipv6-ietf-01.txt> as Proposed Standard

Death to #IPv4! :-)

How will #mastodon not become absolutely horrible when everybody joins?

Introduction

Internet name arjaybe
Terrestrial name Jim Bowering

I like #writing #novels
#greencomet trilogy done
D/L from my blog

I like #creativecommons
My books are CC-BY-SA

I like #freesoftware
I use Free Software to work

I like #selfpublishing
All self-published

I like #blogging
greencomet.org/

I like my #motorcycle
1981 BMW R100

Also #science, #art, #music...

Thank you for your attention

rjb mastodon.club/media/GGWQUWI5MK

let's just make it an official internet rule that 99% of blockchain usage are complete bullshit and the author has no clue what a blockchain is

Aw man Twitter is doubling the chocolate ration to 280 characters

how will Mastodon ever compete

is this the end for Mastodon

only third round venture recapitalisation and a pivot to fidget spinners can save Mastodon now

Current #MadTooter progress:

- Rewritten from scratch, using Redux and React-Router, among other things.
- Logging in now works correctly, one does not need to refresh!
- At least some errors are handled.
- Nicer colors for in-toot links (mentions, URLs, hashtags, etc).
- Stuff that does not work, usually has placeholders.
- Image galleries were moved above the toot texts.
- Lots of other small tweaks all around.

It is deployed at algernon.github.io/mad-tooter/, if anyone feels like giving it a go.

I am being favourited by something that Google translates to "Walking penis bot".

I'm not sure if I should be offended or consider it a compliment!

๐Ÿšถ ๐Ÿ† ๐Ÿค–

Oh, and I also merged a PR for and didn't upset Jim with the git history!

I now have my 9 ids for the security issues in

The packages for sid and unstable are already uploaded, the backport is complete just waiting for the testing transition.

Upload of the backport of security changesets to the stable release is awaiting security team approval.

release 4.8.2 packages just been uploaded. This release fixes 9 security issues.

Stable release will follow shortly, once I have worked out the relevant changesets.

JSON not accepting a trailing comma is a design wart.

4.8.2 is now out and is a security and maintenance release.

This version fixes 9 security issues ๐Ÿ˜ญ
Which is a bunch of XSS and path traversal plus a SQLi.

wordpress.org/news/2017/09/wor

@Mastodon I'm not sure if it was ActivityPub or some other change but I am seeing more of a thread now instead of, say, 1/4 of the toots. That's a huge change for me.

Trying to chase down a bug that occurs on the bug submitter's computer and not mine (and I'm not even sure how it fails) is annoying.

Dealing with historical command line argument parsing and getopt functions is doubly annoying.

Chrome's private browsing is broken

This defeats the purpose of Incognito. If any website is able to tell you're browsing in private mode, then the browser is leaking data that shows it's not private

The #W3C error (approving DRM) could never have happened at the #IETF: 10 years after, we would still be exchanging hundreds of emails without making a decision.