Adolph (npub17eh…94rr) I was talking half of Husky but half generally. If you don’t like the developers decisions, you are free to not use its software, not to harass.
But if you are interested in why I may use or not Husky, I’ll explain my situation. It is fair, as you have kindly explained yourself.
The context is: I stopped using Husky (and any other mobile client) when one of my profiles that runed a Mastodon-powered software stopped working (I have one Akkoma-powered account and a Mastodon-powered one). At that time I decided to use them both directly from the browser and I have to say that I have been quite used to it.
The pros of using the native interface is that you get all the functionality. And I have to say that akkoma has tons of them that I like!
There are two cons, though. The first one is the performance. Using the browser is slower, as I has to load everything each time. The second one is the ability to switch accounts for a publication (in order to reply on it) that you have in the clients.
So I was thinking on using again Husky, although still doubting.
And here is when I saw your post. Being already doubting, it may have some impact, I must admit.
To be honest, I use plenty of software that is hosted in Github, so it won’t be fair if I reject yours only because of that. But, even if I use software hosted in Github, it really bothers me to validate M$ model. I think that generating dependency on a big corp for all our free software is a very bad strategy on the long run. And I will disclose here that I do think politically when I use software. I think that free software is a required tool to construct a fair world. If is not useful for the last, I am not that interested on it.
I have to say that inclusive language (at many levels) is important to me, and it is related to what I was saying before. If technical language has elements that are hostile for fraction of potential developers that are already under-represented in the field (and I can get why master-slave relation terminology is hostile), we should try to avoid them.
This has been a long post, sorry! But things aren’t simple and I wanted to give the picture as complete as I can. Plain words can be cold, sometimes, but I just want to add that I do appreciate your dedication and any of the reasons above won’t make the decision alone. Maybe I just got too used to the browser experience…
npub1up2…pf56
2024-01-31 11:49:43
in reply to nevent1q…geff
Author Public Key
npub1up2udq5tudvx92g7j3839538t45tffpd86gj97tc0tu3fefhcz9q2vpf56Seen on
wss://relay.noswhere.comPublished at
2024-01-31 11:49:43Event JSON
{
"id": "76ac9b7a86d9648cc0c3d87bc38b97433c9d77c97b6a248a269a7ab1e7bd4601",
"pubkey": "e055c6828be35862a91e944f12d2275d68b4a42d3e9122f9787af914e537c08a",
"created_at": 1706698183,
"kind": 1,
"tags": [
[
"p",
"f66e66bb2d91ad65b0b904021f7ef0a3dcab37f1c005a8fedd820a7f7d932762",
"wss://relay.mostr.pub"
],
[
"e",
"1450cd1e65cfd2089765c49747350b9e8dd072b3ea63a08dc7e63b9513f590fb",
"wss://relay.mostr.pub",
"reply"
],
[
"proxy",
"https://bcn.fedi.cat/objects/0cc97082-e26e-48f1-8dc6-6e94923653b4",
"activitypub"
]
],
"content": "nostr:npub17ehxdwedjxkktv9eqspp7lhs50w2kdl3cqz63lkasg987lvnya3qpx94rr I was talking half of Husky but half generally. If you don’t like the developers decisions, you are free to not use its software, not to harass.\n\nBut if you are interested in why I may use or not Husky, I’ll explain my situation. It is fair, as you have kindly explained yourself.\n\nThe context is: I stopped using Husky (and any other mobile client) when one of my profiles that runed a Mastodon-powered software stopped working (I have one Akkoma-powered account and a Mastodon-powered one). At that time I decided to use them both directly from the browser and I have to say that I have been quite used to it.\n\nThe pros of using the native interface is that you get all the functionality. And I have to say that akkoma has tons of them that I like!\n\nThere are two cons, though. The first one is the performance. Using the browser is slower, as I has to load everything each time. The second one is the ability to switch accounts for a publication (in order to reply on it) that you have in the clients.\n\nSo I was thinking on using again Husky, although still doubting.\n\nAnd here is when I saw your post. Being already doubting, it may have some impact, I must admit.\n\nTo be honest, I use plenty of software that is hosted in Github, so it won’t be fair if I reject yours only because of that. But, even if I use software hosted in Github, it really bothers me to validate M$ model. I think that generating dependency on a big corp for all our free software is a very bad strategy on the long run. And I will disclose here that I do think politically when I use software. I think that free software is a required tool to construct a fair world. If is not useful for the last, I am not that interested on it.\n\nI have to say that inclusive language (at many levels) is important to me, and it is related to what I was saying before. If technical language has elements that are hostile for fraction of potential developers that are already under-represented in the field (and I can get why master-slave relation terminology is hostile), we should try to avoid them.\n\nThis has been a long post, sorry! But things aren’t simple and I wanted to give the picture as complete as I can. Plain words can be cold, sometimes, but I just want to add that I do appreciate your dedication and any of the reasons above won’t make the decision alone. Maybe I just got too used to the browser experience…",
"sig": "712a4e07c1ddb6feb1fe3f282c478827bc6d0834b8ba7e5ea73b26a87e9758dddd34dd5d468d9ee895e2bc73d57ca621622b50a9e21691aa4d1841afa714bdef"
}