cross-posted from: https://lemmy.world/post/47583791

Physical keyboard layouts were optimized for typing with ten fingers. Most virtual keyboards just copy the look of those physical layouts — even though the writing experience is completely different, since on a screen we're really only using one or two thumbs. On top of that, most of these keyboards focus on how the keyboard looks, and pay far less attention to how it sounds and feels.

With Honeyboard, I wanted to explore what it means to redesign a keyboard specifically for screens, and build the best possible writing experience around that. I focused on the essential core features that define what a virtual keyboard actually is:

• Write in your native script. Honeyboard ships with 122 languages and 295 layouts.
• A coherent experience for your senses. Organizational structure, visual, haptic, and auditory feedback all work together to make typing genuinely feel satisfying.
• Adapts to any device. Phone, foldable, or tablet — it looks and works perfectly on all of them, so it feels like a native part of your system.
• Fully local. It runs entirely on-device, with no special permissions required.
• Public domain. The code is contributed to the public domain, with a modular, clear structure, thorough tests, and documentation — so it's easy to contribute to or adapt yourself.

This isn't just another keyboard. It's a vision of what digital typing could look like in the future — and it already works today.

There's still some polishing and optimization to do, especially on the sound design, the layout sources, and the layouting algorithm, but none of that gets in the way of everyday use.

I'd love to hear what you think.

cross-posted from: https://lemmy.world/post/47583791

Physical keyboard layouts were optimized for typing with ten fingers. Most virtual keyboards just copy the look of those physical layouts — even though the writing experience is completely different, since on a screen we're really only using one or two thumbs. On top of that, most of these keyboards focus on how the keyboard looks, and pay far less attention to how it sounds and feels.

With Honeyboard, I wanted to explore what it means to redesign a keyboard specifically for screens, and build the best possible writing experience around that. I focused on the essential core features that define what a virtual keyboard actually is:

• Write in your native script. Honeyboard ships with 122 languages and 295 layouts.
• A coherent experience for your senses. Organizational structure, visual, haptic, and auditory feedback all work together to make typing genuinely feel satisfying.
• Adapts to any device. Phone, foldable, or tablet — it looks and works perfectly on all of them, so it feels like a native part of your system.
• Fully local. It runs entirely on-device, with no special permissions required.
• Public domain. The code is contributed to the public domain, with a modular, clear structure, thorough tests, and documentation — so it's easy to contribute to or adapt yourself.

This isn't just another keyboard. It's a vision of what digital typing could look like in the future — and it already works today.

There's still some polishing and optimization to do, especially on the sound design, the layout sources, and the layouting algorithm, but none of that gets in the way of everyday use.

I'd love to hear what you think.

Physical keyboard layouts were optimized for typing with ten fingers. Most virtual keyboards just copy the look of those physical layouts — even though the writing experience is completely different, since on a screen we're really only using one or two thumbs. On top of that, most of these keyboards focus on how the keyboard looks, and pay far less attention to how it sounds and feels.

With Honeyboard, I wanted to explore what it means to redesign a keyboard specifically for screens, and build the best possible writing experience around that. I focused on the essential core features that define what a virtual keyboard actually is:

• Write in your native script. Honeyboard ships with 122 languages and 295 layouts.
• A coherent experience for your senses. Organizational structure, visual, haptic, and auditory feedback all work together to make typing genuinely feel satisfying.
• Adapts to any device. Phone, foldable, or tablet — it looks and works perfectly on all of them, so it feels like a native part of your system.
• Fully local. It runs entirely on-device, with no special permissions required.
• Public domain. The code is contributed to the public domain, with a modular, clear structure, thorough tests, and documentation — so it's easy to contribute to or adapt yourself.

This isn't just another keyboard. It's a vision of what digital typing could look like in the future — and it already works today.

There's still some polishing and optimization to do, especially on the sound design, the layout sources, and the layouting algorithm, but none of that gets in the way of everyday use.

I'd love to hear what you think.

{ "id": 5716886805, "name": "PropaGandalf's Logo", "description": "PropaGandalf was here :)", "links": {}, "path": { "48": [ [ 499, 65 ], [ 492, 65 ], [ 492, 66 ], [ 490, 66 ], [ 490, 67 ], [ 488, 67 ], [ 488, 68 ], [ 486, 68 ], [ 485, 69 ], [ 485, 70 ], [ 483, 70 ], [ 483, 71 ], [ 482, 71 ], [ 482, 72 ], [ 481, 72 ], [ 481, 73 ], [ 480, 73 ], [ 480, 75 ], [ 479, 75 ], [ 479, 76 ], [ 478, 76 ], [ 478, 78 ], [ 477, 78 ], [ 477, 80 ], [ 476, 80 ], [ 476, 82 ], [ 475, 82 ], [ 475, 97 ], [ 476, 97 ], [ 476, 99 ], [ 477, 99 ], [ 477, 101 ], [ 478, 101 ], [ 478, 103 ], [ 479, 103 ], [ 479, 104 ], [ 480, 104 ], [ 480, 106 ], [ 481, 107 ], [ 482, 107 ], [ 482, 108 ], [ 483, 108 ], [ 483, 109 ], [ 485, 109 ], [ 485, 110 ], [ 486, 110 ], [ 486, 111 ], [ 488, 111 ], [ 488, 112 ], [ 490, 112 ], [ 490, 113 ], [ 492, 113 ], [ 492, 114 ], [ 499, 114 ] ] }, "center": { "48": [ 487, 90 ] } }

