freedomPusher

joined 4 years ago
MODERATOR OF
[–] freedomPusher@sopuli.xyz 2 points 2 years ago* (last edited 2 years ago)

“phone” is more complicated for me.

  • smartphone → deGoogled Android (because I won’t feed the popular hardware vendors like Samsung which alternative OSs support), no GSM chip, in airplane mode; occasionally wifi
  • phone (for talking) → 20-year old candybar phone
  • VOIP → disaster because the cheap providers do not support basic crypto
  • payment → cash, even when not possible. That is, if a creditor demands electronic payment, I still offer only cash. When they take me to court, I explain cash acceptance is an obligation. And I win. They can fuck right off with their Bill Gates-ian forced-banking agenda. I also keep my eye out for cashless restaurants that collect after dining -- they’re accepting my cash or I’m eating for free.
  • email → no, snail mail. Google and MS broke email.
[–] freedomPusher@sopuli.xyz 1 points 2 years ago* (last edited 2 years ago)

similar study reported by the ALA. (pdf research paper which also cites PEW research center)

Interesting excerpt:

Gen Z and millennials’ high use of Amazon’s audio-book and ebook paid subscription services poses a challenge for libraries articularly because of “Amazon-exclusive” licensing, which prohibits some authors from distributing their work outside the Amazon ecosystem.

[–] freedomPusher@sopuli.xyz 3 points 2 years ago* (last edited 2 years ago)

from the article:

Younger generations tend to be more values driven than older ones, and libraries’ ethos of sharing seems to resonate with Gen Zers and millennials – as does a space that’s free from the insipid creep of commercialism. At the library, there are no ads and no fees – well, provided you return your books on time – and no cookies tracking and selling your behavior.

Actually we need to work on that.

Libraries do little to nothing to make browsers defensive w.r.t the intrusive web and some libraries even block Tor, which enables ad surveillance corps to monetize your data. PCs are usually all Windows (which has some baked-in surveillance) and often the systems are hardened so users cannot deploy¹ any kind of self-defense tools. Network users are sometimes blocked from using egress Tor traffic (iow, nothing that threatens the library itself). Library patrons are distrusted more than the surveillance advertisers on the other end. So patrons have to contend with both a spammy web and having their hands tied by excessive nannying.

I was unable to fetch the Debian OS at the library because the ISOs are no longer on the official mirror sites. Someone had to setup a server on a non-standard port. One particular library branch decided it was a good idea to arbitrarily block uncommon ports (WTF). And because the security was outsourced without support, the librarians were helpless.

Although to some extent these barriers might not put off millennials because they never experienced the free, open, and ad-free internet we had ~2—3 decades ago.

  1. sure it would be a recipe for disaster to let users install anything willy-nilly, but patrons should be able to lodge a ticket requesting a tool config they need.
[–] freedomPusher@sopuli.xyz 2 points 2 years ago (1 children)

There are maker spaces devoted to that around the world called “fab labs” equipped with CNRs, 3d printers, welding gear, etc, but the hourly prices are insane. A library seems like the wrong place for that sort of thing but I’m sure the price is right.

[–] freedomPusher@sopuli.xyz -1 points 2 years ago* (last edited 2 years ago) (1 children)

Then study German so you can make sense of the research. Then tell us what it says :)

[–] freedomPusher@sopuli.xyz 2 points 2 years ago* (last edited 2 years ago)

I recall reading in a kbin bug (which reported that votes are public and should not be) that Lemmy votes are not. So I could have been misinformed.. i did not look into it.

[–] freedomPusher@sopuli.xyz 1 points 2 years ago* (last edited 2 years ago)

So everyone is stupid trying to run lemmy the way they can

Some people are more skilled than others. Skilled admins know how to avoid CF. Skilled users know how to find instances that are run by skilled admins (non-CF). Unwise users give up something for nothing and needlessly trust and empower a demonstrably abusive tech giant.

Because privacy is more important on a public forum than fighting the bots.

