cemre 🫒's latest activity
- 2y ·
-
Public·
-
mastodon.social
{"p":"","h":{"iv":"ROXSYW+cfvEbFHu5","at":"ocxplSQjdRC3tXEtB/9/wg=="}}
@Gargron how do you keep up with the scaling? Are you on an auto-scalable instance or do you manually adjust it? Great news btw! Let's see how many will stick. There sure will be a snowballing effect :blobcatcoffee:
…See more
@Gargron how do you keep up with the scaling? Are you on an auto-scalable instance or do you manually adjust it? Great news btw! Let's see how many will stick. There sure will be a snowballing effect :blobcatcoffee:
See less
@Gargron how do you keep up with the scaling? Are you on an auto-scalable instance or do you manually adjust it? Great news btw! Let's see how many will stick. There sure will be a snowballing effect :blobcatcoffee:
@Gargron how do you keep up with the scaling? Are you on an auto-scalable instance or do you manually adjust it? Great news btw! Let's see how many will stick. There sure will be a snowballing effect :blobcatcoffee:
- 2y ·
-
Public·
-
mastodon.social
{"p":"","h":{"iv":"ROXSYW+cfvEbFHu5","at":"ocxplSQjdRC3tXEtB/9/wg=="}}
@feditips @brayd definitely agreed. As mentioned by others the main problem is not the implementation as that is pretty straightforward to do. The real problem would be the bandwidth used by this feature. I think the best option would be requesting the toots in batches as the user goes down / explicitly requests to load more. Empty profiles are the worst. Everybody needs a preview to decide on a follow :bongoCat:
…See more
@feditips @brayd definitely agreed. As mentioned by others the main problem is not the implementation as that is pretty straightforward to do. The real problem would be the bandwidth used by this feature. I think the best option would be requesting the toots in batches as the user goes down / explicitly requests to load more. Empty profiles are the worst. Everybody needs a preview to decide on a follow :bongoCat:
See less
@feditips @brayd definitely agreed. As mentioned by others the main problem is not the implementation as that is pretty straightforward to do. The real problem would be the bandwidth used by this feature. I think the best option would be requesting the toots in batches as the user goes down / explicitly requests to load more. Empty profiles are the worst. Everybody needs a preview to decide on a follow :bongoCat:
@feditips @brayd definitely agreed. As mentioned by others the main problem is not the implementation as that is pretty straightforward to do. The real problem would be the bandwidth used by this feature. I think the best option would be requesting the toots in batches as the user goes down / explicitly requests to load more. Empty profiles are the worst. Everybody needs a preview to decide on a follow :bongoCat: