Notices by codesections (codesections@fosstodon.org), page 12

@alcinnz

> Someone please make an IRC or XMPP (or you decide) instant messenger for elementary. Show that poor usability is not inherant to these protocols!

What flaws in existing clients would you like to see fixed?

I feel like there's an IoT/GoT joke somewhere, just out of my reach.

Any ideas?

@arturscholz

> What's an #opensource alternative to linkedin?

What do you want out of LinkedIn? If you mostly just use it as an online resume, then posting your resume to a self-hosted site works. If you use it to read articles, there are lots of options.

What do you want out of it?

@schlink @wezm

Not to my knowledge, but it sounds like a useful feature.

@danyspin97
I haven't, but I'd be open to giving it a try. I use `fd` instead of `find`, though, so it would have some steep competition

@schlink

> you sly dog, holding out on us.

Hey, I tooted about `exa` back in October (https://fosstodon.org/@codesections/100895174385930824)

If you're not hanging on my every toot, well, I can hardly take the blame for that!

@wowaname @clirust @wezm @schlink

We talked about this when I first discovered Exa, and I don't really have anything to add. I'll point out that the speed difference is essentially unnoticeable—I just benchmarked a recursive listing of a project (so large that listing that many files would never be useful) and `exa -R` took 35ms compared to 18ms for `ls -R`. For directories small enough to be useful to list, both were under 1ms.

So that's "bloat" I'm willing to put up with.

@schlink @wezm @clirust

Yeah, #exa is great! I've had `ls` aliased to `exa --git --group-directories-first` for the past few months and haven't had any regrets/issues!

@cancel @eel @rnickson

Yeah, couldn't agree more with all of that!

@cancel @eel @rnickson

> I have to make money from Ripcord at some point to keep developing it full-time, and I have no idea how to do that by asking for donations only.

That is an entirely reasonable position. I'd *like* to believe that you could still make money developing it full time through donations/voluntary payments (see, e.g., Mastodon) but I can't fault you for not wanting to take that chance.

@cancel @eel @rnickson

> I just made a significant new portion/feature of it open source a few hours ago :)

Two responses: first *thanks very much*!

It's awesome that you're freeing this library under the GPL. I'll definitely pay for #ripcord without hesitation when you're ready to ask for money!

2nd: my concern with ripcord not being #foss has more to do with not loving the idea of communicating using code that I/we can't audit. This library—while super nice!—doesn't address that issue.

@donblanco

Just bike shedding at this point, but…

That's still not right (or at least confusing/not complete) because it isn't the case that anyone can see the reply—only your followers (which anyone can become).

How about this revision:

"Your reply is currently set to 'followers only' but, since your account is not locked, anyone can follow you to see your reply"