Of course. Privacy is about control not just security. Those bots CF fights are beneficial. The fight against beneficial bots has collateral damage on humans caught in the cross-fire, evidenced by countless discriminatory CAPTCHAs, driven by some protectionist asshole who doesn’t want their data scraped. The fight against bots is harmful to human users; not just because of the discrimination against blind people but also because we lose the benefits that beneficial bots bring us.

But someone for some reason should give you a server for free. … So you won’t contribute, won’t help just nag about everything. ok.

Of course. Money isn’t free. Your expectation that a developer not only contribute labor to the commons but also spend their own money is a perversely absurd demonstration of self-entitlement. If you want a tor version make it yourself and use the high-speed connection you already have to test with.

But you CAN solve the issues of lemmy because you CAN fork it, but you won’t.

Fork it for what purpose? Adding Tor support is useless on a capped uplink.

You trust some random guy from Finland more than everyone else,

Citation needed. I’ll trust any random person more than Cloudflare because CF has proven to be untrustworthy.

[–] freedomPusher@sopuli.xyz 1 points 2 years ago* (last edited 2 years ago) (2 children)

When running an instance, everything i follow or subscribe to would be fetched. A server is not going to wait until a user requests a specific article. The timeline will be populated and mirror everything -- more than I would likely read. Lemmy is designed so the timeline is populated and visits to articles are instant. I do not read every single article in any community. As an end user, my client only fetches content I under my micro-control.

If there is a gratis VPS somewhere, I would be keen.. that would open up more options.

[–] freedomPusher@sopuli.xyz 1 points 2 years ago (4 children)

Can you? Why don’t you have your own lemmy server and lemmy fork? I’m really curious now, if everything is so terrible here.

I do not have the kind of uplink that can handle that volume.

[–] freedomPusher@sopuli.xyz 1 points 2 years ago* (last edited 2 years ago) (6 children)

Ok so cloudflare can see my password hash

No, not the hash. The hash is only marginally sensitive. CF sees your /unhashed/ password (that is, your password before hashing).

everything else is the same as you,

Not at all. Cloudflare /only/ sees my public content, nothing that I listed as non-public. Of course that can change if Sopuli would suddently decide to use cf.

I can live with that if it helps the instance admin manage his free work.

Several instance admins have managed to offer their gratis service /without/ the Cloudflare compromise. So you’ve made a needless compromise in support of a harmful actor.

Afaik CGNAT shouldn’t be a problem by itself.

CGNAT users hit the blockade unpredictably. Cloudflare is anti-bot (that also includes beneficial bots). So if someone is perceived as running a bot on your network CF will either blackball the IP address or the whole range. You could then receive that blackballed IP address.

I know images are not synced to your instance,

There are many reasons why accessing the original post is useful. Images is indeed one of the problems with CF.

Federation is not supported on Tor:

In the free world of FOSS, we are not limited to what is “supported” because people can grab the code and support themselves. There is in fact a fedi client that shakes free of the server and directly accesses servers needed to assemble a thread. This tool was designed to resist fedi politics. It would naturally be blocked when accessing CFd servers over Tor. CF is just another case where a philosophically dubious configuration by a reckless profit-driven corp causes unforeseen collateral damage to human beings and broke the decentralization of the fedi with a purpose-defeating outcome. The fedi was designed for decentralization but obviously a gross oversight that a majority of fedi users are centralized on CF.

[–] freedomPusher@sopuli.xyz 0 points 2 years ago* (last edited 2 years ago) (8 children)

Can cloudflare see this? I don’t know how it is important?

You have to decide for yourself what’s important and who to trust. What you should consider though is that by choosing a Cloudflare instance, you needlessly overshare; you extend trust when you don’t need to which is a bad default policy. And you are trusting a massive singular tech giant who also has visibility on ~20-25% of all other web traffic in the world.

I can see the SSL cert of lemm.ee is not from cloudflare, so they can’t see https traffic.

