Notices by muesli (fribbledom@mastodon.social), page 36

@jlelse

Some say because I do, I have literally no spare time whatsoever.

I guess it all depends on the definition of "spare".

@cinebox

Well, thank you! Thanks to your feedback I improved the error handling a bit and just pushed it to git!

@cinebox

Ok, I see what's happening, I think: enter your instance URL including the scheme "https://".

@cinebox

Ok, I'm just improving the error handling for this dialog. Hang tight, should provide you with some more useful information in a minute.

@cinebox

Ok, time to gather some more information then:

Can you check the terminal if it printed out any error / auth URL there?

Which instance are you trying to connect to?

Do you have two-factor auth enabled?

@cinebox

I decided not to automatically open it, even though that may be a mistake. Not sure yet 😆

Click the label above the input field, it should open the authorization process in your browser.

@Gargron

Thanks Eugen, highly appreciate your feedback! You're probably right, I'll tweak the palette a bit.

Say hello to Telephant!

I've written a little Mastodon client for the Desktop - called Telephant - and am currently looking for beta testers!

Want to help out and don't mind compiling the app yourself? (Don't worry it's fairly straight forward and I've added detailed instructions to the README!)

Join me here:
https://github.com/muesli/telephant

Looking forward to hearing your feedback!

@Gargron Hey, quick heads up that I think I noticed a bug in Mastodon:

If you sign up for a new account, proceed to edit your profile and save it for the first time, it gets marked as a "Bot" even though I made sure this flag is not ticked in my settings.

Managed to reproduce this twice now.

@ConfusedNyan

Slow and gentle is the way to go. He is rather ticklish, so it may not last long... but it's oh-so-soft 😆

@clacke

When reality gets in the way of your development ethics 😂

@evilchili @felixthepope

@pro

Please be aware that if you start a reply with "Son", it makes everything you say after that sound a bit condescending.

Either way, it's great you managed to never fuck up one of your commits in all those years. As I've mentioned I don't blame anyone for using it, when they know what they're doing.

It still remains a good advice, especially for people who aren't as familiar with Git as you may be. I'm sure you've seen this being a problem before, even though you might not have caused it.

At least someone had the decency to leave a note.

@mjog There's no intention to shame anyone. As I said, it's fine to use it if you know what you're doing. As a maintainer I'd still appreciate it as an indicator that I should be extra careful when reviewing a change set.

Even if you're extra careful, who knows what has happened to your changes between reviewing them and typing "git commit -a". Knowing that someone manually signed off each hunk gives me a bit of extra confidence. That's all.

@mjog

If you're working in your own development branch, sure, go ahead. If you keep force pushing your branch in preparation of a pull request, then that clearly falls under "knowing what you're doing and being careful".

If you're working together with a team on a feature branch or preparing your pull requests with "commit -a", then we clearly have rather different attitudes towards collaboration.

@starbreaker

He does if you're being really careful and gentle. And oh my god it's so soft. So unbelievably soft.

How could you not fall in love with this guy :blobaww:

@mansr

I guess that falls under "knowing what you're doing and using it carefully". Also, easy enough to review.