I just replied this to another commenter, but that's a bad faith argument. The ToS also says to not engage in illegal activity. The admonishment of Nazi's and Racists is an admonishment of illegal evil.
That's a bad faith argument. The ToS also says to not engage in illegal activity. The admonishment of Nazi's and Pedophiles is an admonishment of illegal evil.
Your inclusion of Republicans is a bit of an extreme juxtaposition. Feel free to admonish the individual evil views of Republicans, but to discriminate against Republicans purely for their association is rightly against ToS.
T-Mobile users; be aware that T-Mobile has prepared for this and are trying to automatically transition grandfathered accounts with unlimited everything into their new plans.
I'm not 100% sure if the coverage of the new plans are technically worse, but they're definitely more expensive. And I wouldn't be surprised if the new plans had contact language to do a rug pull in the future.
You need to opt out of the transition.
In my opinion this is actually better than the CoC. The only thing "missing" is the definition of which qualities you shouldn't discriminate against. But that's now generalized into "groups of people".
I still can't discriminate against people based on any qualification. Hell, I technically can't discriminate against "pineapple on pizza eaters".
Is community browsing different than community searching? Because Jerboa has Searching.
I'm still rocking Jerboa on Android. It has been totally inoffensive, and I'll probably just stick with it until it offends me somehow.
As far as I understand;
A user is specific to one instance. In order to interact with the fediverse on that specific account, they need to log into that instance. If they're banned from that instance, they cannot log in and interact with the rest of the fediverse.
There's nothing stopping them from logging into an alt, whether on that same instance or on another instance.
Not really tricky at all. Especially if they limit the expiration date to be within the gap of the current closure logic (min 3-6 months).
Especially "especially" if they made the expiration date a new field, one that offline users could ignore, and navsoftware could use imperatively.
Not too difficult, I imagine. Especially if it's a default field in the UI under Access.
As for the companies making the nav software itself, I'm sure they'd love to implement temporary closures.
Hmm, OSM is perhaps the biggest base for alternative navigational software. Seems like a huge design flaw.
I'm obviously oblivious to the implementation difficulties, but it seems like it should be extremely simple to add something akin to a "temporarily closed until" field, so that uses can set and forget, and it'll resolve itself without a secondary edit.
That way, offline users can ignore this field, and nav software must use it.
Smith River Complex @ Gasquet Ranger District of the Six Rivers National Forest (SRF) - #SmithRiverComplex https://share.watchduty.org/i/10468
I used the phone app and started a chat. Here's what I asked, and their response:
https://i.imgur.com/dcbBes4.png