To me it was not immediately clear from the title what this tool does: It is meant for migrating issues to SourceHut’s TODOs.

Anyone running their own DNS for example via pi-hole may want to disable DoH by blocking resolution of the canary domain use-application-dns.net as documented here: https://support.mozilla.org/en-US/kb/canary-domain-use-application-dnsnet

Absolutely, I’d also urge everyone to read the original article from Stundin: https://stundin.is/grein/13627/key-witness-in-assange-case-admits-to-lies-in-indictment/ It is quite detailed as well as horrifying, regarding all the things the FBI did/let happen just to take Julian Assange down.

Actually there is a map that shows the alleged detention facilities: https://xjdp.aspi.org.au/ but I guess it’s pretty much impossible to tell what the buildings marked there actually are. I have not really researched this topic so far but above analysis doesn’t quite hold anymore assuming the linked map actually shows detention facilities. Does anyone have more resources on this?

The article concludes with:

A lot more needs to be done to make a maintainer’s life easier, but paying them real wages for their real work would be a great place to start.

Which leaves the obvious question, who is going to do the paying. It certainly is not feasible to expect end users to pay the devs directly, especially considering how most projects are built on top of many libraries. That leaves companies, but this can’t really work either as even though a few projects may find a fitting company as sponsor (i.e. said company uses the project as library), there are certainly tons of projects that can’t be tied to some company for sponsorship. And this is not even mentioning that for the most part there is no incentive for companies to sponsor a library even though it’s heavily used internally.

What does this leave? Well, the state, the taxpayers money. The way I see it open source software in today’s society is necessary infrastructure, just like streets or electricity. Open source software is a public good and so the public should fund it. I’d love to see states spending more money on it but I doubt it’s ever going to happen unless our society changes drastically.

But I guess a good first step is to inform non IT people and increase awareness on just how much our world relies on open source.

Sounds like you should consider dual booting :)

One should take this with a grain of salt. First of all according to the article the authors of the paper themselves admit that they do not have conclusive evidence that the observed structures are actually mushrooms. And if you go through the paper everything you see just looks like pebbles.

And something else to consider are some of the other papers of the main author that suggest at least to me that they probably are not an expert in this field:

• Quantum Physics of God: How Consciousness Became the Universe and Created Itself
• Quantum Entanglement with the Future: Lincoln Dreams of His Assassination
• The Time Machine of Consciousness Quantum Physics and the Time Machine of Consciousness: Past Present Future Exist Simultaneously. Entanglement, Tachyons, Relative Time, Circle of Time, Quantum Time, Dream Time, PreCognition, Retrocausation, Deja Vu, and Premonitions

Source: https://www.researchgate.net/profile/Rhawn-Joseph

Are you aware of https://www.windy.com? In comparison it provides quite some more information.

Actually Kate does support LSP via plugin: https://kate-editor.org/post/2020/2020-01-01-kate-lsp-client-status/

Interesting, one thing I wonder is how they make money / how this is funded. This just seems too good to be true, no data collection/tracking, free apps, no ads. Sadly it looks like the apps are not open source though.

Kinda looks like the output of pwgen -sy 1024 1 but that’s probably not very helpful.

I see, better have a closer look next time :)

Yes, that does help a little. But how much depends on your threat scenario: If you just don’t want your ISP to know what you are doing or hide your true IP from some web site you are probably good but if you want to avoid online tracking the situation with a selfhosted vpn may even be worse as your server probably has a static IP address and makes you easy to identify. Also note that once you login into some website with and without vpn it is easy to connect you to your server.

From my experience wireguard is pretty easy to setup. For what purpose do you want to setup your own vpn though? If it is for privacy reasons this is probably a bad idea because most likely the server that will run the vpn software will be linked to you. And if you are the only person using your selfhosted vpn, it is trivial to identify you.

Yes, that’s correct. Weylus itself is only responsible for input and screen mirroring. The program you can see in the GIF is Xournal++.

I mostly agree with the sentiment. The thing that really bugs me is that configuring DNS system wide is broken like that.

Yes you are right, input lag is definitely lower. I don’t have numbers though as it is kinda hard to measure.

I think something that definitely is still missing is an obvious way to migrate existing communities over to lemmy as gracefully as possible. Some kind of bridging, perhaps via bots, would be nice and it looks like I am not the only one thinking this: https://github.com/LemmyNet/lemmy/issues/1542

Rust eliminates a lot of memory safety problems at compile time. Roughly speaking once you allocate memory and assign a variable to it, that variable “owns” said memory. A variable owning memory is responsible for its lifetime and just like in many other programming languages once it goes out of scope, the memory is released.

So far so boring. What makes Rust different is the borrow checker. It ensures that all references (equivalent to pointers in C) to some memory (in this case not owned), are always valid. Like that it is impossible to access invalid blocks of memory in (safe) Rust. You never have to wonder who is responsible for deallocating memory and you never have to fear dangling pointers as those simply do not exist in Rust.

I am sure there is much more to it, but this is certainly one of the arguments.

I am not exactly convinced of this:

• The GiHub repo is empty (only a Readme and LICENSE) and I can not read the source code
• Apparently it is just an electron wrapper, so I would not call this native
• Looks like it just uses https://github.com/nativefier/nativefier, so there probably really is no added value to just using your browser