News

GNUnet News: GNUnet 0.20.0

by

GNUnet 0.20.0 released

We are pleased to announce the release of GNUnet 0.20.0.

GNUnet is an alternative network stack for building secure, decentralized and
privacy-preserving distributed applications.
Our goal is to replace the old insecure Internet protocol stack.
Starting from an application for secure publication of files, it has grown to
include all kinds of basic protocol components and applications towards the
creation of a GNU internet.

This is a new major release.
It breaks protocol compatibility with the 0.19.x versions.
Please be aware that Git master is thus henceforth (and has been for a
while)

INCOMPATIBLE

with
the 0.19.x GNUnet network, and interactions between old and new peers
will result in issues. 0.19.x peers will be able to communicate with Git
master or 0.20.x peers, but some services will not be compatible.

In terms of usability, users should be aware that there are still

a number of known open issues

in particular with respect to ease
of use, but also some critical privacy issues especially for mobile users.
Also, the nascent network is tiny and thus unlikely to
provide good anonymity or extensive amounts of interesting information.
As a result, the 0.20.0 release is still

only suitable for early adopters
with some reasonable pain tolerance

.

Download links

The GPG key used to sign is:

3D11063C10F98D14BD24D1470B0998EF86F59B6A

Note that due to mirror synchronization, not all links might be functional
early after the release. For direct access try

http://ftp.gnu.org/gnu/gnunet/

Changes

A detailed list of changes can be found in the

git log

, the

NEWS

and
the

bug tracker

.

Known Issues

  • There are known major design issues in the TRANSPORT, ATS and CORE subsystems which will need to be addressed in the future to achieve acceptable usability, performance and security.
  • There are known moderate implementation limitations in CADET that negatively impact performance.
  • There are known moderate design issues in FS that also impact usability and performance.
  • There are minor implementation limitations in SET that create unnecessary attack surface for availability.
  • The RPS subsystem remains experimental.
  • Some high-level tests in the test-suite fail non-deterministically due to the low-level TRANSPORT issues.

In addition to this list, you may also want to consult our bug tracker at

bugs.gnunet.org

which lists about 190 more specific issues.

Thanks

This release was the work of many people. The following people contributed code and were thus easily identified:
Christian Grothoff, t3sserakt, TheJackiMonster, Marshall Stone, Özgür Kesim and Martin Schanzenbach.

GeckOS 2.1 released

by
I had to do some digging into our archives to see if we ever covered GeckOS before, but apparently we haven’t – and that’s a shame. GeckOS is a pre-emptive multitasking operating system for the Commodore 64 and the PET, and should be easily portable to other 6502-based machines, and offers multithreading, TCP/IP networking, and more. Version 2.1 has just been released, and it adds a ton of new features and bugfixes.

Penemuan baruu! || Animash part3 #shorts #shortvideo

by
Terima kasih Tuan dan Nyonya sekalian sudah meluangkan waktunya untuk menonton konten kali ini.
Jangan juga buat di like, comment dan subscribe untuk perkembangan channel ini!!!
———-
Jangan Lupa juga buat Follow:
Tiktok :
Instagram :
———-
Barangkali Tuan dan Nyonya mau berbagi Hartanya untuk perkembangan channel ini
Saweria : https://saweria.co/dewamahendra
———-
Jika ada masukan atau saran silahkan ketik di kolom komentar.
Saya sangat menantikan komentar yang membangun dari Tuan dan Nyonya skalian. See yaa!!!
———-
#Dewamahendra #animash #trendingshorts #trending #games #casual #shortvideo #shorts #tiktok #fyp

Glimmer DSL for SWT 4.29.0.0 Released

by
Glimmer DSL for SWT (JRuby Desktop Development Cross-Platform Native GUI Framework) version 4.29.0.0 has just been released! It is that quarterly release the happens when a new version of the Eclipse SWT GUI toolkit is released (SWT 4.29 was released in September of 2023).

The invisible problem: text editing on Android and iOS sucks

by
Android and iOS share a common problem: they copied desktop text editing conventions, but without a menu bar or mouse. This forced them to overload the tap gesture with a wide range of actions: placing the cursor, moving it, selecting text, and invoking a pop-up menu. This results in an overly complicated and ambiguous mess-o-taps, leading to a variety of user errors. It’s less of a problem if you only do short bursts of text in social media or messaging apps. But doing anything more complicated like an email gets tedious. However, in my user study on text editing, I was surprised to find that everyone had significant problems and rather severe workaround for editing text. With the extremely talented Olivier Bau, together we created a prototype called Eloquent, which offers a much simpler solution. We presented this work at UIST 2021. This is now one of my favourite articles I’ve ever read. I despise text input and text editing on mobile devices, whether they be Android or iOS. I hate it with the passion of a thousand burning suns, but it seems like nobody else cares. Luckily, the author of this article, Scott Jenson, a man with an impressive career doing UI work at Apple, Google, and others, agrees with me, and together with his colleagues, during his time at Google, he came up with an entirely different, touch-first way of editing text. The end result – be sure to watch the video to see it in action – immediately clicks for me. I want this. Now. This would be a massive usability improvement, and the fact it isn’t in Android yet, despite being developed at Google, is further evidence Google has no clue how to make good ideas float to the top. Jenson explains why Eloquent, as they called their new input/editing system, won’t ship with Android, while he expresses a bit more optimism Apple might be more open to rethinking mobile text editing: Unfortunately, shipping something like Eloquent would be challenging. First, as too many people mistakenly see text editing as “done”, there is little appetite to fix it. Second, users have been trained to cope with this error-prone approach for well over a decade. Asking people to change at this point would be hard. But most importantly, fixing text editing isn’t seen as important enough in the war between Android and iOS. It’s not the flashy feature that shifts your Net Promoter Scores. What I find ironic is that a fundamental change, like fixing text editing, could make people feel much more at ease using their phones and could be an enormous reason to switch. But it would be a slow burn and take years of steady effort. Android just can’t think this way. Apple just might. Android needs this.