Atemu

joined 4 years ago
MODERATOR OF
[–] Atemu@lemmy.ml 1 points 23 hours ago (2 children)

That will only work if it is reproducible. Given that it downloads random shit from the internet, that's unlikely.

To package this properly, you need to build a derivation that can use a lock file to bundle the deps into some sort of stable format. This is how go's vendoring works.

[–] Atemu@lemmy.ml 1 points 1 day ago

Their success is relatively easy to measure objectively by their effectiveness at protecting communities from i.e. subtle trolls or troll enablers.

Though one's opinion on topics can influence the ability to spot such scum in the moment, the "right" people/a good moderator will know how to do that despite their topical (dis)agreements.

[–] Atemu@lemmy.ml 2 points 1 day ago* (last edited 1 day ago)

Yo what the fuck it produces a high quality translation of the entire website in a snap if you just give it a link. Even Google takes another click and then a long load to do that.
I mean it appears to be quite literal sentence-by sentence translation, so certainly not what a professional translator would do but more than good enough for understanding purposes without any obvious flaws.

Mixing languages also works; German + English produced English + English. Though weirdly introducing yet another language just discarded that other language's section entirely.

You can translate from one language to itself and it fixes spelling mistakes without otherwise altering the text O.o

Using LLMs for this is actually quite a good move; this sort of thing is where they can actually shine. You don't need to be able to reason to translate, you just need to be able to abstract language constructs and that's precisely what LLMs do.

I managed to make the website de-CSS itself a few times, ran into rate limits through normal use(?) and got a few POST re-send popups but that's all stuff you'd expect from the first version of anything.

Whoa, I'm quite impressed.

 

Today, we’re introducing Kagi Translate. It’s not revolutionary - it’s simply a better translation service.

Our combination of advanced language models and precise output selection delivers translations that surpass existing solutions, including Google Translate and DeepL.

Here’s a comparison table for main features:

Feature Google Translate DeepL Kagi Translate
Quality Average High Very High
Webpage translation Yes No Yes (most)
Languages supported 243 33 244

*Quality ratings based on internal testing and user feedback
*Language count as of November 2024

For quick translations, documents, or daily browsing, the difference is clear in the first sentence.

Try it:

Try Kagi Translate with any text →

Translate this blog post into Spanish → (note the simple URL structure)

Using Kagi Translate

Add translate.kagi.com/ before any URL for instant translation. No apps needed. Access 244 languages with zero tracking. Install our browser bookmarklet for quick access.

KagiTranslate

Visit translate.kagi.com for direct use.

We will be bringing Kagi Translate soon inside Kagi Search as a widget for instant translation inside search results.

Kagi Translate is free for everyone. If you’re not a logged in Kagi user, you’ll encounter a simple captcha to prevent automated abuse - a small step that helps us maintain quality while keeping the service free. Kagi members get direct access without captchas, integrating seamlessly with their existing workflow.

Limitations

We do not translate dynamically created content (eg. pages where content is loaded with JavaScript) or paywalled pages.

Kagi Translate uses a combination of LLMs, selecting and optimizing the best output for each task. While this creates immensey powerful translation capabilities, it can occasionally lead to quirks that we’re actively working to resolve.

If you encounter issues or want to suggest improvements (or just want to share your most ridiculous Google Translate fail), please send us feedback. This is our first release and expect many improvements down the road.

Next

This isn’t just about better translation. It’s about raising standards in everyday tools. We believe that privacy and quality can coexist, that powerful tools don’t need to track their users, and that the best technology should simply work without compromises for the user.

Kagi Translate joins our suite of tools (‘treats’): Small Web, Universal Summarizer, and FastGPT alongside Kagi Search and Orion Browser.

Transform your internet experience - become a Kagi member. Access the world’s most powerful search engine and help create a future where digital tools serve their users – not the interest of third parties or advertisers.

 

Announcing Kagi Translate

Never get lost in translation again. Today, we launch Kagi Translate, offering superior translations across 244 languages.

Key features:

  • Higher quality translations than Google Translate and DeepL
  • Zero tracking, no apps needed
  • Free for everyone (Kagi members get captcha-free access)

Try it now at translate.kagi.com or read the announcement post.

Kagi on mobile

We've added search buttons to our homepage to make it easier for you to choose your search type on mobile:

Install Kagi for Android and help us reach 5,000 installs needed for Kagi to submit application for Android choice screen.

Kagi iOS app is currently pending Apple review.

