some of the privacy messengers here (like Briar) have blogging/forum features

many people incorrectly assume briar aims to provide some sort of anonymity, because it uses tor onion services and is a self-described “secure messenger”. however, that is not the case:

https://code.briarproject.org/briar/briar/-/wikis/FAQ#does-briar-provide-anonymity (answer: no)

tldr: briar contacts, even when only actually using onions, exchange their bluetoooth MAC addresses and their most recent IPv6 link-local address and last five IPv4 addresses briar has seen bound to their wlan interfaces, just in case you’re ever physically near a contact and want to automatically connect to them locally.

I asked this question the other day if I could somehow input my handwritten notes into programs like Trilium (or logseq whatever) and memos. OCR/HCR seems to far behind still so I am unsure.

I just left this comment on your post.

Via the pine64 blog update about their e-ink tablet TIL about inkput (using OnlineHTR) which appears to be a step in the right direction.

fun fact: Phoenix was the original name of the browser we now know as Firefox

Similar to this: https://github.com/alibahmanyar/breaklist

Relatedly, there was a company was selling a cloud(🤡)-based product called “Little Printer” from 2012 to 2014; after their backend predictably shut down, some fans of it recreated it as https://tinyprinter.club/ and later https://nordprojects.co/projects/littleprinters/

somehow input my handwritten notes

I’ve heard the reMarkable e-ink tablet’s cloud service has good-enough-to-be-usable handwriting recognition, but sadly I haven’t heard of anything free/libre and/or offline that is.

Brendan Howell’s The Screenless Office is “a system for working with media and networks without using a pixel-based display. It is an artistic operating system.”

You can “read and navigate news, web sites and social media entirely with the use of various printers for output and a barcode scanner for input”.

weird, i wonder why. i just checked on an ubuntu 24.04 system to confirm it is there (and it is).

i guess your computer’s power button might not be supported (out of the box, at least) by Linux’s acpi implementation :(

How do I see all posts in all communities on a server?

By selecting “Local”. And you can sort by “New” to see them in chronological order. eg, here on your instance.

(disclaimer: this information might be years out of date but i think it is still accurate?)

SSH doesn’t have a null cipher, and if it did, using it still wouldn’t make an SSH tunnel as fast as a TCP connection because SSH has its own windowing mechanism which is actually what is slowing you down. Doing the cryptography at line speed should not be a problem on a modern CPU.

Even though SSH tunnels on your LAN are probably faster than your internet connection (albeit slower than LAN TCP connections), SSH’s windowing overhead will also make for slower internet connections (vs rsync or something else over TCP) due to more latency exacerbating the problem. (Whenever the window is full, it is sitting there not transmitting anything…)

So, to answer OP’s question:

• if you want to rsync over SSH, you usually don’t need a daemon (or to specify --rsh=ssh as that is the default).
• if you the reason you want to use the rsync daemon is performance, then you don’t want to use SSH. you’ll need to open a port for it.
• besides performance, there are also some rsync features which are only available in “daemon mode”. if you want to use those, you have at least 3 options:
  • open a port for your rsync daemon, and don’t use SSH (bonus: you also get the performance benefit. downside, no encryption.)
  • setup an SSH tunnel and tell the rsync client it is connecting to a daemon on localhost
  • look at man rsync and read the section referred to by this:

    • The remote-shell transport is used whenever the source or destination path contains a single colon (:) separator after a host specification. Contacting an rsync daemon directly happens when the source or destination path contains a double colon (::) separator after a host specification, OR when an rsync:// URL is specified (see also the USING RSYNC-DAEMON FEATURES VIA A REMOTE-SHELL CONNECTION section for an exception to this latter rule).

HTH.

Hikarunix

Funny that blog calls it a “failed attempt at a backdoor” while neglecting to mention that the grsec post (which it does link to and acknowledges is the source of the story) had been updated months prior to explicitly refute that characterization:

5/22/2020 Update: This kind of update should not have been necessary, but due to irresponsible journalists and the nature of social media, it is important to make some things perfectly clear:

Nowhere did we claim this was anything more than a trivially exploitable vulnerability. It is not a backdoor or an attempted backdoor, the term does not appear elsewhere in this blog at all; any suggestion of the sort was fabricated by irresponsible journalists who did not contact us and do not speak for us.

There is no chance this code would have passed review and be merged. No one can push or force code upstream.

This code is not characteristic of the quality of other code contributed upstream by Huawei. Contrary to baseless assertions from some journalists, this is not Huawei’s first attempt at contributing to the kernel, in fact they’ve been a frequent contributor for some time.

Wasn’t Huawei trying to put a Backdoor into linux?

as far as i know, that has not happened.

what makes you think it did?

fremdscham++ 😬

Or you could just… learn to use the modern internet that 60% of internet traffic uses? Not everyone has a dedicated IPv4 anymore, we are in the days of mobile networks and CGNAT. IPv4 exhaustion is here today.

Where are you getting 60%? Google’s IPv6 Adoption page has it under 50% still:

(while other stats pages from big CDNs show even less)

If you have ::/0 in your AllowedIPs and v6 connections are bypassing your VPN, that is strange.

What does ip route get 2a00:1450:400f:801::200e (an IPv6 address for google) say?

I haven’t used wireguard with NetworkManager, but using wg-quick it certainly adds a default v6 route when you have ::/0 in AllowedIPs.

You could edit your configuration to change the wireguard connection’s AllowedIPs from 0.0.0.0/0 to 0.0.0.0/0,::/0 so that IPv6 traffic is routed over it. Regardless of if your wireguard endpoint actually supports it, this will at least stop IPv6 traffic from leaking.

ipv4 with an extra octet

that was proposed as “IPv4.1” on April 1, 2011: https://web.archive.org/web/20110404094446/http://packetlife.net/blog/2011/apr/1/alternative-ipv6-works/

This video is full of jarring edits which initially made me wonder if someone had cut out words or phrases to create an abbreviated version. But, then I realized there are way too many of them to have been done manually. I checked the full original video and from the few edits i manually checked it seems like it is just inconsequential pauses etc that were removed: for instance, when Linus says “the other side of that picture” in the original there is an extra “p” sound which is removed here.

Yet another irritating and unnecessary application of neural networks, I guess.