Inex.rocks - Revision history

Woozle: Woozle moved page Pub/inex.rocks to Inex.rocks: eliminating "pub"

2022-11-12T15:46:11Z

Woozle moved page Pub/inex.rocks to Inex.rocks: eliminating "pub"

← Older revision	Revision as of 15:46, 12 November 2022
(No difference)

Woozle at 15:45, 12 November 2022

2022-11-12T15:45:53Z

← Older revision		Revision as of 15:45, 12 November 2022
Line 1:		Line 1:
			[[category:instance]]
	==2020-07-22 Domain unblocked==		==2020-07-22 Domain unblocked==
	...after repeated (but patient and reasonably polite) inquiries from their sysop [https://enigmatic.observer/users/inex Inex Code], I told them<ref name=tc1 /> basically this (but referring to them in 2nd person):		...after repeated (but patient and reasonably polite) inquiries from their sysop [https://enigmatic.observer/users/inex Inex Code], I told them<ref name=tc1 /> basically this (but referring to them in 2nd person):

Woozle: /* Footnotes */ I actually posted it semi-public, which is sort of what I intended

2020-07-23T00:35:23Z

Footnotes: I actually posted it semi-public, which is sort of what I intended

← Older revision		Revision as of 00:35, 23 July 2020
Line 19:		Line 19:
	==Footnotes==		==Footnotes==
	<references>		<references>
	<ref name=tc1>'''2020-07-22''' [https://toot.cat/@woozle/104558583395165826 DM reply] ~~(private)~~ to [https://enigmatic.observer/users/inex Inex Code]</ref>		<ref name=tc1>'''2020-07-22''' [https://toot.cat/@woozle/104558583395165826 reply] to [https://enigmatic.observer/users/inex Inex Code]</ref>
	</references>		</references>

Woozle: Woozle moved page Pub/toot.cat/block list/inex.rocks to Pub/inex.rocks without leaving a redirect: more sensible location

2020-07-22T18:39:32Z

Woozle moved page Pub/toot.cat/block list/inex.rocks to Pub/inex.rocks without leaving a redirect: more sensible location

← Older revision	Revision as of 18:39, 22 July 2020
(No difference)

Woozle: Created page with "==2020-07-22 Domain unblocked== ...after repeated (but patient and reasonably polite) inquiries from their sysop [https://enigmatic.observer/users/inex Inex Code], I told them..."

2020-07-22T17:08:26Z

Created page with "==2020-07-22 Domain unblocked== ...after repeated (but patient and reasonably polite) inquiries from their sysop [https://enigmatic.observer/users/inex Inex Code], I told them..."

New page

==2020-07-22 Domain unblocked==
...after repeated (but patient and reasonably polite) inquiries from their sysop [https://enigmatic.observer/users/inex Inex Code], I told them<ref name=tc1 /> basically this (but referring to them in 2nd person):

===The negative===
The [https://toot.cat/@girl/104462394989007467 one lead I was able to get] on this domain said:
* The main admin is known to follow people on domains that are often considered problematic, specifically [https://expired.mentality.rip/about expired.mentality.rip], [https://lor.sh/about/more" lor.sh], and the admin's own domain ([https://enigmatic.observer/about enigmatic.observer]).
* The second admin is [https://udongein.xyz/naiji naiji@udongein.xyz], which is another often-blocked domain and a quick glance at that profile in early July apparently showed direct communications with users on {{ls/domain|neckbeard.xyz}}, freespeechextremist, kiwifarms, pl.smuglo.li and other frequently blocked domains.

I don't know anything about neckbeard, but "free speech extremism" does tend to refer to a lot of very toxic forms of advocacy, and {{l/ip|kiwifarms}} is, from all reports, just plain evil.

===That said...===
Merely being willing to engage in dialogue with toxic people does not necessarily mean that one is toxic. I do not wish to promote a culture of fearing guilt-by-association.

Additionally, I have no idea of the nature of the contact; was naiji interacting ''approvingly'' with those folks, or in an appropriately skeptical manner? Is it happening in a way that causes nastiness to populate the timeline, if I federate with it?

Ultimately, I think that should be up to my userbase to decide -- and this time, if there are incidents, we will document them for future reference.

At this point, due primarily to a lack of documentation of what incident(s) triggered the current block: I've reversed it (with this page as a log of my reasoning), and we will just watch carefully for any future issues with it.
==Footnotes==
<references>
<ref name=tc1>'''2020-07-22''' [https://toot.cat/@woozle/104558583395165826 DM reply] (private) to [https://enigmatic.observer/users/inex Inex Code]</ref>
</references>