erpicht

Amateur typesetting enthusiast.

  • 10 Posts
  • 267 Comments
Joined 1Y ago
cake
Cake day: Jun 03, 2021

help-circle
rss

Try it and find out! If F-Droid recognizes it, it’ll be listed as installed.



“All health care services related to gender transition treatments shall be considered medically necessary and not cosmetic,” the bill reads. Insurance companies may only be required to cover gender-affirming medical care when treatments, like hormone therapy, are also covered for patients that use them for “purposes other than gender transition.”

Yay!


Es kennen anscheinend viele diesen Linkblog von Fefe? Ich höre heute zum ersten mal von ihm und seinem Blog.


Grammarly defiantly collect a lot of information, which makes checking personal texts for grammar awkward

Bolding mine; I find it rather amusing that in a post dedicated to using a grammar-checking tool, the mistake of writing definitely as defiantly made it into the article, not to mention an incorrectly conjugated verb.

However, it seems that English is not his native language, so it’s understandable why such things occur :)


Not sure why you were down voted, as one doesn’t buy an iPhone in order to replace the existing software with FOSS equivalents.


The battery should probably be fine if the phone was made sometime the past 2-3 years, or if only lightly used by the previous owner. I haven’t owned enough phones to make much more than that unqualified prediction, however. I believe one term for a run-down battery is “spent.”

I happened to get my Pixel from a bloke who was upgrading to a newer phone just because he could, and only used it a year or so. The battery life is still excellent a year later under daily use.

I pick hardware based on which operating system I want to use. Getting a carrier and bootloader unlocked phone is my basis for searching, alongside price.

Although it has been claimed Google’s Pixels go to some lengths to implement security features with Android that other phones possibly don’t have. As a bonus, if you get an unlockable Pixel, the bootloader may be relocked when using another OS. But I am not particularly knowledgeable about such things.


That’s unfortunate to hear. As I am still studying at the uni and get part-time work through the privacy-respecting student job market, I’m not personally acquainted with LinkedIn or other job-searching sites.


Another reason to never sign up for LinkedIn, I suppose.


Yeah, I getcha. As a green fellow, I’m not yet much help for evaluating the security of projects by more than hearsay.

Compatibility with work and network requirements is unfortunately a pain still. It seems as though you might just be best off as you are.


One solution to the revenue issue for musicians is freely distributing the digital music and selling merch, physical copies, and concert tickets for income, much how Run the Jewels operates.

This doesn’t work, however, if one’s work is largely copied by larger figures early on, such that building a following and steady income is difficult to impossible because people first and foremost encounter soullessly copied derivatives of one’s music and the original artist is now “just another copy.”

Hence the discussion on how much of a work must be original.


As one commenter on the site points out, this is not a backdoor in any meaningful sense of the word, because it still has to be snuck onto the machine. Malware, yes. Backdoor, no.


I bought a used Pixel 3a for ~$150 over a year ago. The camera is very capable of capturing documents while maintaining legibility, and my banking application works just fine. It runs Android 12.

Purchasing used devices is an excellent way to keep costs down. I would look for deals on eBay.


Vanilla AOSP is an option if you violently distrust Lineage. Or if other projects like Divest, Calyx or Graphene are acceptable, buy supported hardware. A used Pixel, for example, is much less than an iPhone.



Sure, but I bring it up to highlight when even dread copyright law can be excepted, as the many legal cases tackle the questions of where the line between theft and quotation lies.


To add a helpful link, this question about sampling is similar to how Fair Dealing works, often termed “Fair Use” in the U.S. How much is sampled, and how it’s changed and integrated into the new work is a vital component when looking at whether someone is merely copying or innovating.


Have any here actually read the docs and used CollapseOS? I obtained a copy of it and the docs, but have not had time to properly learn how it works yet.


Hey, we gotta take into account that 'specially 'Muricans now are much more, er, big-boned than before! Ain’t no way we’re fitting in that teeny matchbox on the right. We’d have to slim down for that, which is frankly unacceptable.


"Intro to USB drivers for Plan9 and 9Front" by adventuresin9
As someone who has encountered unsupported peripherals, this quick look into how drivers work was fascinating to see.

