From gildarts to ~emersion/soju-dev
--- Trying this as part of the channel update command per IRC conversation. service.go | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/service.go b/service.go index b95f551..a9112ea 100644 --- a/service.go +++ b/service.go @@ -286,7 +286,7 @@ func init() { handle: handleServiceChannelStatus, }, "update": { [message trimmed]
From gildarts to ~emersion/soju-dev
This adds the option of detaching a channel by messaging the bouncerserv service. Format of the command is `channel detach <name>`. Partially resolves ~emersion/soju#37 --- service.go | 31 +++++++++++++++++++++++++++++++ 1 file changed, 31 insertions(+) diff --git a/service.go b/service.go index b95f551..7816c30 100644 --- a/service.go +++ b/service.go @@ -290,6 +290,11 @@ func init() { desc: "update a channel", [message trimmed]
From gildarts to ~emersion/soju-dev
On 7/8/2021 4:53 AM, Alexey Yerin wrote: > On Wed Jul 7, 2021 at 10:26 PM MSK, gildarts wrote: >> Rebased on most recent head, sorry for the third round here. > > This part should go into timely commentary after ---, otherwise it will > appear in the commit message. > Oops, my bad. Still getting used to the email based workflow. -gildarts
From gildarts to ~emersion/soju-dev
Rebased on most recent head, sorry for the third round here. This is adding a fallback for authentication to allow providing username, client, and network inside the password field. It splits on `:`, but only if the password fails to be recognised initially. Doesn't change the allowed characters in passwords. --- downstream.go | 31 +++++++++++++++++++++++++++++-- 1 file changed, 29 insertions(+), 2 deletions(-) diff --git a/downstream.go b/downstream.go [message trimmed]
From gildarts to ~emersion/soju-dev
This is adding a fallback for authentication to allow providing username, client, and network inside the password field. It splits on `:`, but only if the password fails to be recognised initially. Doesn't change the allowed characters in passwords. --- downstream.go | 31 +++++++++++++++++++++++++++++-- 1 file changed, 29 insertions(+), 2 deletions(-) diff --git a/downstream.go b/downstream.go index fee5134..d359321 100644 --- a/downstream.go [message trimmed]
From gildarts to ~sircmpwn/aerc
On 6/3/2021 8:39 AM, Ondřej Synáček wrote: > I am not sure if the channel on Freenode is maintained "officially" > from `aerc` contributor team but wanted to ask: Are there any plans > to move to Libera or not? > The official `#` channel was closed down and then seized by freenode staff and redirected to `##`. I don't see a aerc channel on libera, but the one on freenode definitely isn't official. -gildarts
From gildarts to ~emersion/soju-dev
On 6/3/2021 3:26 AM, Simon Ser wrote: > I'm still not a fan of shoe-honing the network name into the password > field. Putting it in the username or nick is already a hack. > > I'd rather see clients patched to support changing the username/nick. > I don't think clients should update their settings (ie. their > configured username or nick) when the server changes it. Yeah, that is fair. I might keep tinkering on this to use on my local instance just for getting it working for now. IRCCloud has relatively good reasons for not allowing changing username because of the abuse vector. There are already people who use them for abuse, but they are relatively easy to block because of the static ident
From gildarts to ~emersion/soju-dev
On 6/1/2021 3:53 PM, gildarts wrote: > Prompted by conversation on IRC about enabling tools like IRCCloud > to specify information inside of the password field, since they > don't allow configuring the username field, etc. Okay, ignore this patch. I need to send a v2 after I resolve some bugs. -gildarts
From gildarts to ~emersion/soju-dev
Prompted by conversation on IRC about enabling tools like IRCCloud to specify information inside of the password field, since they don't allow configuring the username field, etc. Doesn't prevent `:` user in passwords. This is adding a fallback for authentication to allow providing username, client, and network inside the password field. It splits on `:`, but only if the password fails to be recognised initially. --- downstream.go | 25 +++++++++++++++++++++++-- 1 file changed, 23 insertions(+), 2 deletions(-) [message trimmed]
From gildarts to ~sircmpwn/sr.ht-discuss
On 4/16/2021 11:07 AM, Страхиња Радић wrote: > On 21/04/16 09:45, gildarts wrote: >> How would that work? > > This is all hypothetical, but still there is a potential. A big tech > spying corporation could use any means it already uses to gather data about a > user. When a user accesses a server that is known to set the header telling > "not to gather information" (IDK, maybe information obtained by something as > simple as a crawler?), the user gets that habit associated with his/her "social > profile" or however else one would call it. The corporation could then, for > example, dedicate more resources/attention towards tracking the user, or use the > information in whetever other way it sees fit. It is a bit of data about a user