It’s impossible for end users to know whether Cloudflare has a TLS private key. It’s also very rare for Cloudflare not to have the key because it would defeat the purposes admins use Cloudflare for. If Cloudflare cannot see the traffic, it cannot respond to requests and the full load must be redirected to the source host (thus DoS protection and performance benefits are effectively gone). The rarely used option for a web admin to not share their key with Cloudflare is only available to premium customers, which keeps the option rare.

Do you know irl, personally who is the admin of sopuli.xyz? How can you be sure that they are not run by NSA or other countries’ agents?

I cannot know, but it’s far easier to trust one entity than many entities. With lemm.ee you have a diffusion of responsibility problem (i.e. finger-pointing) if shit hits the fan.. lemm.ee claims CF abused your data and CF claims lemm.ee did.

Who?

People whose ISPs use CGNAT, VPN users, the Tor community, libraries and situations of shared IP addresses in general.

You only communicate with your instance,

Not always. Sometimes I need to visit the original source. You cannot rely on 3rd party instances to keep a mirrored copy. Many instances are tight on space and when external content ages beyond a year they do a cleanup. There are also many visibility shenanigans with blocking where you realize you’re not seeing the whole conversation and need to visit original hosts to piece it together.

Which instance cannot reach lemm.ee because of cloudflare?

Any Tor instance would be inherently unable to reach lemm.ee, though I don’t know of any Tor instances myself (have not looked).

[–] freedomPusher@sopuli.xyz 3 points 2 years ago* (last edited 2 years ago) (1 children)

There are several ways:

  • You can hit F12 in either Firefox or Chrome, look at the headers for a “CF-ray” field. (or a simple CLI way: curl -I "$URL" | grep -i cf-ray)
  • this page will check for you. (there is a clearnet version of that link but i don’t recall); caveat: if a non-CF host has CF hosts on the same domain, this checker treats all hosts on the domain as CFd.
  • You can do a whois lookup to see if the IP belongs to Cloudflare.
  • If you do a DNS query, that will often give clues (though AFAIK you cannot distinguish users of CF’s DNS service from those of their proxy service)
  • There are some browser add-ons here which will tag Cloudflare sites so you can avoid them. The BMCA plugin will auto-redirect visits to CF sites to the archive.org mirror. Note those plugins can be tricky to install.

Note that your instance (lemmy.dbzer0.com) is free from Cloudflare.

 

The library’s PC was blocked from a Cloudflare site. This was not the CAPTCHA style block but a hard and fast absolute block. I tested another site which I know is Cloudflared, and no block (but that was the type of site that pushes CAPTCHAs rather than absolute blocks).

So I’m wondering how common this is. Cloudflare is generally hostile toward any shared IP address. Are many libraries experiencing Cloudfare blockades?

 

cross-posted from: https://fedia.io/m/Brussels/t/344992

Until recently, it was possible to download #Youtube videos on a library PC & store on USB drive by using an #Invidious front-end. Recently the library has blocked all invidious instances. You can still view videos but when you try to download one it gives a 403 forbidden error.

Why are they doing this?

I can only think of two possibilities: 1. bandwidth limitations 2. copyright issues. Anyone know anything solid about this?

Suggestions on other options would be appreciated. I assume users cannot install their own apps, which means front-ends that need installation are problably a non-starter. It looks like there is a web-based front end called #Piped but many of those instances are hosted with the same domain as Invidious thus may be blocked as well.

#lawfedi

 

cross-posted from: https://fedia.io/m/Brussels/t/344992

Until recently, it was possible to download #Youtube videos on a library PC & store on USB drive by using an #Invidious front-end. Recently the library has blocked all invidious instances. You can still view videos but when you try to download one it gives a 403 forbidden error.

Why are they doing this?

I can only think of two possibilities: 1. bandwidth limitations 2. copyright issues. Anyone know anything solid about this?

Suggestions on other options would be appreciated. I assume users cannot install their own apps, which means front-ends that need installation are problably a non-starter. It looks like there is a web-based front end called #Piped but many of those instances are hosted with the same domain as Invidious thus may be blocked as well.

#lawfedi

2
submitted 2 years ago* (last edited 2 years ago) by freedomPusher@sopuli.xyz to c/dabradio@feddit.uk
 