What else are we working on?

We are currently working on Kagi for Teams plan. This will allow you to bring your entire team or organization to Kagi. We'll have two options available: Professional and Ultimate tier, with fair and flexible pricing (inactive team members do not pay). We expect to launch in two weeks. Let us know if you would like to test this earlier by emailing support@kagi.com.

Improvements and bug fixes

Bangs

This release includes several new bangs and a significant cleanup of older ones. You can read the full changelog here. These changes were driven by our community, and we appreciate all contributions to our open source Bangs repo!
Here's a preview of our latest additions:

  • !attack: search site:attack.mitre.org
  • !jsr: jsr.io
  • !fast: moved to FastGPT
  • !javadoc: Java 23 API docs, docs.oracle.com/en/java/javase/23/docs/api/search
  • !startech: startech.com
  • dropout: dropout.tv

Kagi in the wild

Here is this week's featured social media mention:

Tag our account or use #Kagi when mentioning us in your posts!

[–] Atemu@lemmy.ml 1 points 3 days ago (2 children)

You'd typically think the abuse that happens on a higher level than dumb spam which those platforms succumb to would be even worse, but I feel we're somehow in a slightly better position to regulate that on Lemmy because of the delegation of moderation to users rather than instance admins.

We "just" need a relatively small amount of the "right" people to effectively counter that.

[–] Atemu@lemmy.ml 1 points 4 days ago

That would be a reasonable explanation if we didn't get an admission this was done very much intentionally so, with only the inability to even build being an unintended side-effect from the founder and CTO himself.

I'd invite you to actually read the two comments they made in the thread I linked, I get the feeling that you didn't.

[–] Atemu@lemmy.ml 1 points 4 days ago

Two posts up from what I posted: https://github.com/bitwarden/clients/issues/11611#issuecomment-2424865225

Hi @brjsp, Thanks for sharing your concerns here. We have been progressing use of our SDK in more use cases for our clients. However, our goal is to make sure that the SDK is used in a way that maintains GPL compatibility.  

  1. the SDK and the client are two separate programs
  2. code for each program is in separate repositories
  3. the fact that the two programs communicate using standard protocols does not mean they are one program for purposes of GPLv3

Being able to build the app as you are trying to do here is an issue we plan to resolve and is merely a bug.

[–] Atemu@lemmy.ml 4 points 4 days ago

Nah it's not news that their ethos has been fading away for a long time now and that Mozilla just really isn't what it used to be a decade ago.

[–] Atemu@lemmy.ml 1 points 4 days ago (1 children)

I find Lemmy in general tends to lean quite authoritarian autocracy-ish; that feels more like a reflection of the general user base.

I don't like that in the slightest to be clear but I do think it's true.

[–] Atemu@lemmy.ml 4 points 4 days ago (4 children)

Right now, it's definitely a good thing it's not popular. We are not in any way shape or form ready for the spam that popular platforms receive.

[–] Atemu@lemmy.ml 1 points 4 days ago (1 children)

“Oh, but there are no journalists!”

Good? I don’t want endless ragebait posted in my feeds.

I don't think that's the kind of "journalism" your strawman desires.

[–] Atemu@lemmy.ml 20 points 4 days ago

This is the Mozilla foundation, not the Mozilla corp. The latter has the deal with Google; the former couldn't make that deal even if they wanted to.

[–] Atemu@lemmy.ml 60 points 4 days ago (5 children)

the idea of putting people before profit feels increasingly radical

What. The. Fuck.

 

Leveling up our infrastructure

This Sunday at 6am UTC, we're making a step forward on our production infrastructure.

After years of faithful service, our original database server is being replaced with significantly more powerful hardware.

Expected downtime: 10 minutes

Protecting young minds: Enhanced video safety for families

Your children deserve better than clickbait and shock value. We're making it happen with advanced video controls.

Family account owners can now shape a safer, cleaner video experience for family members:

Authentic thumbnails

  • Replace misleading clickbait with actual video screenshots
  • See what you're really getting before clicking
  • End the bait-and-switch

Clean video titles

  • Choose between title case or lowercase formatting
  • Create a consistent, distraction-free experience
  • Focus on content, not hype

Example (click to enlarge):

To access these options, navigate to: Settings > Parental Controls (section: Video Search Settings) or click here.

Why this matters

Recent research confirms a disturbing truth: children's video searches frequently expose them to inappropriate content, violence, and frightening images. We believe our children deserve better. Kagi's new parental controls help parents better manage the video content their children are exposed to, reducing the risk of exposure to inappropriate content and creating a safer online experience for them.

