Show newer

Made a small PR to enable out-of-band oauth token support.

We basically had everything already in place, we just needed to tweak the redirect logic (by extracting it from the oauth server implementation we use) and add a handler to show the token nicely to the user via an html page:

https://github.com/superseriousbusiness/gotosocial/pull/889

Should be useful for bots that require an oob code, and for CLI clients like Toot.

this one goes out to all the kobolds 

rockussy

@kim we'd like 200k from an unknown investor so we can burn startup money like you're supposed to

hey does anyone instead wanna pay us gotosocial devs $80k/yr to close source our project and start making morally rancid decisions?

@kim like right now GTS has pretty bespoke build code, generating and splitting into different bundles etc, which is a usecase i'd rather put into it's own library github.com/superseriousbusines

it's still calling browserify at it's core to turn one type of code into another, but there's a lot of parts around it for livereloading, setting plugins, writing to different files etc

@kim kind of, I'm using browserify, which is nicer (and older) than webpack as the core bundler, but I'm building tooling around it for a variety of usecases. Currently my projects use either plain browserify, or budo/budo-express to add livereloading capability, but I'm hoping to simplify that all into a single API + dependency I can use in all my projects

YouTube: New release for you
Nora En Pure - Stop Wasting Time

wow way to call me out okay

so far 'fedifox' is my preferred name for it I think, but suggestions welcome

Show thread

cohost, cp 

mandatory content warnings:
- censorship

we must protect our fragile userbase terrified of even discussing having their child porn censored

~ cohost devs

Hello everyone!

We just made a bugfix release of GoToSocial: v0.5.2 Stunning Sloth.

This release fixes a couple of issues with domain blocks:

Now, domain blocks can be added in either unicode or punycode, and they’ll work either way.

Also, side effects for domain blocks will now be processed correctly in the background after initiating a domain block via the API or admin panel.

This fixes an issue where a domain block would be created properly–and enforced, don’t worry!–but side effects like deleting accounts from that domain, deleting follows etc, would not be processed. This meant you’d end up with account entries still sitting in the database, or you’d see that you were still being ‘followed’ by an account from a blocked domain, even though your instance was no longer sending or receiving messages from that domain. Silly!

If you had any domain blocks that weren’t processed correctly before, you can just unblock and reblock the domain, and the side effects will now go through :)

You can get the release from here:

https://github.com/superseriousbusiness/gotosocial/releases/tag/v0.5.2

Show older
Pixietown

Small server part of the pixie.town infrastructure. Registration is closed.