If you have resources, please install Archiveteam’s warrior program to contribute to the project! We’re already up to 11TB and 187 million pages archived, but we’re going to need a lot more help to get all the NSFW content before the 17th!
irc is #tumbledown on efnet, you can add blogs to be saved at
@staff won’t improve anything just because you talk shit about them
go join a better social network if you want, you know, ACTUAL CHANGE
https://joinmastodon.org/ is highly recommended as it is free software that you can host yourself and is very user friendly and already has tons of mobile apps
it is built on open protocols so you can talk effortlessly with people on other kinds of instances, like Pleroma, or follow the uploads of Peertube users, which is a peer to peer youtube alternative
our admins are not beholden to shareholders or profit of any kind, only to us, users
and if you don’t like your admins, you can easily make your own server and still communicate with others
Tumblr was deemed too full of inappropriate content to be allowed to be downloaded from the app store.
It has this “inappropriate” problem because of rampant porn ad bot accounts. The old solutions were bots to detect image sets with nsfw content, the automatically enabled safe mode, tag filtering for mobile, and wide takedowns of nsfw bots based on words used (that’s why their messages are full of numbers and symbols, to evade this)
Tumblr released their own bot supposedly capable of wiping the ad bots, but it’s taking down many popular blogs, possibly due to sheer amounts of posting or sheer amounts of ad bots in their notes. This bot was likely rushed to be put out.
You are more likely to be accidentally flagged if you post external links, as well. If your acct is taken down you CAN get it back, but it’s a pain. E-mail tumblr support for help with this. It takes down side blogs with the main ones.
I’ll be halting posts for about a week or until this problem is fixed.
JUST
USE
A
BETTER
SOCIAL
PLATFORM
such as mastodon :)
fuck centralized social networks (twitter, facebook, tumblr)
REMINDER THAT WHENEVER @staff FUCKS UP YOU CAN GO JOIN ONE OF THESE FOR ABSOLUTELY NO COST WHATSOEVER AND JOIN A COMMUNITY WHERE THE ADMINS ACTUALLY CARE ABOUT YOU INSTEAD OF PROFIT
still picking at this, eight months or so on. i stalled out for a while convinced i’d started something i didn’t have the ability or skill to finish, but having done too much to trash it. bits and pieces have been beginning to make more sense as i poke at other, smaller things on the side.
“Personal piece about an idea I had in mind since a few weeks : A cyborg
hacker that use Biologic technologies to physically propagate
viruses/worm and take over any kind of computer facility”
Learn how to read source code. It is an extremely valuable skill.
Everyone who has written software knows that reading source code is generally more difficult than writing it. This is because you have to lower yourself to the level of the (virtual) machine running it. You have to lower your level of abstraction and understand what is probably going on behind function calls that you haven’t written. On top of that, you have to then place yourself in the mindset of the author. This is not easy. Once you can do this, however, you can start truly reading code.
Like all useful skills, the ability to read code comes with practice. Maybe you’ll have to read some really old legacy code - maybe something with syntax in all-caps, or code that has “just worked” chugging along for the past 22 years since the intern who wrote it left. These are the programs that use some kind of miraculous self-modifying state with a use-after-free hack, with more lines that invoke undefined behavior than lines which don’t. (As an aside: if you have not seen these programs yet, wait until you get a job in the Real World ™. They’re everywhere.)
This takes a while. It has to do with time and experience, but moreso an effort and a want to read code. It sucks to do things you suck at. It sucks even more when you’re trying to do things you suck at (reading another person’s code) when you thought you were actually really good at it (reading your own code). It’s like wading through mud - you’re trying to accomplish something useful, doing something you’ve normally been good at, and now you’re working towards this same goal (understanding the program) but at an painfully slow pace, with every mistake reminding you how much you suck at it.
It’s worth it. If you’re looking at horrendously written code - of which you will be reading a lot in your career - there is a very good chance you are in a place where you can make an effort to re-write it. And depending on the size of the codebase, you can probably start fixing horrendous code, if you’re in a position to do so. Or, if you are not so much in the corporate world, or work for a company where you aren’t exposed to horrible code (congratulations!) you can funnel your efforts towards open source. Plenty of open source projects of great significance could use your help. Maybe you’ll look at the source to the program you’re using, and you can figure out why it’s not behaving how you expected it to. If you get REALLY crazy, you may even write up a patch and send it to the author. Think of it as your contribution to society.
After you have learned to read code, I would personally expect you’ve learned a thing or two from what other people have written. You’ve learned how not to do things, but hopefully learned some good design patterns through reading good code. These patterns will be echoed in whatever code you write. If you’ve reached this point then point it’s safe to say: you’ve become a much better programmer as a side effect of being able to read code.