Help us protect more young minds - share your thoughts on making this protection available more broadly to all plan types. In case you wonder why we did not make this option enabled by default - video thumbnails and titles serve as a marketing tools for content creators, and changing them unilaterally would introduce us as a biased intermediary on a matter that is still in the air. This could have a negative impact for publishers and potentially conflict with our mission to "humanize the web". It is a delicate issue, and this is why we had propagated the control over this to the user level, as with all personalization features in Kagi.

Custom Assistant Bangs

Launch your Custom Assistant instantly from anywhere with a Bang shortcut. Simply set your preferred command and you're ready to go.

This seamless integration means your Assistant is always just a keystroke away, whether you're researching, writing, or exploring new ideas.

Improvements and bug fixes

  • We fixed many issues causing interruptions with the Assistant. please let us know if you see any further issues.
  • Standalone bang shortcut ignores snap #5083 @tuesday
  • Timer shown for unrelated query #4103 @azdanov
  • Duplicate video results #4306 @loloriz
  • Z-index on icon covers tooltip #4849 @bebowilson
  • Custom bangs that override builtin bangs no longer work #5148 @avkiselev
  • Focus address field after clicking reverse image search button #4906 @tuesday
  • Override the ai downranking if you are searching ai images #5082 @Thibaultmol
  • Quick answer weird code block formatting #4770 @timo
  • Background for Advanced search in dark mode is too light #4586 @eirk
  • Keep focus on the search field upon accepting suggestion #4973 @xdc
  • Pricing page translation typo #4596 @Albi
  • !gflights incorrect target #5132 @Connor
  • Untimely redirect when typing a verse #5107 @X145678908765
  • Assistant: Option to use Shift+Enter to send prompt instead of just Enter #2121 @Value7609
  • Enhancement Request: Customizable Multiple AI Assistant Prompts with User-Defined !bang Commands #2183 @ZarK
  • Assistant input text box stubbornly places itself under the keyboard #4902 @gunslingerfry
  • New Assistant - Touch Issues on Mobile (Dynamic Viewport Resizing, Covering Sources) #4835 @silvenga
  • Microphone on assistant doesn't work #5105 @sleepysnooze
  • Assistant web search gets stuck #5025 @azdanov
  • Typo in the FAQ #5079 @duck

Join the Kagi revolution in the wild!

Here are all the cool places you can find us at:

Use #Kagi when mentioning us in your posts! Which brings us to this week's featured post from social media:

We also have a Kagi Community Discord server where you can join our community for real-time discussion about the product and chat with other Kagi users. There is also /r/SearchKagi on Reddit - steadily growing unofficial community.

Thank you for being a vital part of our journey - your support inspires us every day, and we can’t wait to see where this adventure takes us next! 🙏

 

@brjsp thanks again for submitting the concern here. We have made some adjustments to how the SDK code is organized and packaged to allow you to build and run the app with only GPL/OSI licenses included. The sdk-internal package references in the clients now come from a new sdk-internal repository, which follows the licensing model we have historically used for all of our clients (see LICENSE_FAQ.md for more info). The sdk-internal reference only uses GPL licenses at this time. If the reference were to include Bitwarden License code in the future, we will provide a way to produce multiple build variants of the client, similar to what we do with web vault client builds.

The original sdk repository will be renamed to sdk-secrets, and retains its existing Bitwarden SDK License structure for our Secrets Manager business products. The sdk-secrets repository and packages will no longer be referenced from the client apps, since that code is not used there.

This appears at least okay on the surface. The clients' dependency on sdk-internal didn't change but that's okay now because they have licensed sdk-internal as GPL.

The sdk-secrets will remain proprietary but that's a separate product (Secrets Manager) and will apparently not be used in the regular clients. Who knows for how long though because, if you read carefully, they didn't promise that it will not be used in the future.

The fact that they had ever intended to make parts of the client proprietary without telling anyone and attempted to subvert the GPL while doing so still remains utterly unacceptable. They didn't even attempt to apologise for that.

Bitwarden has now landed itself in the category of software that I would rather move away from and cannot wholeheartedly recommend anymore. That's pretty sad.

 

