| 00:00:38 | | yarrow2 quits [Client Quit] |
| 00:04:23 | | yarrow quits [Read error: Connection reset by peer] |
| 00:05:49 | | yarrow (yarrow) joins |
| 00:30:37 | | nepeat quits [Ping timeout: 272 seconds] |
| 00:32:26 | | nepeat (nepeat) joins |
| 00:39:46 | <fireonlive> | hello |
| 00:42:18 | <Flashfire42> | hi |
| 00:55:54 | <fireonlive> | :) |
| 01:20:38 | <yarrow> | hey |
| 01:49:47 | <lemuria> | morning |
| 01:49:52 | <lemuria> | how's the archiving going |
| 01:51:10 | <fireonlive> | https://x.com/polymarket/status/1815115526043017727?s=12 |
| 01:51:10 | <eggdrop> | nitter: https://nitter.poast.org/polymarket/status/1815115526043017727 |
| 01:51:12 | <fireonlive> | holy FUCK lol |
| 01:51:33 | <lemuria> | big financial L |
| 01:52:11 | <lemuria> | now donate it all to archiveteam and IA, 50/50 split or else ./s |
| 02:12:22 | <fireonlive> | yeeee |
| 02:25:47 | | etnguyen03 quits [Client Quit] |
| 02:31:46 | | yarrow quits [Read error: Connection reset by peer] |
| 02:33:42 | | yarrow (yarrow) joins |
| 02:34:55 | | Notrealname1234 (Notrealname1234) joins |
| 02:35:22 | | Notrealname1234 quits [Client Quit] |
| 02:52:29 | <pabs> | https://fee.org/articles/un-deletes-article-titled-the-benefits-of-world-hunger-was-it-real-or-satire/ |
| 02:56:10 | <pabs> | fireonlive: nitter.poast.org has some sort of verification crap, isn't there a better nitter instance? |
| 03:30:29 | <lemuria> | i've had luck with xcancel |
| 03:49:25 | <pabs> | just as bad IIRC |
| 03:49:51 | <pabs> | just wants a captcha right now, which doesn't work without JS |
| 04:01:22 | <@OrIdow6> | All the ones I've checked out as of late use a CAPTCHA |
| 04:01:49 | <@OrIdow6> | makes sense, I used to see stuff that would use public Nitter instances in order to fetch stuff from Twitter |
| 04:02:12 | <fireonlive> | sadly i don't know of any :( |
| 04:02:23 | <fireonlive> | there's privacydev but it's overloaded a bit |
| 04:05:33 | | ilnrja quits [Remote host closed the connection] |
| 04:05:55 | | ilnrja (ilnrja) joins |
| 04:29:46 | | wickedplayer494 quits [Ping timeout: 255 seconds] |
| 04:30:22 | <yarrow> | there are many mirrors |
| 04:30:37 | | wickedplayer494 joins |
| 04:30:49 | | wickedplayer494 is now authenticated as wickedplayer494 |
| 04:32:43 | <yarrow> | https://github.com/zedeus/nitter/wiki/Instances |
| 04:33:42 | | wickedplayer494 quits [Remote host closed the connection] |
| 04:34:05 | | wickedplayer494 joins |
| 04:39:39 | | wickedplayer494 is now authenticated as wickedplayer494 |
| 04:43:00 | <yarrow> | oh, I guess most aren't working, though |
| 04:45:13 | | qw3rty__ quits [Ping timeout: 272 seconds] |
| 04:51:00 | | qw3rty__ joins |
| 05:04:55 | | shgaqnyrjp_ (shgaqnyrjp) joins |
| 05:05:09 | | shgaqnyrjp quits [Remote host closed the connection] |
| 05:42:40 | | wickedplayer494 quits [Ping timeout: 255 seconds] |
| 05:43:12 | | wickedplayer494 joins |
| 05:56:04 | | DogsRNice quits [Read error: Connection reset by peer] |
| 06:15:24 | | lemuria is now known as lemuria_ |
| 06:15:35 | | lemuria_ is now known as lemuria__ |
| 06:15:41 | | lemuria__ is now known as lemuria |
| 06:25:27 | | shgaqnyrjp_ is now known as shgaqnyrjp |
| 06:30:26 | <qwertyasdfuiopghjkl> | fireonlive: The nitter.poast[.]org instance appears to be malicious (run by nazis), so you should change the one eggdrop links to to one of the other currently functional ones from https://status.d420.de/ . (Source: according to https://seirdy.one/posts/2023/05/02/fediverse-blocklists/ (ctrl+f poast), the domain is also used for a nazi fediverse |
| 06:30:27 | <qwertyasdfuiopghjkl> | instance, and the name of the person whose post is linked as evidence also matches the reddit username of someone claiming to run the nitter instance: https://old.reddit.com/r/nitter/comments/1bmk7tc/a_nitter_instance_that_still_works_almost/kwfzdvi/ ) |
| 06:38:55 | <steering> | poast is by far the most reliable instance. |
| 06:40:18 | <steering> | I'm not sure how a separate service on the same domain being bad makes the nitter instance "malicious", do you have f.e. any evidence of it changing or hiding tweets? |
| 06:41:01 | <steering> | That's about the only "malicious" thing a service which is effectively just a proxy can do. |
| 06:46:37 | | BlueMaxima quits [Read error: Connection reset by peer] |
| 06:51:09 | <qwertyasdfuiopghjkl> | It is run by the same person: https://seirdy.one/posts/2023/05/02/fediverse-blocklists/ links to a post by @graf@poa[.]st ( https://archive.today/suzOG ) who is listed as the owner of both poa[.]st ( https://archive.today/dEdIl ) and poast[.]org ( https://archive.today/Rcxjl ), and their display name is the same as the reddit user running the |
| 06:51:09 | <qwertyasdfuiopghjkl> | nitter instance (though since the domain name matches, that is kind of redundant). |
| 06:56:31 | <tek_dmn> | One of them has to be an attempted refresh or something if that's the case. Different registrars, different ASNs (though one is CloudFlare so that doesn't mean much), and yet those pages are identical. (and funnily enough poast[.]org doesn't want to resolve half the time because NXDOMAIN) |
| 06:56:34 | <qwertyasdfuiopghjkl> | (I don't have any evidence of it having done anything malicious yet, but I also wouldn't trust any site run by nazis to *not* be malicious.) |
| 06:57:35 | <steering> | It's pretty well known they're run by the same person. |
| 06:58:58 | <tek_dmn> | I, personally would refrain on actually labelling something 'malicious' if the best evidence you have is 'wouldn't trust any site run by nazis to *not* be malicious,' but I also don't really have a horse in this race. "I don't trust that one, look at it's ownership" is a bit different than "it's malicious, I have no evidence it is but I wouldn't trust that it's not, so it is" |
| 06:59:44 | <steering> | ^ |
| 07:00:50 | <steering> | I would love to replace it for my own use, but then I'd have to deal with constantly switching between 3 different instances that are probably all broken... (which is something that I did for a while last year and am not eager to do again) |
| 07:01:20 | <tek_dmn> | I'd bring one up myself if I had the capability. I have a feeling I do not though. |
| 07:05:16 | <steering> | Any public instance will immediately get inundated by scrapers, so you have to do something about those. Then, you have to keep changing things to keep up with Xhitter's changes. And then AIUI you need enough Twitter accounts to get enough tokens to have a high enough rate limit to serve all your users. |
| 07:05:38 | <tek_dmn> | exactly. |
| 07:06:03 | | wickedplayer494 is now authenticated as wickedplayer494 |
| 07:06:54 | <steering> | https://github.com/zedeus/nitter/issues/1201 has discussed this same topic BTW (completely with comment from graf, the owner) |
| 07:09:37 | <qwertyasdfuiopghjkl> | What I meant by "appears to be malicious" is that since it is under the same domain (+ run by the same user) as another website I *would* consider to be in the category of "malicious" (fediverse instance hosting nazis), anything else under that domain should be considered malicious until proven otherwise (doing which is basically impossible, since |
| 07:09:37 | <qwertyasdfuiopghjkl> | you can't prove a site serves the same content for everyone or isn't spyware on the server side). |
| 07:12:06 | <tek_dmn> | I would argue then, it does not "appear" to be malicious as there is nothing on the site itself that is apparently malicious. Just that it's untrustworthy. I can't prove it's not spyware. You, similarly, cannot prove that it is. |
| 07:12:21 | <steering> | Well, feel free to figure out another instance that is consistently functional; I'd love to hear it. |
| 07:12:48 | <tek_dmn> | What next, should I remove using any instances of software if the owner of the software was quotes by a known nazi since now that owner is malicious? |
| 07:13:16 | <steering> | Twitter also hosts nazis, but you don't seem to consider (the content on) Twitter to be malicious? |
| 07:18:16 | <tek_dmn> | Or, to put it another way: there is a reason that American law (at least) is (supposed to be) built off the 'innocent until proven guilty' premise. The moment that switches, then nothing is good, because everything can be linked back to something if you want to follow enough links. I could probably point to any fediverse server (not just Mastodon instances) and come up with a chain of relations that ends in a nazi. You have to like, prove |
| 07:18:16 | <tek_dmn> | your website is bad before it should be removed. |
| 07:18:18 | <qwertyasdfuiopghjkl> | tek_dmn: That depends on how much you trust the owner of a software to not add anything malicious (note that in this specific case, the owner *is* a nazi, instead of just quoting one (which could happen by accident, depending on the context)) |
| 07:18:41 | <tek_dmn> | Yes. But who's making that decision? |
| 07:20:21 | <tek_dmn> | Because "it's malicious and you should use another one" takes my trust about what I use for my purposes out of the picture by demanding it be replaced. "Hey; the owner is a nazi, trust at your own risk" allows the people using the thing to make up their mind instead of trying to make it up for them. |
| 07:22:17 | <tek_dmn> | The moment we get into "you should block this because they MAY have done something, I don't know, but you can't prove they didn't" is the moment I get into why Minority Report is not meant to be a documentary. You should not be guilty of a crime you "could" have committed. A website is not malicious unless it is "shown" to be malicious. It can be untrustworthy, it can be one that you don't feel good about, it can be one that you find likely is, |
| 07:22:17 | <tek_dmn> | but you cannot conclusively label a site for something the site has not demonstrated. |
| 07:23:48 | <qwertyasdfuiopghjkl> | tek_dmn: Anyone using the software can obviously decide for themselves if they want to continue using it, but they should still be aware that something's sketchy to be able to make an informed choice. (You can of course continue using it if you still believe it to be trustworthy, but some other people might decide otherwise themselves.) |
| 07:23:50 | <tek_dmn> | And the point I was making there was the question of "if we can claim the possibility of malice, as direct malice, then where does the boundary of malice stop? The fact that fedi (sometimes) defeds over sneezing the wrong way is, overbearing, but a fine example of that question. |
| 07:24:45 | <tek_dmn> | And "this appears to be malicious" is making that choice up for them by telling them not that it might be a problem but that it is |
| 07:49:27 | <qwertyasdfuiopghjkl> | (replying to https://hackint.logs.kiska.pw/archiveteam-ot/20240722#c446030 ) In this case, the chain of relations is just one person long, *the actual owner of the site*. |
| 07:49:31 | <qwertyasdfuiopghjkl> | (replying to https://hackint.logs.kiska.pw/archiveteam-ot/20240722#c446035 ) I'm not "demanding" anything is replaced, I'm just informing someone who uses a thing that there's something suspicious going on with it. Also, I said that it *appears* to be malicious, but I don't think what specific wording I used matters that much. |
| 07:49:35 | <qwertyasdfuiopghjkl> | (replying to https://hackint.logs.kiska.pw/archiveteam-ot/20240722#c446036 ) I'm not saying that they're legally guilty of something, I'm saying that *I think* the site is likely to be malicious. (In that message, I also wasn't talking about blocking anything, but informing someone that they might be unknowingly linking to a malicious website.) |
| 07:49:39 | <qwertyasdfuiopghjkl> | (replying to https://hackint.logs.kiska.pw/archiveteam-ot/20240722#c446039 ) The admin calling people various slurs and being nazis is *NOT* equivalent to "sneezing the wrong way"! |
| 07:50:29 | <qwertyasdfuiopghjkl> | tek_dmn: ^ |
| 07:51:09 | <tek_dmn> | Either I'm too autistic to English or you're doing the thing everyone does, which is mistaking an example for an argument |
| 07:52:25 | <tek_dmn> | as given by "a fine example of that question" and "that question" being "if we can claim the possibility of malice, as direct malice, then where does the boundary of malice stop?" which has actually nothing to do with the actions of the current person or site being discussed... just your announcement. |
| 07:52:58 | <tek_dmn> | the chain of relations, is irrelevant as that was an example of "if we can claim the possibility of malice, as direct malice, then where does the boundary of malice stop?" |
| 07:53:18 | <tek_dmn> | do you see a pattern or do I need to explain the remark about legal guilt as well? |
| 07:57:12 | <qwertyasdfuiopghjkl> | I'm not claiming the nitter instance as "direct malice", I'm claiming that there is a (in my opinion, high) possibility that it's malicious, since it's closely related to another site I consider malicious. You're trying to nitpick the specific wording I used. |
| 07:57:23 | <tek_dmn> | Correct. |
| 07:57:37 | <tek_dmn> | That... is what I've been doing, this entire time. |
| 07:58:41 | <tek_dmn> | and I will demonstrate that, like so: |
| 07:59:49 | <tek_dmn> | (with sarcasm) Hey everyone, you should add steering to your client's ignore list. They appears to be malicious (link to a site owned by a nazi). I can't prove they're doing anything harmful, but the possibility is there and you can't prove they're not! |
| 08:00:04 | <tek_dmn> | my grammar is GREAT at 4 AM, let me tell you. |
| 08:04:58 | <qwertyasdfuiopghjkl> | I was not calling anyone malicious for linking to it, I was informing them that they might accidentally be linking to something malicious. I also mentioned in parentheses that the reason I considered it malicious was that it was run by nazis, and listed the evidence I used to come to that conclusion. |
| 08:05:40 | <tek_dmn> | When did I say you were? |
| 08:05:48 | <qwertyasdfuiopghjkl> | (replying to https://hackint.logs.kiska.pw/archiveteam-ot/20240722#c446029 ) steering: I do consider the *nazi* content on twitter malicious, but in this case the site *is specifically for/supports* the nazi content. |
| 08:13:21 | <qwertyasdfuiopghjkl> | tek_dmn: You implied in https://hackint.logs.kiska.pw/archiveteam-ot/20240722#c446054 that my intent was to blame fireonlive for linking to nitter.poast[.]org and imply they were doing so maliciously, while my actual intent was the opposite (notifying them that the instance they were automatically linking to was potentially malicious and they |
| 08:13:22 | <qwertyasdfuiopghjkl> | should probably change it to a less sketchy one or at least add a warning message). |
| 08:13:33 | <tek_dmn> | I never implied that, actually. |
| 08:14:20 | <tek_dmn> | I said I've been nitpicking your wording, demonstrating as such by using nearly identical wording in a similar message that is obviously incorrect. |
| 08:15:33 | <tek_dmn> | the fact that you just admitted "my intent was to [...] imply they were doing so maliciously" actually proves my exact point: your wording ("appears to be malicious") implies that the site is malicious. Not that it *can be* but that it *is*. |
| 08:15:44 | <tek_dmn> | let me rephrase that |
| 08:16:29 | <tek_dmn> | the fact that you just admitted "you implied [...] that my intent was to" ... There we go. |
| 08:17:31 | <tek_dmn> | I used the exact same warning you did. But when you did it, it's just to let them know it's potentially malicious. When I did it, it's to imply it's malicious. |
| 08:19:30 | <qwertyasdfuiopghjkl> | Could you please rephrase that? I'm not sure which "it" you're referring to. |
| 08:26:29 | <tek_dmn> | When you said "appears to be malicious" it was to warn of a potential possiblity. When I said "appears to be malicious," you interpreted that as implying malice. That is two completely different readings, from the same four words. The exact thing I've been getting at this entire time. It's not that you're incorrect. It's that your wording could use a little more clarity. |
| 08:37:53 | <qwertyasdfuiopghjkl> | Ahh, I think I get it now. I think I was misinterpreting you as trying to argue that the nitter instance couldn't be *suspected* of being malicious for being hosted by nazis, while you were actually trying to argue that it couldn't be *proven* to be malicious solely based on it being hosted by nazis. (or at least I'm guessing that's what you |
| 08:37:54 | <qwertyasdfuiopghjkl> | meant.) Apologies for the confusion. |
| 08:43:28 | <qwertyasdfuiopghjkl> | (I think part of the confusion might be that I might have a broader interpretation of what I consider to fall under the category of "malicious website" than just the cybersecurity stuff) |
| 08:51:13 | | qw3rty__ quits [Ping timeout: 255 seconds] |
| 08:58:07 | | qw3rty__ joins |
| 09:00:02 | | Bleo1826007227196 quits [Client Quit] |
| 09:01:28 | | Bleo1826007227196 joins |
| 09:28:44 | | yarrow quits [Read error: Connection reset by peer] |
| 09:36:50 | | yarrow (yarrow) joins |
| 11:00:03 | | Bleo1826007227196 quits [Client Quit] |
| 11:01:22 | | Bleo1826007227196 joins |
| 13:17:43 | <Harzilein> | personally i link to twiiit.com that i know nothing of and i just hope it only chooses its redirects on technical grounds |
| 13:26:32 | | icedice quits [Client Quit] |
| 13:57:29 | | katocala quits [Ping timeout: 272 seconds] |
| 13:57:46 | | katocala joins |
| 13:57:46 | | katocala is now authenticated as katocala |
| 14:07:37 | | katocala quits [Ping timeout: 272 seconds] |
| 14:08:31 | | katocala joins |
| 14:08:31 | | katocala is now authenticated as katocala |
| 14:21:41 | | PredatorIWD joins |
| 15:19:49 | | Doranwen quits [Ping timeout: 272 seconds] |
| 15:25:21 | | Doranwen (Doranwen) joins |
| 15:35:01 | | qw3rty__ quits [Ping timeout: 272 seconds] |
| 15:36:13 | | Doranwen quits [Ping timeout: 255 seconds] |
| 15:36:17 | | that_lurker quits [Ping timeout: 272 seconds] |
| 15:38:25 | | Doranwen (Doranwen) joins |
| 15:41:16 | | qw3rty__ joins |
| 16:04:06 | | PredatorIWD quits [Read error: Connection reset by peer] |
| 16:07:41 | | PredatorIWD joins |
| 16:30:46 | | BPCZ quits [Quit: eh???] |
| 16:32:06 | | Bleo1826007227196 quits [Client Quit] |
| 16:32:28 | | Bleo1826007227196 joins |
| 16:33:01 | | BPCZ (BPCZ) joins |
| 16:42:10 | | briansxml joins |
| 16:42:20 | | briansxml quits [Client Quit] |
| 17:39:11 | | Juesto (Juest) joins |
| 17:41:41 | | Juest quits [Ping timeout: 272 seconds] |
| 17:41:41 | | Juesto is now known as Juest |
| 18:46:43 | | DogsRNice joins |
| 19:27:19 | <Barto> | qwertyasdfuiopghjkl: i was the one person suggesting to use this nitter instance for the single reasons that privacydev's one had a harsher rate limit. I was not aware of anything else. |
| 19:27:38 | <Barto> | qwertyasdfuiopghjkl: fireonlive cannot take the blame of this |
| 19:43:14 | | wickedplayer494 quits [Read error: Connection reset by peer] |
| 19:45:14 | | wickedplayer494 joins |
| 19:45:46 | | wickedplayer494 is now authenticated as wickedplayer494 |
| 19:47:40 | <qwertyasdfuiopghjkl> | I don't see there being any reason to blame anyone, and it's not like it was easily possible to notice this, especially since the other site wasn't up on that domain at the time. (I discovered the issue because I vaguely recalled having seen a similar domain in some blacklist at some point in the past and looked it up, probably wouldn't have found |
| 19:47:40 | <qwertyasdfuiopghjkl> | it otherwise.) |
| 19:58:58 | <@OrIdow6> | This Nitter page is faking data? |
| 20:05:18 | | nukke quits [Quit: nukke] |
| 20:08:06 | | nukke (nukke) joins |
| 20:32:43 | <qwertyasdfuiopghjkl> | OrIdow6: I'm not aware of it faking any data (but if it ever did, I likely wouldn't be able to tell anyway, since I haven't cross-checked anything and won't be using it in the future). The issue is that it's run by nazis (see https://hackint.logs.kiska.pw/archiveteam-ot/20240722#c446000 ) and thus likely to be some kind of malicious (or become so |
| 20:32:44 | <qwertyasdfuiopghjkl> | in the future). Since https://status.d420.de/ has 3 mostly functional alternatives *not* known to be run by nazis, nitter.poast[.]org should be avoided unless (and possibly even if) none of the others are available and you accept the risk of data manipulation and whatever else a malicious website could do. |
| 20:45:54 | <myself> | It'd be interesting to occasionally query two and compare the results to detect such manipulation if it happened |
| 20:48:48 | <Flashfire42> | I concur with myself on this matter. Whilst I defs dont approve of Nazis would be interesting to see if there is any data manipulation. tho like it or not nazis are good at hiding from being shut down |
| 21:01:19 | <@OrIdow6> | qwertyasdfuiopghjkl: Honestly I don't see much of a risk to using it; seems the biggest thing they could do is redirect to goatse or something, and that's a lot of effort for something that'll quickly have everyone stop using it |
| 21:02:17 | <qwertyasdfuiopghjkl> | myself, Flashfire42: I think it'd be very unlikely to actually find any data manipulation even if there is any, since there's a JS requirement, we wouldn't know which of the billions of tweets to check, and even if we somehow happen to check the right one, they might only show bad data to users who don't look like an automated check. |
| 21:04:20 | <@OrIdow6> | And this is just for the convienent viewer bot, I don't believe we're using Nitter as a shim to AB Twitter anymore |
| 21:04:48 | <thuban> | there are no specific allegations; mitming nitter would require significant effort for (given the ease of checking against other instances or twitter itself) minimal benefit; furthermore, a nefarious actor (whether planning an mitm attack, malicious scripting, or some other malfeasance) would obviously be better off starting with a 'clean' domain and identity than affiliating |
| 21:04:50 | <thuban> | openly with poa.st. |
| 21:04:54 | <thuban> | as nitter is a cost to the instance operator rather than a benefit, and as ime nitter.poast.org is much more reliable than the other surviving nitters (that uptime graph doesn't account for rate limiting), i for one will continue using it |
| 21:04:56 | <thuban> | (i wouldn't use it for archival purposes, but i wouldn't use any third-party nitter for archival purposes) |
| 21:05:17 | <thuban> | OrIdow6: no, and when we did they were semi-private instances operated by at memebers |
| 21:07:50 | <thuban> | *members |
| 21:18:50 | <@JAA> | lemuria, TheTechRobo, kpcyrd, thuban: The $2000/TB figure is basically Moore's law but for storage. If you assume that disk space gets exponentially cheaper over time, a finite amount of money does buy you indefinite storage duration because the replacement hardware gets cheaper over time sufficiently fast. The exponential decrease of storage cost has been true for many decades, although it doesn't |
| 21:18:56 | <@JAA> | look like it anymore recently. The $2000/TB figure is at least several years old, too, though; I wouldn't be surprised if it predates the 2011 flooding of Taiwanese HDD manufacturing plants. |
| 21:30:58 | | midou_ joins |
| 21:32:13 | | midou quits [Ping timeout: 272 seconds] |
| 21:32:37 | | midou_ is now known as midou |
| 21:33:02 | <qwertyasdfuiopghjkl> | OrIdow6, thuban: Even if you don't consider the risk of malware, spyware and data manipulation as high, it's still significantly higher than it'd be if you if you tried the other 3 instances first. A nitter instance will also get you more clicks/potential malfeasance victims than some other site, especially if it's considered "much more reliable |
| 21:33:03 | <qwertyasdfuiopghjkl> | than the other[s]". The biggest problem though is that by eggdrop automatically (or others manually) linking to it, we would be subtly promoting a nazi site every time someone posts a Twitter link. Adding a warning after the link wouldn't be much of an improvement, since that would just change it to *unsubtly* promoting a nazi site. |
| 21:43:34 | <thuban> | i don't agree either that the risks are "significantly higher" (again, if you want clicks, why use a name you know will result in people being told to avoid you?) or that linking to a nitter instance is endorsement of the domain owner's attitudes |
| 21:51:20 | <qwertyasdfuiopghjkl> | thuban: Given that IIRC when we were using it earlier noone noticed for *months*, it's not that easy to find out about it if you don't suspect something's off. I also think that they might be using the nitter instance to advertise/promote/SEO/whatever their nazi fediverse thing, so we should avoid giving them more clicks. Also, I think most people |
| 21:51:21 | <qwertyasdfuiopghjkl> | would interpret linking to a nazi-affiliated site as endorsement of nazis, especially if the people linking are aware of the nazis and non-nazi alternatives exist. |
| 21:53:00 | | etnguyen03 (etnguyen03) joins |
| 21:57:08 | <qwertyasdfuiopghjkl> | (I would avoid automatic linking even if it *was* the only option, and when linking to it manually is needed for whatever reason, link to it with the URL escaped like example[.]com/whatever and accompanied by a warning about the nazis.) |
| 22:00:16 | <qwertyasdfuiopghjkl> | Currently, fireonlive can just change the nitterizer to use one of the other 3 working instances so this won't be a problem, but in the event all 3 go down, it'd be better to disable it entirely than change it back to nitter.poast[.]org, since anyone who chooses to risk using it despite the potential maliciousness can set up a redirect via a |
| 22:00:16 | <qwertyasdfuiopghjkl> | browser extension for themselves anyway. |
| 22:03:11 | <qwertyasdfuiopghjkl> | (might have posted the last 2 messages out of order since I forgot one was in my clipboard while replying to t.huban's message and hadn't been sent yet) |
| 22:08:07 | <kpcyrd> | JAA: does this count as longing the dollar? |
| 22:37:02 | | BlueMaxima joins |
| 22:37:09 | | pseudorizer quits [Client Quit] |
| 22:38:08 | | pseudorizer (pseudorizer) joins |
| 22:40:07 | | midou quits [Ping timeout: 255 seconds] |
| 22:51:34 | | BearFortress_ joins |
| 22:54:58 | | BearFortress quits [Ping timeout: 255 seconds] |
| 22:55:47 | <thuban> | qwertyasdfuiopghjkl: which is it--it's so obscure that no one could notice the association with poa.st, or it's deliberately enticing people to poa.st? (if it were purely technical seo, again, clean name.) |
| 22:56:07 | <thuban> | given reasonable confidence in the quality of the service relative to the risk--which i have for the reasons outlined above--i would happily (and even in preference) read tweets on literal hitler's dime, because i don't want literal hitler to have money. |
| 22:56:21 | <thuban> | (taint-by-otherwise-harmless-association is created primarily by people expecting dissociation; if you convince enough people 'wearing blue jeans means you support X', well, it does _now_. i think it's important to be resistant to such claims for this reason.) |
| 22:58:05 | <thuban> | but it sounds like your concern about endorsement is independent of your concern about malice, so i don't think further argument would be productive here (and i fear would get too general/disruptive) |
| 23:25:55 | <imer> | if anyone ever wants to brick their docker install, attempt to create a ipv6 network and miscalculate the mtu so it ends up smaller than the minimum of 1280, real fun to debug that one lol |
| 23:26:30 | <imer> | all sorts of bizzare errors that arent cleared by deleting the containers/network (docker system prune -af did the trick after deleting everything related) |
| 23:47:26 | <qwertyasdfuiopghjkl> | thuban: I'll reply to each of your messages separately (took a while to write) |
| 23:47:33 | <qwertyasdfuiopghjkl> | (replying to https://hackint.logs.kiska.pw/archiveteam-ot/20240722#c446192 ) The site at poast[.]org might return at some point. Some of the people who are unaware of poast specifically, might be sympathetic to nazis or susceptible to nazi propaganda, potentially resulting in an increase of donations to the malicious fediverse instance, which would |
| 23:47:33 | <qwertyasdfuiopghjkl> | be counterproductive to your next point. |
| 23:47:35 | <qwertyasdfuiopghjkl> | (replying to https://hackint.logs.kiska.pw/archiveteam-ot/20240722#c446193 ) I agree, but the link should always be given alongside an explanation of that, so people can decide for themselves if they accept the risk increase in exchange for slightly increasing the nazis' server costs (which might not even occur if they're paying a flat monthly |
| 23:47:36 | <qwertyasdfuiopghjkl> | rate, so you should try to figure that out first). |
| 23:47:39 | <qwertyasdfuiopghjkl> | (replying to https://hackint.logs.kiska.pw/archiveteam-ot/20240722#c446194 ) Yes, but in this case there's 4 brands of blue jeans (nitter instances), one of which is produced (hosted) by nazis, so specifically promoting Nazi Jeans (nitter.poast[.]org) over the other brands has a certain implication, even if you say you're doing it because of other |
| 23:47:39 | <qwertyasdfuiopghjkl> | reasons like "higher quality" (since the actual nazis tend to do that too, to avoid blatantly giving themselves away/getting banned/etc.). |
| 23:47:43 | <qwertyasdfuiopghjkl> | (replying to https://hackint.logs.kiska.pw/archiveteam-ot/20240722#c446195 ) They're mostly independent, but there's some overlap in promoting something that eventually might get people hacked via some browser vulnerability or do something else harmful. |