McSinyx @mcsinyx@librem.one

What's up with people exploting production systems in the name of research and acting surprised when the security issues is tackled?
https://discuss.python.org/t/8710

This track was on fire and Hopsin literally killed it: https://www.youtube.com/watch?v=LsV2GWlGh-o

Now I'm hyped for Minor Disturbance!

@SuricrasiaOnline, since NT there is chntpw

This reminds me of the good ole xfishtank, @huy_ngo

@hund, in theory you can force the client to display it as flowed and in most of the cases it won't break. Though such behavior is nonstandard and you'll need to advocate hard for your client to support it.

Cc: @huy_ngo, @pizza_pal

@huy_ngo and @pizza_pal, that's when we only consider some human languages in discussion mode. Poems should be soft wrapped in a special way or never at all, and code snippets (the new kind of poems) must be displayed as-is, since whitespaces play an important role in readability.

People working together must agree upon the width, some will be unhappy, but if it's not clear already, dealing with code on a phone screen is good for neither eyes nor mental health.

@huy_ngo, for plaintext documents, hard wrapping is to aid version control and CLI tools (it's drastically easier and cheaper to work on the basis of lines instead of words), so basically we're limited by the technology of our time. Documents in markup languages can be reformatted or graphically rendered when represented to users though.

Emails are a bit different. There is format=flowed, but it's only supported by like half of the email clients.

Cc: @pizza_pal

Oh the irony, @huy_ngo, that the blogspam uses Google Analytics. Here is the original article: https://signal.org/blog/the-instagram-ads-you-will-never-see