@brjsp thanks again for submitting the concern here. We have made some adjustments to how the SDK code is organized and packaged to allow you to build and run the app with only GPL/OSI licenses included. The sdk-internal package references in the clients now come from a new sdk-internal repository, which follows the licensing model we have historically used for all of our clients (see LICENSE_FAQ.md for more info). The sdk-internal reference only uses GPL licenses at this time. If the reference were to include Bitwarden License code in the future, we will provide a way to produce multiple build variants of the client, similar to what we do with web vault client builds.

The original sdk repository will be renamed to sdk-secrets, and retains its existing Bitwarden SDK License structure for our Secrets Manager business products. The sdk-secrets repository and packages will no longer be referenced from the client apps, since that code is not used there.

This appears at least okay on the surface. The clients' dependency on sdk-internal didn't change but that's okay now because they have licensed sdk-internal as GPL.

The sdk-secret will remain proprietary but that's a separate product (Secrets Manager) and will apparently not be used in the regular clients. Who knows for how long though because, if you read carefully, they didn't promise that it will not be used in the future.

The fact that they had ever intended to make parts of the client proprietary without telling anyone and attempted to subvert the GPL while doing so still remains utterly unacceptable. They didn't even attempt to apologise for that.

Bitwarden has now landed itself in the category of software that I would rather move away from and cannot wholeheartedly recommend anymore. That's pretty sad.

 

cross-posted from: https://lemmy.ml/post/21519137

I recently switched from a MBP to a Framework 16 as my primary laptop and one thing I immediately noticed was that I was unable to stop kinetic scrolls in Firefox by laying my fingers onto the touchpad. It'd just slide by unimpeded. You could work around this by counter-scrolling a little rather than holding still which is how I've been coping with it but it's suboptimal to say the least.
(As are many things in the Linux touchpad experience. Linux desktop developers really ought to use a macbook for a little to get a sense for how to do this properly.)

This was caused by Firefox' use of GDK3 to implement its windowing and input needs which does not support hold gestures.

GDK4 does support them but, as I understand it, a port of Firefox to GDK4 would be a ton of work and there isn't really much desire for it as GDK4 doesn't offer many real advantages over GDK3 as Firefox doesn't use classical GTK widgets or anything and only really uses it for basic input/output primitives.

A backport to handle hold gestures in GDK3 too was attempted but, in classic GNOME fashion, it was rejected.

The implementation now somehow gets events from the touchpad directly via wayland somehow from what I could gather but if it works, it works.

You can try this out in the latest nightly builds.

 

I recently switched from a MBP to a Framework 16 as my primary laptop and one thing I immediately noticed was that I was unable to stop kinetic scrolls in Firefox by laying my fingers onto the touchpad. It'd just slide by unimpeded. You could work around this by counter-scrolling a little rather than holding still which is how I've been coping with it but it's suboptimal to say the least.
(As are many things in the Linux touchpad experience. Linux desktop developers really ought to use a macbook for a little to get a sense for how to do this properly.)

This was caused by Firefox' use of GDK3 to implement its windowing and input needs which does not support hold gestures.

GDK4 does support them but, as I understand it, a port of Firefox to GDK4 would be a ton of work and there isn't really much desire for it as GDK4 doesn't offer many real advantages over GDK3 as Firefox doesn't use classical GTK widgets or anything and only really uses it for basic input/output primitives.

A backport to handle hold gestures in GDK3 too was attempted but, in classic GNOME fashion, it was rejected.

The implementation now somehow gets events from the touchpad directly via wayland somehow from what I could gather but if it works, it works.

You can try this out in the latest nightly builds.

 

Better image search with AI-generated images detection

Last week we got quite clear and direct feedback that we need to do something about AI-generated images that started creeping up in the image search.

You asked for it and we delivered!

We are enhancing our image search with a new ranking algorithm and an AI image filter. These updates prioritise authentic, human-created images and downrank AI-generated content. Users can also opt to exclude AI-generated images entirely.

Learn more about Kagi's AI image filter here: https://help.kagi.com/kagi/features/exclude-ai-images.html

We will continue actively improving this feature based on your feedback.

Improvements and bug fixes

The Assistant

  • We've enhanced the Assistant mobile experience with several updates, including improvements to the thread view and header navigation
  • Kagi Assistant v2 mobile threads menu #4725 @frin
  • Kagi assistant gpt LLM not working #5055 @ash
  • Assistant Tooltips are Hard to Click #5037 @silvenga

Celebrating Our Community

