Paged Out #6 [pdf]

I've thought about this problem a lot, and come down to the conclusion that that means that this is basically art, as opposed to pure information/an educational resource.

Art is almost always inaccessible to someone because that's part of what constitutes "art". Music is inaccessible to the deaf. Paintings are inaccessible to the blind. Food is inaccessible to those unable to smell.

If the purpose of the thing that you're creating is art, then it is necessarily inaccessible along the dimensions of your artistic freedom. (obviously, intentionally making it inaccessible along other dimensions, such as requiring a verbal test in order to view a painting, is silly, but we're not considering that) That's just what art is. That doesn't mean that you can't strive to make it a bit more accessible (e.g. with readings of content that a screen reader would have a hard time parsing), but merely that you have to acknowledge that (1) there's some parts of your art that certain people will never be able to experience (which is not your fault) and (2) that some things will be economically (in the spiritual sense, e.g. including volunteer time) infeasible to make accessible.

Conversely, if what you're making is meant to be a purely functional resource, then you should probably strive to make it accessible - but the only reason you can do this in the first place is because you've made a value decision to sacrifice aesthetics/art in the name of function.

That's a very long way of saying that I think you're taking a very reasonable position on this.

First of all let me say that I think this is a really great zine. I'm not really a zine guy, but I'm really excited about this. But, gently, let me say this format kind of sucks for reading. I generally HATE reading on paper, but this had me saying "I'd buy this on paper". My biggest gripe is I read partway through last night, and then wanted to go back to it today and my browser "suspended" that tab so I'm back at the front page. Probably like if I laid down a print pub. ;-) I guess the right answer there is to download and open it in a pdf reader.

All that said, I'd encourage you to NOT switch to HTML and leave it as PDF. There's something about it.

It would be good to figure out how many people actually care about printability. Perhaps what you could do is:

1. HTML is the primary format for articles. Authors can do whatever tricks they like in CSS, but are encouraged to make their layouts reasonably responsive. JS should be limited to things that actually benefit the article (such as LaTeX rendering or simple live examples).

2. The article must fit on one page when printed to PDF using a mainstream Web browser.

3. The author should provide a PDF file. It could just be the output of printing the HTML to PDF from a browser, or it could be something fancier, as long as it fits on a page and has the same text as the HTML version.

Looking at the most recent issue, most articles could be faithfully reproduced with a typical modern Markdown implementation (one that supports tables and code highlighting, and maybe LaTeX math) and some simple CSS.

Printable subscription would be nice. It often times just helps financing the venture, as well as for sponsors to have something on hand.

I'd still keep in mind that this format severily limits reach in times where short (kudos for one page thing!) and accessible form is an expectation.

Nevertheless - I will keep reading and spreading the word.

Tangenatially. How would audio reading work for posts with code samples and diagrams in it? Do you have an example of that?

Setting some gentle publication conventions could help a lot with this. For example, requiring two-column or three-column format greatly improves article readability on mobile.

Sadly that's not doable for us. LaTeX, for all its benefits, has terrible user experience and would drive away a lot of authors. One of the benefits of using PDFs is that anyone can use almost any tool they feel comfortable with to make the article (except for Photoshop - we banned Photoshop PDFs because they are ridiculously constructed). For example, I use Google Slides for my articles (which seems like a weird choice, but it's so easy to do complex one-of formatting in it).

If you're interested to explore lots of XSS edge cases, I've found this CTF to be enjoyable.

https://alf.nu/alert1

All JSON serializers worth their salt can serialize a single string to JSON, so the simplest way is to do json.dumps(the_string) and mark the string as safe so that it doesn't get escaped twice.

Encoding for each scenario can be quite complex unfortunately. Django does have some template filters to help.

I recommend following the documentation carefully, and using a JSON API or other similarly standard mechanism if the documented options are insufficient.

Thanks for raising this question, and I agree it is important. Maybe encouraging independence from the russian oil would be a more efficient way to go. Of course, it can't happen immediately, but if some countries consciously don't want to work in this direction - such situation may constitute a safety threat to Europe - and this shouldn't be left without attention.

in my opinion there is a pragmatic aspect to it,

to put it simply, the taxes paid go to finance "whatever their government are doing".

also, do you think, like - all russians are against the war and don't have imperialistic mindset. it's just their government to blame? I'd say there is a decent part that got affected by propaganda both imprinted into education and news.

I don't know about the artists contributed to the journal (do you?), but in my opinion it is just a safer bet to find an artist unrelated to Russia.

apart from that, promoting russian culture (i.e works by russian artists) while it is actively destroying culture of other countries - means contributing to the process.

Not who you are replying to but thanks for mentioning lulu.com - I have a camera manual pdf that I have been meaning to get printed as a spiral bound book and their rates look quite reasonable.