Just got a cheap dab+ radio from a shop that was liquidating. Bluetooth, stereo, USB, dab+, fm, aux.. The signal quality is perfect on 86 out of 87 Brussels stations that were auto-tuned. It sounds a bit low pitch & slightly muffled but I think that’s down to the cheap hardware.

  • One station cuts out (update: couple more cut out at different times).
  • 6 stations are redundant.
  • One station seems to have no purpose other than to advertise www.dabplus.be.

So there are ~80 useful stations, which is much more than the number of FM stations it could tune (~24, varying quality). DAB+ seems to also include AM broadcasts but I doubt there would be 50+ AM stations, so apparently DAB+ is receiving stations that don’t exist on FM or AM. Notably, there is BBC World Service in English, which I don’t think is offered over FM. That channel alone makes buying a DAB+ radio worth it.

Still no jazz stations! …AFAICT… Unless one of the stations with chatter going on is normally jazz. Otherwise that’s surprising & disappointing. Maybe some of the stations have jazz programs at scheduled times.

(update) These are the genres stations are tagged with:

  • news
  • current affairs
  • information
  • factual
  • arts
  • leisure
  • pop music
  • oldies music
  • classical music
  • folk music
  • rock music
  • other music

Most are tagged as “pop music” (80s, EDM, rock, hip hop, etc). And news=current affairs=information=factual (redundant!) So the “program type” metadata is not as useful as it could be.

The “Business AM” station sounds like AM radio (slightly raspy). I wonder if it’s being received by an AM radio tranceiver and converted to DAB+.

 

As I was looking into DAB gear, I found out the US only supports DAB players if they are in-band on-channel (IBOC) capable.

That complicates things a bit if I want to take the hardware to the US. Is IBOC typical or rare in DAB+ hardware sold in the EU?

This article lists the vendors but then got truncated.

 

I really like the idea of treating the radio like a #MythTV PVR -- to browse a schedule, prioritize programs and have them automatically recorded. But this article is bad news. It says the devices that could do this have been discontinued.

Is that still true? The article is 4 years old.

In principle, a DAB+ radio should be a network appliance. Just like Silicondust makes TV tuners with cat5 ethernet connections, it would be useful to have a DAB+ tuner that’s cat5 attached so software can present the schedule on a big screen and schedule recordings. Doesn’t exist, does it?

4
submitted 2 years ago* (last edited 2 years ago) by freedomPusher@sopuli.xyz to c/dabradio@feddit.uk
 

My smartphone has a built-in FM radio. Local shops are selling DAB+ radios. So I have to decide whether to buy one. I’m not really keen accumulate more electronic appliances for marginal gains.

Sound quality alone doesn’t justify it. What other factors are there? Will I get many more stations in Brussels?

I’m hesitant because AFAIK I cannot buy a DAB radio with an EPG+record fuction. (update: looks like I can get a USB stick & use software to fetch timetables & schedule recordings)

 

One of the bare minimum quality standards an official Debian app must have for admission into official Debian repos is that it must have a man page. Dino (the XMPP app) does not. This also means if users query to know what XMPP apps are installed by running “man -k xmpp”, there is no mention of dino-im.

The bug tracker for the Dino project is exclusively on Github, so this bug is reported here.

 

Debian Bullseye has dropped libraries that electron-based apps depend on. Consequently, Electronmail and the Wire app are both broken in Debian Bullseye.

The underlying issue is documented here:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895037

Debian developers will never know about the impact specifically on Electronmail and the Wire app because they are not in the official debian repos.

Both apps are managed exclusively in MS Github. Hence why this bug report is here.

 

This is a catalog and detailed comparison of tens of forges - mostly public access:

