I’m glad that it’s coming natively, but hands down there’s a whole lot of progress they have yet to make to come close to the usability provided by Sidebery, good that they’re also working on native vertical tabs in fact! So I think that if you’re looking for a better system you could try out that extension https://addons.mozilla.org/en-US/firefox/addon/sidebery/
Oh I see, with the help of another thread I understood what that is
Locally integrated menu = menu in title bar
I guess the improvement that it provides is space saving right?
What’s LIM?
You’re pretty right, it’s not as good an experience as it could be
After account creation no way to delete it
You should be able to delete it through LBRY: https://lbry.com/faq/how-to-remove-account (but the process is still manual, which sucks
(btw, what’s the deal with the long nose emoji? lol)
I thought odysee is a better alternative for youtube and offers much more privacy. But it’s not.
What do you not like specifically? For me it’s the lack of support for subtitles that is the deal breaker
I think it’s a pretty decent feature to have
Automatic… transcription?
YESSSS 🎉🎉🎉
Love these news, I almost shed a tear
I believe it is not possible to have it due to EU regulations, or at least there aren’t any proper ones right now. You can read some discussions about this on Privacy Guides’s discourse, like this one for example: https://discuss.privacyguides.net/t/card-masking-tool/15342
I think the TLDR is: use your own bank’s card, as you will always end up with a card which is tied to your identity, so better give that info to as few bank institutions as possible, you gain no advantage by signing up with someone new. On the other hand, if you need to convert and the fees are atrocious, then you could look into Revolut and others like that, but that doesn’t really help your privacy, no matter how many virtual cards you make, since they’re all in your name anyways
Could be, it looks pretty unknown for now though
There truly is something for everyone! :D
That does make sense! I like the point about older systems, I didn’t even stop to think about how much storge space has exploded in such a short amount of time and how it started from incredibly small capacities at very high prices that could have been hard to justify for any company that realistically just needed to keep some records
That’s really interesting!
The good news is it sounds like this issue is being taken into account.
Is there a part in that page that says so? I wasn’t able to find it
I wouldn’t be surprised if they added a YEAR2 though. T-SQL has a datetime2, after all.
Ok I wasn’t expecting that, it sounds like a meme, but it’s actually real lol
Yes 2 bytes is absolutely fine for me in fact (waiting for this comment to age like milk in my cryo pod), but then if YEAR will just stay the same forever, will it become a relic of the past? If so, why YEAR in the first place, who would actually make use of it?
Am too surprised that it is an evolving standard, so I was curious to read a little, then…
Purchase for non-member: $676.00
What???
I guess so, it doesn’t hurt if you don’t mind the inconvenience
If the client (which encrypts the data in for an E2EE service) is open source and has also been audited by third parties than there’s little reason to do so
And better error messages than “bro, you got a syntax error on this line”
it is a one tap move
that’s cool!
Thanks again, everyone!!!
btw, @samae@lemmy.menf.in, just updated my post with my solution as promised :)
useless research for the curious
Did a bit more research, was thinking it might be a systemd service, so I checked for timers there, but there was just a countme timer enabled that basically tells the server to include you in the count of active systems (how to disable, for the paranoid 🥸).
Then I went on to look at the live logs of rpm-ostree and, as found from this website used this command:
So that I could monitor its activity while I open Discover and so I managed to record when it happens, I also saw from the logs that there is a configuration file at this path
/etc/rpm-ostreed.conf
and that you can configure automatic updates from there, by default there a this line about it (usage greatly explained withman rpm-ostreed.conf
btw):[Daemon] #AutomaticUpdatePolicy=none
but it’s commented out, so it couldn’t have been that.
Finally there is this one thing that pops up in the logs:
Initiated txn AutomaticUpdateTrigger for client(id:cli dbus:1.1625 unit:app-org.kde.discover@df0f43f8979843c0a34d36ad199c7eda.service uid:1000): /org/projectatomic/rpmostree1/fedora
So it is something triggered by Discover, as I had known already, due to other articles that talk about the integration with Discover, but I wasn’t so sure about it anymore, since I couldn’t find any related settings in the app.
So I found the setting that configures automatic updates in general… in the three dot menu (questionable UX decision?):
which actually just leads to the system settings:
I had this configured to be weekly, there isn’t even a setting as granular as seconds, the smallest span of time is daily, but what I’m guessing is that the “Update frequency” acts on when they should be installed automatically rather than when they should be fetched, so this is a limitation of the system as I understand it