Imagine suddenly you no longer exist, poof, from one day to the next there is no more you.

What if you knew that this day would come in a month?
What if it wasn't for another year?
Or in 5 years?

Would you spend your remaining time differently than you do now?
If so, why aren't you already doing it?

I have rewritten and refined some parts and am quite happy with the final result. I also made a small git repository with the source code and some compiled documents.

All resources are published under the Unlicense. Feel free to modify anything.

At this point I'm very concerned about the open source industry relying so much on github. You have to remember that any project there can be swept away overnight because it doesn't fit into the agenca of a large company, for example.

{ "id": 8412027923, "name": "PropaGandalf", "description": "This is the logo of the freedom-loving PropaGandalf, who immortalised himself on this free and open source canvas with the help of his closest matrix friends.\n\nThe logo incorporates many symbolisms, including:\n- the colours of anarcho-capitalism\n- the open source logo\n- a copyright/copyleft sign turned downwards as a sign of the rejection of all intellectual property (IP)\n- a keyhole representing encryption and the cypherpunk culture\n- a broadcast antenna standing for the spread of the gospel of freedom and liberty", "links": { "lemmy": [ "![email protected]" ] }, "path": { "0": [ [ 750, 333 ], [ 750, 346 ], [ 751, 346 ], [ 751, 348 ], [ 752, 348 ], [ 752, 350 ], [ 753, 350 ], [ 753, 351 ], [ 754, 351 ], [ 754, 353 ], [ 755, 353 ], [ 755, 354 ], [ 756, 354 ], [ 756, 355 ], [ 757, 355 ], [ 758, 355 ], [ 758, 356 ], [ 759, 356 ], [ 759, 357 ], [ 760, 357 ], [ 761, 357 ], [ 761, 358 ], [ 762, 358 ], [ 763, 358 ], [ 763, 359 ], [ 764, 359 ], [ 765, 359 ], [ 766, 359 ], [ 767, 359 ], [ 768, 359 ], [ 769, 359 ], [ 770, 359 ], [ 771, 359 ], [ 772, 359 ], [ 773, 359 ], [ 774, 359 ], [ 775, 359 ], [ 776, 359 ], [ 776, 358 ], [ 778, 358 ], [ 778, 357 ], [ 780, 357 ], [ 781, 356 ], [ 781, 355 ], [ 783, 355 ], [ 783, 354 ], [ 784, 354 ], [ 784, 353 ], [ 785, 353 ], [ 785, 351 ], [ 786, 351 ], [ 786, 350 ], [ 787, 350 ], [ 787, 348 ], [ 788, 348 ], [ 788, 346 ], [ 789, 346 ], [ 789, 333 ], [ 788, 333 ], [ 788, 331 ], [ 787, 330 ], [ 786, 330 ], [ 786, 328 ], [ 785, 328 ], [ 785, 326 ], [ 784, 327 ], [ 783, 327 ], [ 782, 327 ], [ 782, 326 ], [ 781, 327 ], [ 780, 327 ], [ 779, 326 ], [ 778, 327 ], [ 777, 327 ], [ 776, 326 ], [ 776, 325 ], [ 777, 325 ], [ 777, 324 ], [ 778, 324 ], [ 778, 323 ], [ 777, 323 ], [ 777, 322 ], [ 776, 322 ], [ 775, 322 ], [ 774, 322 ], [ 774, 321 ], [ 774, 320 ], [ 775, 320 ], [ 776, 320 ], [ 763, 320 ], [ 763, 321 ], [ 761, 321 ], [ 761, 322 ], [ 759, 322 ], [ 759, 323 ], [ 758, 323 ], [ 758, 324 ], [ 756, 324 ], [ 756, 325 ], [ 755, 325 ], [ 755, 326 ], [ 754, 326 ], [ 754, 328 ], [ 753, 328 ], [ 753, 329 ], [ 752, 329 ], [ 752, 331 ], [ 751, 331 ], [ 751, 333 ], [ 750, 333 ], [ 750, 333 ], [ 751, 333 ] ] }, "center": { "0": [ 769, 342 ] } }

Folget dem Gandalf

The Mixxx Board of Directors in pleased to announce plans to acquire the AlphaTheta Corporation (formerly known as Pioneer DJ), Serato Audio Research Ltd. and Native Instruments.

Hey fellow linux enjoyers,

today I found this interesting article which talks about rethinking the underlying data structures of an OS. I was always very enthusiastic about DBFileSystems but this approach takes it even a step further.

It comes with some serious caveats though.

Niri, the scrolling WM, now supports touch input

sus

Seriously what is this? Nintendo argues that by instructing users how to extract the prod.keys from their own switch the yuzu developers are essencially infringing on the DMCA.

So what? Now you can't even freely use your own property anymore because it goes against the design intentions of some big company that just want's to milk their users?

Nintendo goes directly after this argument in its lawsuit, arguing that buying a Switch game only means you "have Nintendo's authorization to play that single copy on an unmodified Nintendo Switch console."

Hello networking community

driven by the vision of a decentralised, independent and neutral network, I have set out into the depths of netowrking. I have compared different networks and tried to understand the underlying structures.

But my head is spinning from all the research and I've lost track a bit, which is why I'm turning to you. I would like to compare and categorise all these networks according to their protocols using the osi model.

I would be grateful if you could help me to fill in the following table as good as possible. You can simply copy it or write your answer in the comments.