New Kenobi Trailer!
Thoughts on this newest look at the upcoming series?
fedilink

This is an excellent introduction to using `groff` with the `-me` macro set. It is tailored towards anyone just looking for a quick start and even comes with some sample files at the end.

Community Poll: What do you use *roff for?
As stated above, I am curious to know how groff fits into people's lives. Do you write manpages, only take notes with it, prefer it to LaTeX andor ConTeXt for text formatting, or something else entirely? Which macros do you use, if any? Let me know! As for me, I encountered groff after already learning LaTeX, but I instantly appreciated its concise commands and began using it to take biology notes with the simple `-me` macro. I'm slowly expanding my usage to encompass math and graphing with `eqn` and `grap`, respectively. My needs are not always met by `-me` as of late, so a macro switch is in order. GNU seems most inclined to continue work on `-mom`, so I'll likely switch over to that soon enough.

Announcement copied from the main page of the FreeDOS website: " Please help us test the new release candidate (RC) for the FreeDOS 1.3 release! There are a ton of new changes and improvements from 1.2, including: * New FreeCOM 0.85a * New Kernel 2043 and an 8086 version with FAT32 support * Floppy Edition now uses compression and requires about half as many diskettes * The return of networking * Some new programs and games * Many many many package updates * Some updates and improvements to NLS * Improved install process, especially with the MBR * Some support to automatically set the COUNTRY.SYS information * Improved CD initialization for the boot media and installed system ... and much, much more! Get your copy of FreeDOS 1.3 RC5 from the FreeDOS Downloads page. Thanks to everyone for helping make this next FreeDOS 1.3 release candidate! Things are looking pretty good in this release. We'd love to make this the last release candidate before the official release of "FreeDOS 1.3." You can help make that happen by downloading FreeDOS 1.3 RC5 and testing all the programs! Let us know of any bugs or compatibility issues so we can fix them. " (*link above is to the FreeDOS 1.3 RC5 downloads page*)

Groff for Windows 10 (plus more!)
Are you a downtrodden Linux user, forced to use Windows 10 despite your wishes? Do you long to typeset with the simple and powerful groff but aren't sure if it is possible on Windows? Fortunately for the typesetting inclined, it is possible to use the magnificent *groff* on Windows as well! I decided to highlight this project in particular, because it allows one to use groff on Windows 10 in a most similar manner as on a linuxbox. The notable (*improvement?*) that this port of groff makes is automatically assuming `pdf` output, as `ps` files aren't supported out-of-the-box on Windows 10. Most importantly, the usual macros are supported as well! I don't use `-mom`, but `-ms` and `-me` seem to work flawlessly so far. The graphing package `grap` is offered too! Be sure to put the binaries in your path so they're accessible from `cmd.exe`. Coupled with *vim* and the *ezwinports' manpages*, the environment hardly feels like Windows 10 at all, which is a good thing, from my perspective. The *ezwinports* from **eli-zaretskii** on SourceForge offers much more than just groff utilites, one example being *texinfo*, so feel free to look through the rest of the software binaries offered as detailed on the README :) I would be curious to know if there ever was a Windows user who began to use groff without learning it first through a *nix operating system. Anyone know someone who fits the bill? It's a long shot, but I think it'd be a nifty thing to see. I'm certainly hoping to popularize groff within mine own circle. Wondering how I possibly could have managed to find *ezwinports*? It's front and center on the GNU page about groff: [https://www.gnu.org/software/groff/](https://www.gnu.org/software/groff/)

Questionnaire: Favorite Piece(s) of Early Music?
I thought it'd be fun to poll the community members here about some of the music they enjoy. Please share what you listen to! I am a fan of William Byrd's *Galliard*. Byrd wrote a million Galliards for various instruments, so below is one for the lute, as available on Youtube: link: https://www.youtube.com/watch?v=PaCMIdmIPRg

