Any word on licensing? They mention that their Mastodon reimplementation is open source, but I see nothing about Rama itself.
Edit: Not open source. Seems the only place this is mentioned is in a Reddit comment, of all places. https://www.reddit.com/r/Clojure/comments/175tapf/announcing_clojure_api_for_rama_build_endtoend/kah5hfo/
As a Kagi subscriber, I've been very happy with their transparency in general. The feedback site is open to the public and Vlad and other staff members regularly engage in conversation about possible future features, limitations, and even business decisions in the Discord. It's been refreshing.
...which makes the response to this issue all the more frustrating and disappointing.
I think Vlad's comments in the original feedback thread were fair enough, but then later, in the Discord, I saw a lot of "let's move this to a private chat". They even changed their General channel to "slow mode" to prevent live conversations as this topic became hot. Now I see they were also deleting threads?! Ugh. That's not transparent at all. Not what I expected based on my previous experience with Kagi.
Oh, gotcha. I misunderstood and thought you were describing a Chrome-vs-Firefox difference specifically. Yeah, I can relate. I'm de-googling my life but I'm not sure I'll ever be 100% de-googled. I'm taking it bit by bit. I sign up for new things with different email addresses now and occasionally I'll change existing services if it's possible. But there's no way I'm going to go through my bajillion web site accounts and move them all.
I don't understand the problem. Google services work in Firefox pretty much the same way, yeah? Does Chrome integrate an authenticator app? If som you might want change your 2FA settings at https://myaccount.google.com/security . If you have an Android phone you can get push notifications on it, or you can also use third-party authenticator apps.
It would be great if the frontend and backend were separated with a unified API and you could simply choose a frontend/interface (Vivaldi) with whatever backend/engine (Gecko). That’s not how it (currently) works though.
Arc has floated this idea. Currently Arc is Chromium-based, but they say they've designed it to allow for swapping engines in the future.
IIRC, Edge had a similar feature for a while, allowing you to run legacy Internet Explorer tabs if a site required it. Not sure if that still exists.
Firefox syncs across devices as well, if you sign up for a Firefox account and enable sync. This works for bookmarks, logins, history, and you can even access remote tabs if you want. It's also easy to send a single page from one device to another.
On desktop, Firefox has an import feature that will pull your bookmarks and logins m other browsers (like Chrome) into your Firefox profile.
Even if you're neck-deep in Google services, Chrome doesn't do anything special.
A non-smartphone, that is, a cell phone like the ones that today’s parents had when we were young and with which we made calls and sent text messages, was enough for us, and it did not cause addiction.
That's not the way I remember it. Texting addiction was a thing. That's how Twitter became popular; it was basically a way to broadcast SMS to friends at first.
I guess it's a matter of degrees.
Ad-based services are the real problem here, I think. You don't hear people complaining about Wikipedia addiction.
All the time. Not always by choice!
A lot of my work involves writing scripts for systems I do not control, using as light a touch as is realistically possible. I know for a fact Python is NOT installed on many of my targets, and it doesn't make sense to push out a whole Python environment of my own for something as trivial as string manipulation.
awk is super powerful, but IMHO not powerful enough to justify its complexity, relative to other languages. If you have the freedom to use Python, then I suggest using that for anything advanced. Python skills will serve you better in a wider variety of use cases.
Not sure what you're seeing on your end, but I get a fairly lengthy article with graphs.
Thank you for saving me the trouble of investigating this as an option.
No reason to tolerate proprietary licenses when there are so many viable FLOSS solutions out there.
I'd go a step further and say "punk" is by definition political, and more specifically anti-authoritarian and non-conformist.
That said, this is a relatively new usage of the word. 100 years ago it meant nothing of the sort.
This is correct, albeit not universal.
KDE has a predefined schedule for "release candidates", which includes RC2 later this month. So "RC1" is clearly not going to be the final version. See: https://community.kde.org/Schedules/February_2024_MegaRelease
This is at least somewhat common. In fact, it's the same way the Linux kernel development cycle works. They have 7 release candidates, released on a weekly basis between the beta period and final release. See: https://www.kernel.org/category/releases.html
In the world of proprietary corporate software, I more often see release candidates presented as potentially final; i.e. literal candidates for release. The idea of scheduling multiple RCs in advance doesn't make sense in that context, since each one is intended to be the last (with fingers crossed).
It's kind of splitting hairs, honestly, and I suspect this distinction has more to do with the transparency of open-source projects than anything else. Apple, for example, may indeed have a schedule for multiple macOS RCs right from the start and simply choose not to share that information. They present every "release candidate" as being potentially the final version (and indeed, the final version will be the same build as the final RC), but in practice there's always more than one. Also, Apple is hardly an ideal example to follow, since they've apparently never even heard of semantic version numbering. Major compatibility-breaking changes are often introduced in minor point releases. It's infuriating. But I digress.