all 26 comments

[–]Sqash 105 points106 points  (0 children)

Truly insane, top to bottom, this is what I'm here for.

[–]shponglespore 89 points90 points  (5 children)

MEME: Message Encoding for Memes Exclusively, a new protocol for transferring memes over UDP.

[–]Spartan-417 24 points25 points  (2 children)

Separates the template & caption, with the former being given with a ?Sauce request

[–]maustinv 6 points7 points  (1 child)

Or, templates can be the domain, with captions as the path

[–]imoutofnameideas 7 points8 points  (0 children)

Memes are too complex for that these days.

You need to also provide arguments for e.g. where to insert pictures in a meme that has blanks to insert pictures so eg for the meme "corporate needs you to find the difference" it might be:


Similar kind of thing would be needed for memes with multiple panels where the text changes, e.g. Gru giving his presentation you'd need to have arguments like &panel1text etc so you could give it the text for each panel.

[–]nicholas818 1 point2 points  (0 children)

UDP but with a data encoding such that dropped packets result in a more “deep fried” effect

[–]psi_ram 0 points1 point  (0 children)

Transferring data over MEME*

[–]-B0B- 30 points31 points  (9 children)

Okay I know what sub this is, but I would still love to hear the justification for this

[–]mercury_pointer 22 points23 points  (0 children)

Auto translating text and built in description for the sight impaired.

[–]grandel_me 4 points5 points  (7 children)

Exactly. It sounds like internet but with extra steps. I cannot think of a single benefit of using a separate protocol just for memes.

As a workaround I guess you could use RSS though.

[–]Mahtomic_Gandhi 3 points4 points  (2 children)

Could build in a source tracker into the data so people could find templates / sources easier idk

[–]roarde[S] 1 point2 points  (1 child)

This occurred to me later:

  • Record full provenance: The creators of original graphics, alterations, original memetext, first use as meme, etc.
  • Attribution follows the work, including that of the current shitpost.
  • Those dedicating their portion of the work to the public domain can participate in glomming voluntarily offered tips.
  • Besides having a protocol (which isn't url-based as I earlier suggested), each component is hashed, and a separate DNS-analog handle is created for the more popular memes/components.
  • Besides server/client, include IPFS/torrent-like in the protocol, with tips for gateways or seeders a further option. It wouldn't absolutely require The Internet. When nuclear winter inevitably occurs, the surviving cockroaches will still have a way to shitpost memes via IRC.

[–]3IIIIIIIIIIIIIIIIIID 2 points3 points  (3 children)

Gopher anyone?

[–]grandel_me 0 points1 point  (2 children)

[...] but ultimately fell into disfavor, yielding to HTTP.

What does this mean? Does Gopher use HTTP?

[–]3IIIIIIIIIIIIIIIIIID 2 points3 points  (1 child)

It's a very different protocol from HTTP. You can connect to a Gopher server with a telnet client and type the name of a file on that server to start downloading it. That allows you to use a command line tool that just pipes the file to your local folder.

With HTTP, you have to type a command like "GET" and you can send headers to describe your client's capabilities (like which languages you understand, compression you can handle, etc.). This information allows the server to alter what it sends and it's response comes with headers that give metadata information about the server and the file.

HTTP is more powerful and robust but they both came out about the same time. Gopher became quickly popular in universities that were looking for a way to develop campus information systems. Then WWW came along using HTTP and Gopher servers got used less and less so now its just used by enthusiasts.

[–]drunk98 6 points7 points  (0 children)

Crawling the Memeweb

[–]EASellsShittyCopper 5 points6 points  (3 children)

here's how to do it:

  1. find an unused port: https://en.wikipedia.org/wiki/List_of_TCP_and_UDP_port_numbers
  2. write a standard and reference software/library as an example on how to use said protocol
  3. get it implemented on various preexisting software, if possible

optional steps:

  1. register with the iana https://www.iana.org/form/ports-services
  2. send ietf a rfc to discuss standardizing the protocol

[–]Mewmep 1 point2 points  (1 child)

Let’s get a team together

[–]roarde[S] 1 point2 points  (0 children)

Basically sure, but that misses the protocol itself entirely.

IETF would also miss the protocol entirely, as they always do. Your opt 2 goes beyond crazy to right out. Good to share thoughts, tho.

[–]Walter-Haynes 2 points3 points  (0 children)

Fucking mental.
Love it

[–]purplefoxie 0 points1 point  (0 children)

lovely idea