PostIdQuery

post

myProfile

query PostIdQuery(
  $id: String!
) {
  post(id: $id) {
    ...PostListItem_post
    author {
      ...Profile_profile
      ...LevelList_levels
      ...TopCommentators_topCommentators
      id
    }
    id
  }
  myProfile {
    ...MyProfile_myProfile
    id
  }
}

fragment CardListItem_card on Card {
  id
  enabled
  recurrent
  first4
  second4
  last4
  expiryMonth
  expiryYear
  isDefault
}

fragment CardList_cards on User {
  cards(first: 50) {
    edges {
      node {
        id
        last4
        expiryMonth
        expiryYear
        enabled
        isDefault
        ...CardListItem_card
        __typename
      }
      cursor
    }
    pageInfo {
      endCursor
      hasNextPage
    }
  }
}

fragment CommentListItem_comment on Comment {
  id
  createdAt
  text
  author {
    id
    avatar
    name
    urlSlug
    verified
  }
}

fragment LevelListItem_level on Level {
  id
  price
  title
  description
  cover
  price3
  price6
  price12
  archived
  incomingMessages
  buyCount
}

fragment LevelList_levels on User {
  levels(first: 10) {
    edges {
      node {
        id
        price
        archived
        title
        incomingMessages
        ...LevelListItem_level
        __typename
      }
      cursor
    }
    pageInfo {
      endCursor
      hasNextPage
    }
  }
}

fragment MediaListItem_postMedia on PostMedia {
  id
  fileName
  downloadable
  media {
    type
    isAuthor
    id
  }
  public
}

fragment MyProfile_myProfile on User {
  id
  name
  avatar
  about
  urlSlug
  deleted
  currency
  myBalance
  pendingBalance
  notViewedActivityCount
  notViewedPaymentCount
  notReadDialogs
  queueCount
  banned
  verified
  incomingMessagesType
  incomingPaidMessagesEnabled
  incomingPaidMessagesPrice
  ...CardList_cards
  defaultCard {
    id
  }
  locale
}

fragment PostListItem_post on Post {
  id
  publishedAt
  likeCount
  fireCount
  tipCount
  tipAmount
  liked
  fired
  tipSent
  hiddenPhotoCount
  hiddenVideoCount
  totalHiddenVideoLength
  buyToView
  price
  unlockTransaction {
    id
  }
  accessLevels
  publicText
  hiddenText
  buyers {
    edges {
      node {
        id
        avatar
        verified
      }
    }
  }
  comments(first: 4) {
    edges {
      node {
        id
        ...CommentListItem_comment
        __typename
      }
      cursor
    }
    pageInfo {
      endCursor
      hasNextPage
    }
  }
  postMedias(first: 60) {
    edges {
      node {
        id
        public
        ...MediaListItem_postMedia
        __typename
      }
      cursor
    }
    pageInfo {
      endCursor
      hasNextPage
    }
  }
}

fragment Profile_profile on User {
  id
  name
  avatar
  cover
  about
  lastSeen
  urlSlug
  deleted
  banned
  isMe
  isOnline
  incomingMessagesType
  incomingPaidMessagesEnabled
  incomingPaidMessagesPrice
  follow {
    id
    isFollowing
    level {
      id
      incomingMessages
      ...LevelListItem_level
    }
    isActive
  }
  verified
}

fragment TopCommentatorListItem_topCommentator on User {
  id
  avatar
  name
  urlSlug
}

fragment TopCommentators_topCommentators on User {
  topCommentators(first: 9) {
    edges {
      node {
        id
        ...TopCommentatorListItem_topCommentator
        __typename
      }
      cursor
    }
    pageInfo {
      endCursor
      hasNextPage
    }
  }
}


As with any endeavor, creating services at the level of @unlokz has many pitfalls.

It can be imagined as an iceberg. Sailing past an iceberg on the Titanic, you only see its top part. You dive into this project and then begin to understand why there are so few decent projects in this field.

It's not enough to be a programmer; it's important to understand finance and accounting to ensure the legality of receiving and making payments to authors. It might seem as simple as receiving money and then making a payment...

It's much more complicated than it seems. This is exactly the issue we are currently focusing on. It's very important to create a system that doesn't glitch, so that no author loses money, and all buyers receive their content.

When you first see this mountain of tasks, you want to quit and do something simpler. But we didn't quit and continued to delve into every detail. Step by step, a wonderful service is emerging that will become a convenient tool for any author