At Kagi, we’re all about community, and nothing has made us prouder than seeing the incredible photos our members are sharing online of their Kagi swag! Whether you’ve posted a picture of your free t-shirt or a sticker proudly displayed on your laptop, we want to take a moment to say thank you. Your support means the world to us.

The story:

We were thrilled to celebrate our first big milestone: reaching 20,000 loyal members who’ve stuck with us through this adventure. To show our appreciation, we've sent out free t-shirts and sticker packs to those first 20,000 supporters. Earlier this month, these members started receiving their packages and excitedly shared photos across various socials. Here’s a snapshot of just a few:

For anyone who missed out, don’t worry! You can head over to the Kagi Store and snag your first-edition Doggo t-shirt. We’ve got four fantastic designs, each one representing our determination to build a better, more ethical and more human web.

Help us reach our next milestone: 50,000 members

As we gear up to reach 50,000 members, we’d love your help in spreading the word!

We don't rely on ads to drive our growth; instead, we depend entirely on word-of-mouth marketing and community recommendations. This grassroots approach means that every conversation you have about Kagi, every post you share showcasing your swag, and every mention you make to friends and family has a real impact. Your enthusiasm helps us reach new members who share our vision for a better web. Let’s make our next milestone one to remember.

Where to find and tag us on the social web:

We also have a Kagi Community Discord server where you can join our community for real-time discussion about the product and chat with other Kagi users.

As we move forward, we want to reiterate our commitment to continuously improving Kagi for all our members. Your feedback and engagement are invaluable as we strive to create an even better experience. Thank you for being a vital part of our journey - your support inspires us every day, and we can’t wait to see where this adventure takes us next!

 

Hello, Kagi Fans!

We know it's been a few weeks since our last update, and there's a good reason for that. The entire company took a break from the usual routine to fly to Barcelona, Spain, for our annual retreat - a chance to reenergize and refocus for the exciting journey ahead.

But don’t worry, it wasn’t all fun and no work. In fact, we’ve got a pretty exciting update for you today. The retreat gave us fresh inspiration, and we’re ready to bring some of those new ideas to life starting right now.

Launching the official Kagi Android app

We're delighted to announce the launch of the official Kagi Android app! This marks an important milestone in our mission to make Kagi Search more accessible and encourage more people to try it out.

https://play.google.com/store/apps/details?id=com.kagi.search

The app allows users to begin using Kagi Search immediately right from the first launch (no account needed!). For those with existing subscriptions, signing in is seamless, enabling access to all Kagi features.

Additionally, the app includes native homescreen widgets, providing one-click access to search directly from your homescreen.

If you use an Android device, go check it out! We've simplified the process of sharing Kagi with your network.

Additionally, a recent EU ruling presents a significant opportunity for Kagi. Google is now required to include any search engine that meets specific criteria, such as having an app with over 5,000 installs, in the default list for Android and Chrome — install the app today and help us meet the criteria!

Stay tuned for more exciting updates coming soon!

Introducing Snaps

Snaps are an innovative search operator that allows for site-specific searches directly from the search bar. By simply typing @ followed by the designated site bang, you can limit your search results to a specific website. For example, to search on Reddit or HackerNews, you can enter:

  • @r winter boots which translates to winter boots site:www.reddit.com
  • and @hn vim emacs to vim emacs site:news.ycombinator.com