![](https://lemmy.ml/pictrs/image/DUWL4PY5Ku.png) Pictured above: a printout of an unformatted NRO source document (*see link at bottom to get a PostScript or Plaintext copy*) **What is NRO?** 'NRO is a text processor based on the design provided in "Software Tools" by Kernighan and Plauger.' -- taken from the NRO description (link: https://gitlab.com/FDOS/unix/nro/-/blob/master/HELP/NRO) But that's not exactly helpful, is it? Put more simply, NRO is nroff for FreeDOS. Not sure what nroff is? For the GNU/Linux user, it's the program that makes manpages look the way they do. The GNU version used for GNU/Linux is called groff. For those unfamiliar, each line beginning with a period (`.sp 2` for example) starts a formatting command. The letters specify which command is meant. All other lines contain the text that will be formatted. To learn more about nroff, look at the following Wikipeidia article on troff: https://en.wikipedia.org/wiki/Troff Or visit the related Lemmy: * https://lemmy.ml/c/groff (it's new: first post coming soon, but the sidebar has some info) **Does DOS need this? If so, why?** Good question! I am unsure. Nonetheless, it does its intended job well. It's possible to make easily readable documentation for DOS this way. However, groff can also be used for professional typesetting, akin to LaTeX, albeit with easier and simpler syntax. As I use groff primarily for this purpose, I was curious to see how the NRO version fared. For that, we turn to a printout of my NRO document: ![](https://lemmy.ml/pictrs/image/M8OESIW6MI.png) ![](https://lemmy.ml/pictrs/image/XfcQqF0G9q.png) The printout looks awful, and that's mostly due to the monospaced "typewriter font" that it's formatted with. Can this be remedied? Not without printing the document on a real PostScript printer with another font, I would think. Why don't I know for certain? *I am printing this to PDF on Linux using CUPS*, which creates a PDF document using the processed NRO output. Turning away from the font however, it's clear to see NRO did some fairly remarkable things to the source file. There is a header, an automatically numbered page, various indenting, bolded text, reasonable margins, and all the fragmented lines in the source file have been joined together to fill the page. Wow! It's just like every other word processor! But the real question is: should you start to use NRO? Probably not, unless you already use groff on GNU/Linux already, and want to continue to use it in FreeDOS. Is there a better way to produce professional looking PostScript and PDF documents in FreeDOS? Up next on my schedule is exploring TeX in FreeDOS. All the files shown here can be located / downloaded at the following address: https://github.com/sennler/nro/tree/main/EXAMPLES

Have you ever wished there were a proper desktop for your DOS system, and thought that the GUI options, like Ozone or Seal, weren't quite cutting it? They don't really come with much software integrated into the GUI, and the transition back to command line is rather jarring. What if I told you there were a better, more useful alternative? Well, thanks to TheOuterLinux (link: https://theouterlinux.gitlab.io/), there's now an excellent TUI (text user interface) desktop for DOS! Packed with tons of useful software, such as web browsers, file managers, music players, and even a lock screen, PsychDOS offers an alternative to the entirely command line driven DOS while playing to the strengths text mode offers. Get PsychDOS: https://psychoslinux.gitlab.io/DOS/INDEX.HTM Still on the fence about trying it out? Don't just take my word for it! FreeDOS founder Jim Hall provides an overview of PsychDOS on the FreeDOS YouTube channel: https://www.youtube.com/watch?v=wQCiZtnJekU Featured image: PsychDOS Page 3.5 (link: https://psychoslinux.gitlab.io/DOS/IMAGES/PAGE35.JPG) Image Attribution: TheOuterLinux Image License: https://creativecommons.org/licenses/by-nc-nd/4.0/ More PsychDOS images: https://psychoslinux.gitlab.io/DOS/SCRNSHOT.HTM

"The north-German state of Schleswig-Holstein plans to switch to open source software, including LibreOffice, in its administration and schools. In doing so, the state wants to reduce its dependence on proprietary software, and eventually end it altogether. By the end of 2026, Microsoft Office is to be replaced by LibreOffice on all 25,000 computers used by civil servants and employees (including teachers), and the Windows operating system is to be replaced by GNU/Linux." This article by Mike Saunders shows several photos from the Open Source conference, also linking to an interview with the Digital Minister Jan Philipp Albrecht and a PDF of the Parliment's Planning. (both in German)