Lemmy Shitpost
Welcome to Lemmy Shitpost. Here you can shitpost to your hearts content.
Anything and everything goes. Memes, Jokes, Vents and Banter. Though we still have to comply with lemmy.world instance rules. So behave!
Rules:
1. Be Respectful
Refrain from using harmful language pertaining to a protected characteristic: e.g. race, gender, sexuality, disability or religion.
Refrain from being argumentative when responding or commenting to posts/replies. Personal attacks are not welcome here.
...
2. No Illegal Content
Content that violates the law. Any post/comment found to be in breach of common law will be removed and given to the authorities if required.
That means:
-No promoting violence/threats against any individuals
-No CSA content or Revenge Porn
-No sharing private/personal information (Doxxing)
...
3. No Spam
Posting the same post, no matter the intent is against the rules.
-If you have posted content, please refrain from re-posting said content within this community.
-Do not spam posts with intent to harass, annoy, bully, advertise, scam or harm this community.
-No posting Scams/Advertisements/Phishing Links/IP Grabbers
-No Bots, Bots will be banned from the community.
...
4. No Porn/Explicit
Content
-Do not post explicit content. Lemmy.World is not the instance for NSFW content.
-Do not post Gore or Shock Content.
...
5. No Enciting Harassment,
Brigading, Doxxing or Witch Hunts
-Do not Brigade other Communities
-No calls to action against other communities/users within Lemmy or outside of Lemmy.
-No Witch Hunts against users/communities.
-No content that harasses members within or outside of the community.
...
6. NSFW should be behind NSFW tags.
-Content that is NSFW should be behind NSFW tags.
-Content that might be distressing should be kept behind NSFW tags.
...
If you see content that is a breach of the rules, please flag and report the comment and a moderator will take action where they can.
Also check out:
Partnered Communities:
1.Memes
10.LinuxMemes (Linux themed memes)
Reach out to
All communities included on the sidebar are to be made in compliance with the instance rules. Striker
view the rest of the comments
The cause of this for SMS is not the phone, but the network, and the underlying technology. SMS is push-based, compared to Internet messaging which is pull-based, and uses a backoff-based redelivery mechanism. Once your message is sent and has been received by your carrier, deliver is attempted, but if the recipient handset is unavailable the carrier will try periodically to redeliver, and if it still fails the wait period between delivery attempts will increase the longer the recipient is unavailable. May be every five minutes for the first hour, but then once an hour for the next 24, for example.
Each message is its own distinct entity which is treated separately for delivery, just like letters in the post. That's why it was possible to get this sort of odd-seeming scenario where you have a newer message that made it through, while an older one is still stuck in retry somewhere.
Makes sense. I think it's similar to how email works, right?
Email has bits of both in the chain.
Using the olden-days of desktop email apps as an example then:
The issue most likely seemed to me to be just that plus the fact that the google service would never retry on SMS when switched back to SMS. So your message wouldn't be sent until the recipient had a WiFi connection. Ridiculous implementation.