This feature was made possible thanks to the contribution of our user @tuesday ( #1231) on Kagifeedback!

This will work with any bang that Kagi support, including custom bangs you define. Kagi Bangs are open source, we welcome your contributions!

Universal Summarizer for Chrome

Universal Summarizer is one of the most-loved Kagi treats. The extension is now available for Chrome - Download it here!

We had to split it out of Kagi Search extension for Chrome due to rules of the Chrome store. Kagi Universal Summarizer is available to Firefox users via Kagi Search for Firefox and is natively built into the Orion browser.

The Assistant - 30 day update

It's been 30 days since we launched the Assistant, and we're excited to share a range of new updates with you.

Upload functionality:
We're excited to announce that you can now upload a variety of local files directly to the Assistant! This new feature allows you to add multiple files in a single prompt. Here's a list of supported file types:

  • Text files: .txt, .md
  • Rich text documents: .pdf, .docx, .pptx
  • Tabular data files: .json, .csv, .xlsx, ...
  • Images: .jpeg, .png, .webp, ...
  • Audio files: .mp3, .wav, .m4a, ...

Additionally, you can add a URL to have its contents summarised or to pose questions about it.

Stop button
We've introduced a Stop button that allows users to immediately halt the Assistant's streaming output.

Mobile improvements
And also made several enhancements to our mobile experience, and there's even more on the way!

Plus many other Assistant improvements

  • Give assistant a PWA manifest #4734 @Thibaultmol
  • Add Stop button for AI assistants #4034 @andrew-rivera
  • Multiline assistant queries on mobile #4693 @fxgn
  • Added Llama405b model to the list of available models in the Assistant
  • Assistant v2 Text Input Form increases with use #4799 @DaJonas
  • Session Link for Kagi Assistant #4772 @melomac
  • Assistant V2 initial prompt text field doesn't scroll #4739 @Thibaultmol
  • Kagi Assistant UI Issues #4729 @emptyjar
  • Browsing to https://kagi.com/assistant when not logged in results in 404 #4765 @cmart
  • [firefox] text box in assistant text box can display funny at wrap point #4002 @sbeckeriv
  • Universal summarizer can't find transcript: yet finds transcript for slightly different URL edition #4451 @leftium
  • Assistant history vanishes temporarily after branching #4686 @Value7609
  • Assistant v2. Custom LLM settings not persistent. #4672 @flokerama
  • New Assistant Beta looks bad in Safari #4675 @Rudotel
  • Assistant does not respect lens when searching #4756 @double
  • Assistant - Broked Fonts #4837 @silvenga
  • Assistant not respecting multiple lines. #4764 @tombert
  • Opus 3 interacting poorly with internet access #4804 @artemvmin
  • Assistant (V2): make the 'send' button in the chat gray as long as the llm is still 'typing' #4738 @Thibaultmol
  • Claude models are confused about internet access in Assistant with Web Access #4843 @Nashwan
  • Model name is intersecting the assistant answer on mobile #4694 @fxgn
  • Completely innacurate assistant context #4667 @tinkling6961
  • Assistant - Inconsistant "New Tab" Behavior #4909 @silvenga
  • New Assistant - Asking to Search #4794 @silvenga
  • New Kagi Assistant has lost the ability to parse line breaks #4778 @orb
  • Impossible to copy the code while the response is still being displayede #4848 @kfbme
  • Assistant.v2 firefox issues with scrolling to bottom #4662 @zut
  • Assisant 'internet=off' is ignored #4965 @Thibaultmol
  • The buttons on the bottom of a thread (copy, regenerate, info) shouldn't be inactive depending on how far you scrolled #4831 @chris_20017
  • Assistant v2 Text Input Form increases with use #4799 @DaJonas
  • An unknown error has occured in assistant #4988 @oNco
  • Assistant mode adding redundant newlines on paste #4845 @pravinxor
  • Code font is giant on phone for assistant #4797 @tombert
  • Universal Summarizer dropdown values unreadable in Dark mode #4749 @Christoph
  • Assistant V2beta character display error #4673 @OxygenX
  • Assistant thread UI buttons on Firefox mobile don't work #4805 @tinkling6961
  • Paste an image in research assistant to chat about it #4028 @hadario
  • The Assistant input box isn't cleared when submitting a prompt using the microphone if the device keyboard has been used #4923 @laiz
  • Copy the search prompt to the assistant prompt when "The Assistant" button is clicked on the search page #5005 @webwalrus

Search improvements and bug fixes

 

cross-posted from: https://lemmy.ml/post/21154325

Write is a handwriting app that works on a lot of platforms including Linux which cannot be said about most handwritten note-taking applications.

More information and demo: https://github.com/styluslabs/Write/

I've used it for uni on a Linux tablet/convertible and it worked really quite well and has some nice convenient features for note-taking.

The UI looks like it's from android 4.something though ^^'

What I really appreciate about it is that its storage format are plain SVG(Z) which are extremely compatible. All you need to view your scribbles is an SVG viewer (i.e. a web browser) which basically every computer with a GUI has. Their website is in fact mostly just the output of their own app.

 

Write is a handwriting app that works on a lot of platforms including Linux which cannot be said about most handwritten note-taking applications.

More information and demo: https://github.com/styluslabs/Write/

I've used it for uni on a Linux tablet/convertible and it worked really quite well and has some nice convenient features for note-taking.

The UI looks like it's from android 4.something though ^^'

What I really appreciate about it is that its storage format are plain SVG(Z) which are extremely compatible. All you need to view your scribbles is an SVG viewer (i.e. a web browser) which basically every computer with a GUI has. Their website is in fact mostly just the output of their own app.

view more: next ›