Re: [DNG] FF now defaults to DNS-over-HTTPS for US
On 2020-03-03 5:45 p.m., spiralofhope wrote: This helps me remember: E for English "grEy" A for American "grAy" I attempt to be trilingual in "English". Thanks, that memory tool is great. In Canada we say GrEh, but we spell it the English way. (-; Clarke ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] FF now defaults to DNS-over-HTTPS for US
On Tue, 3 Mar 2020 11:49:57 -0800 Rick Moen wrote: > > 'grey' rather than 'grey': because it's much greyer that way. > 'gray' > > See, even when I set out to adopt quaint USAnaian spelling, I > sometimes can't quite manage it. This helps me remember: E for English "grEy" A for American "grAy" ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] FF now defaults to DNS-over-HTTPS for US
Er, stepping on my own line: > Some years back, I had some good-natured jousting in e-mail with noted > Usenet figure Gharlane of Eddore[1], who had chided me on > rec.arts.sf.tv.babylon5 about my use of Commonwealth spelling -- but > certainly didn't allege that it was mistaken. I amused him and almost > won him over with my declaration that of course I write 'grey' rather > than 'grey': because it's much greyer that way. 'gray' See, even when I set out to adopt quaint USAnaian spelling, I sometimes can't quite manage it. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] FF now defaults to DNS-over-HTTPS for US
Quoting Steve Litt (sl...@troubleshooters.com): > "Another relevant question is whether further centralisation [SIC] of > the internet is, inherently, a bad thing." Unaware of the Queen's English, my good lad? Some years back, I had some good-natured jousting in e-mail with noted Usenet figure Gharlane of Eddore[1], who had chided me on rec.arts.sf.tv.babylon5 about my use of Commonwealth spelling -- but certainly didn't allege that it was mistaken. I amused him and almost won him over with my declaration that of course I write 'grey' rather than 'grey': because it's much greyer that way. I miss him a lot. He was erudite and a real character, just what I want to be when I grow up. [1] https://en.wikipedia.org/wiki/Gharlane_of_Eddore ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] FF now defaults to DNS-over-HTTPS for US
On 2020-03-03 12:56, Steve Litt wrote: On Sun, 01 Mar 2020 17:08:28 -0600 goli...@devuan.org wrote: Just great! So how can we keep off this cloudflare thing? https://www.theregister.co.uk/2020/02/25/mozilla_turns_on_dns_over_https_by_default_for_usa/ "Another relevant question is whether further centralisation [SIC] of the internet is, inherently, a bad thing." Yes, centralization of the Internet is a bad thing, completely contrary to the Internet's design and purpose. The Internet (formerly Arpanet) was designed by the Department of Defense to be widely distributed, with lots of redundancy, so that if the Soviet Union nuked the hosts in Philly, the hosts in Atlanta and Chicago and South Bend Indiana picked up the slack. The distributivity made the Internet indestructible. It also made it hard for a scoundrel to poison the DNS system or to get away with lying. Now we're starting to centralize. Facebook, controlled by one multi-billionaire, solicits and promotes political lies that might determine elections. The golden age of the Internet was the mid to late 1990's, when we all got online via the regulated telephone utility. Anyone with a Linux computer, a few modems, and a reasonable on-ramp to the Internet could set themselves up as an ISP, the controller of your last mile. And they did. So prices fell from $75/month in 1995 to $25/month by 1999. And if you didn't like your ISP, you probably had 50 other choices. So ISPs were reasonably priced and customer-focused: Competition at its best. In today's more centralized Internet, there are maybe twenty providers of last-mile service nationwide [1], and they've divided the map such that no more than two compete in most areas. Prices are up. One could argue that price per Mbs is way down, but in 20 years I'd hope so, and believe that with competition we'd be paying about $10/month for the same service. It's my belief that the wide distributivity of the original Internet was what allowed it to thrive to this point, and centralization is slowly choking it, putting it at risk, and making it less useful. Exaaactly. The question is "less useful" for whom? Certainly not the user. It is ultimately about control of information and populations in order to empower and enrich those at the top of the economic food chain. Truth are lies and lies are truth. Just keep buying more of what you don't need to create debt which will enslave you for life. We own you. Get over it and just keep clicking . . . golinux ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Which DE?
On Mon, 02 Mar 2020 08:11:49 +0100 "J. Fahrner via Dng" wrote: > Am 2020-03-01 23:07, schrieb aitor: > > > My vote is for tint2. > > I also vote for openbox with tint2. Last night I installed tint2 on my OpenBox. Seems to work very nicely. The tint2conf configuration tool that ships with it is horribly incomplete, so config must be done manually via file edit and then applied via killall -SIGUSR1, which would be very difficult for non-power-users. > > if you don't want to tediously configure it yourself, install > Bunsenlabs https://www.bunsenlabs.org/ and then migrate it to Devuan. > Bunsenlabs has a nice theme and helper scripts for the openbox menu. > It saves you a lot of work. That's good info, because tint2conf sucks. SteveT Steve Litt February 2020 featured book: Thriving in Tough Times http://www.troubleshooters.com/thrive ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] FF now defaults to DNS-over-HTTPS for US
On Sun, 01 Mar 2020 17:08:28 -0600 goli...@devuan.org wrote: > Just great! So how can we keep off this cloudflare thing? > > https://www.theregister.co.uk/2020/02/25/mozilla_turns_on_dns_over_https_by_default_for_usa/ "Another relevant question is whether further centralisation [SIC] of the internet is, inherently, a bad thing." Yes, centralization of the Internet is a bad thing, completely contrary to the Internet's design and purpose. The Internet (formerly Arpanet) was designed by the Department of Defense to be widely distributed, with lots of redundancy, so that if the Soviet Union nuked the hosts in Philly, the hosts in Atlanta and Chicago and South Bend Indiana picked up the slack. The distributivity made the Internet indestructible. It also made it hard for a scoundrel to poison the DNS system or to get away with lying. Now we're starting to centralize. Facebook, controlled by one multi-billionaire, solicits and promotes political lies that might determine elections. The golden age of the Internet was the mid to late 1990's, when we all got online via the regulated telephone utility. Anyone with a Linux computer, a few modems, and a reasonable on-ramp to the Internet could set themselves up as an ISP, the controller of your last mile. And they did. So prices fell from $75/month in 1995 to $25/month by 1999. And if you didn't like your ISP, you probably had 50 other choices. So ISPs were reasonably priced and customer-focused: Competition at its best. In today's more centralized Internet, there are maybe twenty providers of last-mile service nationwide [1], and they've divided the map such that no more than two compete in most areas. Prices are up. One could argue that price per Mbs is way down, but in 20 years I'd hope so, and believe that with competition we'd be paying about $10/month for the same service. It's my belief that the wide distributivity of the original Internet was what allowed it to thrive to this point, and centralization is slowly choking it, putting it at risk, and making it less useful. [1] Not counting city-provided Internet SteveT Steve Litt February 2020 featured book: Thriving in Tough Times http://www.troubleshooters.com/thrive ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] libnetaid-0.1
Hi again,
On 3/3/20 13:10, aitor wrote:
Hi,
On 2/3/20 1:03, aitor wrote:
Hi again,
On 1/3/20 22:36, aitor wrote:
Hi all,
The shared library of simple-netaid is ready for use.
Here you are the packages for devuan beowulf in amd64:
http://gnuinos.org/libnetaid/
Install all the packages and write the following simple program:
___
#include
int main (int argc, char **argv)
{
print_active_wifis(argv[1]);
return 0;
}
___
You can build it linking the shared library and the headers with the
following flags:
$ gcc main.c -o main -lnetaid
-I/usr/include/x86_64-linux-gnu/simple-netaid
Maybe first of all you will need to update the ld cache via:
$ sudo ldconfig
Now, if you run the binary:
$ sudo ./main wlan0
you will get all the available active wifis (replace wlan0 by your
.
The above program is a very simple example, but shortly i will
document the usage
of this library and some functions like, for example:
bool is_plugged(const char *device);
void show_devices();
void interface_up(const char *device);
void interface_down(const char *device);
void ifup(const char *device);
void ifdown(const char *device);
void print_active_wifis(const char *device);
void wired_connection(const char *device);
void wireless_connection(const char *device, const char *essid,
const char *password);
void show_network_connection();
void disconnect(const char *device);
etc...
Cheers,
Aitor.
I fixed a bug related with the wireless_connection and uploaded the
new packages.
You can test this function building the following code:
__
#include
int main (int argc, char **argv)
{
wireless_connection(argv[1], argv[2], argv[3]);
return 0;
}
___
and running:
$ sudo ./main wlan0
It's working for me without failures.
Cheers,
Aitor.
I'm updating the packages. Some parts of the code need changes when
upgrading from jessie to beowulf, mostly the code of iproute.
http://gnuinos.org/libnetaid
Build the folling example (as I explained above):
http://gnuinos.org/libnetaid/main.c
and run the following commands:
$ ./main 0
$ sudo ./main 1
$ sudo ./main 2 ESSID PASSWORD
$ sudo ./main 3
The first one says if you are connected; the second one gives you all
the available active wifis;
the third one connects to the wireless devices, and the last one
disconnects the device.
Cheers,
Aitor.
New update in both the packages and the main.c example. The "./main 0"
command now gives a detailed info about the network connection.
I removed the MAC Address so far because it's giving me a segmentation
fault. I hope fix this issue shortly.
Download the new packages again and give it a try, if you want.
Thanks in advance,
Aitor.
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] libnetaid-0.1
Hi,
On 2/3/20 1:03, aitor wrote:
Hi again,
On 1/3/20 22:36, aitor wrote:
Hi all,
The shared library of simple-netaid is ready for use.
Here you are the packages for devuan beowulf in amd64:
http://gnuinos.org/libnetaid/
Install all the packages and write the following simple program:
___
#include
int main (int argc, char **argv)
{
print_active_wifis(argv[1]);
return 0;
}
___
You can build it linking the shared library and the headers with the
following flags:
$ gcc main.c -o main -lnetaid
-I/usr/include/x86_64-linux-gnu/simple-netaid
Maybe first of all you will need to update the ld cache via:
$ sudo ldconfig
Now, if you run the binary:
$ sudo ./main wlan0
you will get all the available active wifis (replace wlan0 by your
.
The above program is a very simple example, but shortly i will
document the usage
of this library and some functions like, for example:
bool is_plugged(const char *device);
void show_devices();
void interface_up(const char *device);
void interface_down(const char *device);
void ifup(const char *device);
void ifdown(const char *device);
void print_active_wifis(const char *device);
void wired_connection(const char *device);
void wireless_connection(const char *device, const char *essid, const
char *password);
void show_network_connection();
void disconnect(const char *device);
etc...
Cheers,
Aitor.
I fixed a bug related with the wireless_connection and uploaded the
new packages.
You can test this function building the following code:
__
#include
int main (int argc, char **argv)
{
wireless_connection(argv[1], argv[2], argv[3]);
return 0;
}
___
and running:
$ sudo ./main wlan0
It's working for me without failures.
Cheers,
Aitor.
I'm updating the packages. Some parts of the code need changes when
upgrading from jessie to beowulf, mostly the code of iproute.
http://gnuinos.org/libnetaid
Build the folling example (as I explained above):
http://gnuinos.org/libnetaid/main.c
and run the following commands:
$ ./main 0
$ sudo ./main 1
$ sudo ./main 2 ESSID PASSWORD
$ sudo ./main 3
The first one says if you are connected; the second one gives you all
the available active wifis;
the third one connects to the wireless devices, and the last one
disconnects the device.
Cheers,
Aitor.
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] FF now defaults to DNS-over-HTTPS for US
On 3/2/20 1:08 AM, goli...@devuan.org wrote: > So how can we keep off this cloudflare thing? there are also other non-corp DoH/DoT providers, so default cloudflare setting in ff can be changed.. (eg. https://libredns.gr/). generally, i don't find DoH a problem, i think it's a good measure for most users.. it's cloudflare i don't trust. 2c, d. signature.asc Description: OpenPGP digital signature ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
