I’m missing emoji reactions (not replies), jeje
I’m missing emoji reactions (not replies), jeje
For some time the alternative is freetube, though I don’t like is electron, is what we can somehow reliably use
Sorry about that. I was not aware of other meanings. I’ll try to remember to use the complete “software” word instead of its acronym I was used to since the 90s… Hopefully under the context what I wrote doesn’t get misinterpreted. Thanks !
If talking about non proprietary kernels’ drivers, such as linux, then again, profit is what regulates it. No wonder why now nvidia finally cares about linux, being the most used kernels behind the cloud, behind servers of whatever. Meaning, it’s not profitable not to support linux now a days for Nvidia.
The other fundamental factor is lock-in, which is abused by some big corps, such as MS.
But the profit idea es even wrong, but it’s what we have been educated with. For an OEM, providing FOSS drivers or FOSS FW doesn’t mean to have less profit, but somehow it’s interpreted as such. And there’s also our culture, backed by corps again, that tends to make us believe that everything profitable enough has to be corporate secret, and if not, others would take advantage of you business. That way of thinking really prevents for more FOSS adoption at the OEMs level. I don’t agree with it. It might be the presence or lack of some HW features might be inferred by the drivers/FW, but it doesn’t mean your competitors will know how exactly you provide such feature, and even less how to make it with the performance you do. And usually once released, you really want to show off your features, your innovation and so on, not keep it secret. So in general, really see no issue for OEMs not to offer drivers and FW as FOSS, even as free/libre SW.
I can imagine OEMs offering FOSS drivers and FW, but that not being as convenient for the major players in the market, since that would risk their position in the market. Just a thought…
Remember the lock-in mechanisms by the corps that feel being threatened if open sourcing dirvers… Some of which no longer say it out loud, but still think GPLed licences are a cancer…
I’m not aware of any, do you mind sharing anyone, better if not requiring account?
BTW I can easily find blogs about p2p solutions for whatever, but not about p2p blogging solutions…
The issue with social networks is the account requirement. Even though decentralized, they still require servers with accounts. If you, to prevent not being able to access at some point included an email, and the server gets hacked, then there you go.
Perhaps is a mistake of mine, to think social networks are not anonymous enough. Maybe they are. But tracking mechanisms are so sophisticated now a days, than the need for an account make me think they won’t ever be. That’s why I excluded social networks. Perhaps it’s the only option as of Today though.
I have never bought the idea that free/libre SW in general is just not as easy, including GNU+Linux. I’ll leave out open source initially, and come back to it later, not because it doesn’t experience the same, but because corporate wide it doesn’t suffer the same fate. And linux itself is one of the most widely used kernel if not the most, it happens similarly to openssl, and so many other open source components. So I see no issue with linux adoption, I can’t think of any kernel more adopted than linux…
To me what has really affected free/libre SW is the monopolistic abuse of the corporations, plus their ambitions, and how in Today’s world, they have created the illusion that being a technologist is the same as being a technology consumer, which gets into the hearts of governments and education systems (more hurting, public education systems). Let me try some practical examples:
Paid SW might be more intuitive to use at times, I can understand that. There are paid developers making the UIs more intuitive and attractive, in the end it needs to be bought or massively consumed to get earning through its use. But if you look deeper, perhaps it’s not just that free/libre or open alternatives are non intuitive at all, perhaps people gets used to that UI when attending basic or high school, or college/university. Perhaps even when exposed to mobile devices even when they can barely walk. Everything else, different in nature, will look alien to the future “technologists”…
On a sad (lacking hope) note, I don’t think there’s any indicator of things changing. My only hope is changes in educational systems, which are nowhere happening, and not the parents, as mentioned they are already convinced that using google, ms, apple, oracle or whatever prepare their kids for the future and will make them the technologists of the future.
On a funny note, I would answer the motivating question with: Linux is so good that it’s actually most probably the most used kernel world wide, :)
What is implied with alacritty not being customizable, what is then .config/alacritty/alacritty.toml
meant for? That said, I’d argue kitty has hard coded what fonts can be used with it, though some might think this is good, but in my mind it’s a limitation.
At any rate, this is a matter of taste. I use alacritty with screen. Some might argue kitty is better because of tabs supports, and if that’s a thing for them, then that’s fine…
At any rate, again, terminal emulators are a matter of taste…
deleted by creator
XMPP, 🙂
The phone doesn’t poll, instead it goes to sleep, and gets awakened by the push notifications. Just like GCM/FCM ones. Part of the key thing, because not any one can self host, is that it requires very little information in comparison, and some providers are open source and even free SW. The one I use is ntfy, there’s the next cloud (next push), and not long ago you can use the conversation push service (up.conversation.im) through the Convesations xmpp client. I was aware of Conversations capable of becoming a unified push distributor, but actually was looking for it to use a unified push distributor instead.
But I was informed already it’s not necessary, and doesn’t make much sense, by being very low power consumer, even though it requires to keep unrestricted battery consumption on the background. So no issues by Conversations not supporting using a unified push notifications distributor.
I see. Thanks for clarifying.
ohhh, I see. Many thanks !
ohh, sorry, I didn’t noticed it, as you can tell…
If I may, what’s the issue with URLs?
Since this community is partially inaccessible due to some change in how URLs are handled
ohh, I see, is there a setting, besides unrestricted battery use, one can should set as well then? I remember another about background use, but can’t seem to find it…
This is the first post that clarifies why there’s no need for unified push notifications, but still conversations supports GCM/FCM push notifications. I seem though for those phones unified push notifications would help, the same way GCM/FCM does? At any rate, for battery purposes I got it’s not required.
Many thanks !
It depends on the distributor:
https://unifiedpush.org/users/distributors
And how much info they collect. I understand the ntfy requires is really bare minimum compared to what GCM/FCM asks and collects.
On mobile, it’s sort of a needed if you one doesn’t wand to use GCM/FCM which is really bad privacy wise, and particularly needed on peer to peer applications, because they tend to drain the battery…
Some other benefit is that for those who can, they can self-host ntfy, nextcloud with unified push provider, and so on…
On the list of apps supporting unifid push, I even see element (matrix), but I don’t identify any xmpp one:
Yeap, I noticed it being a unified push distributor, actually in its settings on can find the option to enable it.
OK, I won’t worry about battery usage then. But the argument about unified push notifications not being useful, but the GCM/FCM actually found useful is somehow hard to understand. But I understand what you’re saying about battery usage. Thanks a lot !
Ohh, thanks, I’ll try asking there…
BTW, before molly supported unified push notifications, it was also using websocket and that still required to enable unrestricted use of battery, as currently conversations does. Once I the unified push molly version showed up, such unrestricted use of battery was no longer needed. Websocket definitely is much better than GCM/FCM, but it implies, I believe more battery consumption, though perhaps not unbearable.
Jami was also using websockets and required to allow consuming battery on the background as well, and then moving to unified push no longer required that, but in the case of Jami, by being peer to peer, the effect is more noticeable.
All that to say, that other apps have moved to unified push notifications for better battery savings, even though they used websockets before, and curiously enough conversations does take advantage of GCM/FCM push notifications, so is not clear to me why disregarding unified push ones, but it’s always up to the developers/maintainers, and what they need/want to invest on… So that’s why I mentioned I don’t quite get what was mentioned on the github issue, though it was clear to me there’s no intention to provide the support.
Yeap, thanks a lot !
Just a minor suggestion. When looking for something different than what you’re currently familiar with, do so in very open minded way, hopefully no looking for clones to what you were used to, but willing to experience and learn new stuff (there’s no failure, just something new that had to be learned and experienced).
I know it’s easier saying than doing…
Looking for advice on giant communities is sort of hard, and in the end you won’t know what works better for you if you don’t try it. The open mind needs to come with some time to be able to play, and enjoy during the play, so it’s not a whole series of frustrations.
On this same forum (different threads/posts/converstions) I’ve read very different recommendations. Even though Manjaro has been recently getting a lot of bad reputation because of letting some certs expire, it’s still considered an “introductory” gnu + linux distribution. I’ve also read Mint is a pretty good “introductory” gnu + linux distribution as well, specially now that ubuntu has finally shown its inclination towards its snap store, rather than the good and solid dpkg + apt, which allowed it to grow on users to where it’s currently at.
I myself prefer rolling release models for distributions, and being as vanilla as possible, to be closer to upstream as possible. However I dislike systemd, which is just a personal taste, so I don’t have a specific recommendation. It used to be Manjaro offered openrc, but they dropped it, and the distributions I know are Artix (it has gui installers if that’s considered “introduction” level distribution, but one still need to handle the configuration mismatches with upgrades as with Arch), Gentoo (I wouldn’t say it’s not for starters, but for sure it has its learning curve, but more importantly you need to be aware that it’s a source based distribution), and Void. If you don’t really care, rolling release distributions, which might have an easy ramp up might be Manjaro as mentioned, and now I believe openSUSE Tumbleweed. maybe even fedora come close… Rolling release models might come even easier for newcomers, in my opinion, since there’s no need to think on what happens on major updates, but rather one needs to keep updating periodically, but hopefully the distribution helps supporting the safest and saner configurations natively so the user, and particularly newcomer to the distribution don’t have to deal a lot to get such safe and sane configurations, at least to start with. And that’s to me the important part to call it “introductory” distribution, easy installation might be part of it, but it’s hardly the majority of it, and this is perhaps the sad part of what I like about being as vanilla as possible, some distributions even take that as a mantra for configurations, and upstream developers don’t always have the safer, or the saner configurations by default. I believe Manjaro and some others take that into account to make things smoother to start with. Maintaining the distribution, keeping it up to date, being able to install stuff, has it’s learning curve, no matter the tools/frameworks to do so, and it might be harder if one has to deal with how to make things work because the software doesn’t work as it should (configuration required upfront), and it’s not hardened enough as well so the user needs to know that and do additional configuration upfront as well.