@veer66 What is too tight? If your software/site flies on 2G; it'll be an amazing experience for those on 2G and highers. The lesson here is that to have a stellar experience, designing and testing in the most common (and usually overlooked) parameters can lead to great results. @mishari

@jalcine @mishari Too tight means testing on too slow network e.g. 2400 bps modem. This leads back to my first question. I will rephrase it. Where do people still use 2G?

@veer66 @mishari No lie, I haven't responded for a few reasons:

1) There's no strong case against testing in low speed environments: it literally helps you improve speed times when testing code

2) This "request for evidence" is something you can handle as easily and in the same amount of time you've requested it over here: bfy.tw/LeDr

@veer66 the point is not 2G the point is constraints force you to implement better design. @jalcine

@mishari @jalcine I agree with limiting connection speed to test the web. However, with 2G speed, I have to exclude podcast, video, etc. And I have no information that any potential target still use 2G.

@veer66 @mishari @jalcine idk if it's 2G but if you've ever used WiFi on a train you've known the suffering of a slow and intermittent connection.


@grainloom @veer66 @mishari @jalcine our, just, a (regional) train through Germany.

there's bursts of 4G when you're stood in a station, but otherwise you'll be happy to have 3G, and you'll be unhappy to have 2G cuz most things just don't work on it

and i don't know how much of this is due to TLS connection establishment

@grainloom @veer66 @mishari @jalcine and then, of course, there's wide stretches with no connection at all

for instance, sitting on the side of sofa further away from the window at home, i often lose connection while making a phone call.

@hirojin @grainloom I can walk into my university and immediately lose connection to an otherwise very big network (own carrier + some more networks they use). Brutalist Concrete Buildings, hooray.
@hirojin @jalcine @mishari @veer66 @grainloom TLS 1.3 might help a little, but still... 2G latency is not designed for our ridiculous protocols
Sign in to participate in the conversation


BE WARNED this instance will absolutely be unstable at times. It will 10000% be used for experimenting with settings and tweaks to Mastodon. So the place may experience outages, not federate reliably with the rest of the world, have posts go missing, or other technical faults. As such it's meant to be a chill, maybe kinda playful place. FOR BREAKING THE SOFTWARE. Time to see what we can do with this thing! Time to ˥∀IƆOS HƆ⊥I˥⅁

the code is here

This instance also has domain level blocks on numerous others, using the block list found here .

followbots from other instances will be blocked. please report them

Some rules

  • Do not engage in harassment of any kind.
  • Racist, sexist and other oppressive slurs will get you suspended, even in non-public conversations.
  • You can post porn and nudity, but you must use the nsfw flag and do not post on the public timeline or you will be silenced (ask around how to make unlisted posts)
  • try to be kind
  • no non-sentient bots until further notice
  • no shit that's illegal in Canada
  • animated gifs should always be marked sensitive/NSFW and identified as animated gifs (for now let's say just putting 'gif' in the text of the toot is sufficient), because they can cause serious problems for people

some guidelines

  • stuff here is impermanent but i still want this to be as safe a space as we can reasonably make it. let's keep common triggers and angry/ranty/grumpy toots behind CWs
  • free speech maximalists can kindly fuck off. there are instances where that is a priority. this is not one of them.
  • all languages are welcome!

the privacy stuff in the 'terms' isn't what it should be, but no time to change it yet. this instance's data will not be sold or traded or whatever.