https://git.sdf.org/humanacollaborator/humanacollabora/src/branch/master/forge_comparison.md

 
  1. Free-world compatible bug tracker:

    (problem) You intend to report a bug, but the project officially uses an exceptionally controversial bug tracker (e.g. Gitlab.com or MS Github).

    (solution) Users report the bug wherever they want (forum, mailing list, Mastodon, usenet), then a reference to the ad-hoc bug report is indexed somewhere so users can browse all existing reports for a particular project. A similar idea is proposed here: https://pleroma.libretux.com/objects/c2e53ffd-212b-42c7-92cf-2ab7422e0372

  2. Censorship Whistleblower:

    Maintains local copy of posts to Reddit & Lemmy. Periodically checks public (cookieless) view of those articles. Logs & alerts on shadowban/censorship/moderator actions.

    Perhaps collaborate on metrics to expose patterns of censorship. Perhaps automatically post copies of censored material in a out-of-band place that has different people in power.

  3. Citation Scrubber/Optimizer for essays:

    1. Accepts text-based file or a link to an already published doc, parses out all URLs and checks for:

      • Tor hostility (403, CloudFlare, Impurva, tar-pitting)
      • assets of tech giants (CloudFlare, Amazon AWS, Google Cloud, MS Azure, etc)
      • JavaScript that fails LibreJS
      • dead links
    2. Creates report showing:

      • any offending discoveries from the above checks
      • most recent mirror link found in wayback machine (regardless of article quality/ethics, in case the article later disappears)
      • alternate links to nefarious/harmful links
    3. Produces new markdown version (if the input was in markdown), which automatically applies the suggested changes. Perhaps give an option to retain the bad links but annotate warnings.

  4. Surfraw Expansion:

    CLI search tool with results imported to a local db for filtering and analysis before using. E.g. CloudFlare results could be given a reduced ranking.

  5. Mastodon pro-netneutrality client:

    • When posting: checks your link to see if the document has access restrictions (e.g. paywall, blocks tor, CloudFlare). If yes, it edits your toot with an archive.org version of the link and keeps you in the editor.

    • When reading: posts containing bad links are hidden or replacement links are attached. Stats are kept so chronic offenders can be unfollowed, muted, or targeted for etiquette pursuasion/gentle lecturing.

  6. Mastodon pro-netneutrality server:

    Similar to the client. Posts with Tor-hostile and/or CloudFlare links are refused.

  7. Email address free-society compatibility tester:

    Does an MX lookup & checks whether an email address is hosted in a walled-garden like Gmail or MS Outlook, and reports known situations that the server refuses RFC-compliant messages. E.g. some servers will reject a message if the domain of the FROM address doesn't match the reverse lookup of the connecting IP; some reject connections from dynamic IPs, thus forcing senders to share the message with another third party.

    Perhaps state the retention policy of the server, if known, and/or the legal retention limits in that jurisdiction.

    Checks whether the email address has a PGP key on public keyrings.

  8. Wire-Bitlbee plugin

    Wire is a better alternative to Signal, but the bloated client app is Electron based. A bitlbee plugin would make it possible to use any IRC client the user wants.

Vote here:

 

(this post is intended for the repo-criteria-discuss@gnu.org mailing list)

This article covers a lot of unethical characteristics of gitlab.com.

If you search for the string "criteria" on that page, it will bring you to the issues that are relevant to the FSF mission. I also suggest reading the whole thing, because some of gitlab.com's harmful conduct should inspire more criteria for ethical repositories.

E.g.:

  • (3) Bugs should be easy to report. Some repos are so painful to use that people simply choose not to report bugs. Yet there is no criteria that covers this. Bug reporting is the one activity where convenience is critical.

  • (7) Being able to run "torsocks git clone " should be a criteria.

  • (9) Being able to register with a forwarding email account (and more generally, not being excluded from participation as a consequence of securing one's self).


This post is here because gnu.org has started using "OpenSPF" to restrict inbound email. The email above was rejected by the mail server automatically because the domain of the envelope FROM header does not match the reverse lookup of the sending server's IP address. In short, they are blocking contributors from using a forwarding email service to protect themselves. It's a pre-emptive strike with collateral damage to legitimate participants. Anyone with access to repo-criteria-discuss@gnu.org: please forward this to that list (or people thereon).

view more: ‹ prev next ›