comment from hacker news
#hastext; #hastitle; #client; #cookie; #https; #received

They function differently, but in terms of what gets communities to actually form and stick around, I think they're very similar:

- Making a new space for your community is trivial for anyone; it can be done in seconds with a few clicks and all you have to do is choose a name.

- Many people already have an account, so you don't need to convince everyone to sign up for a new platform. (Which scales with the platform's size, like all network effects.)

- Communities have their own space they can adjust to their liking, rather than being a vague cluster of nodes with a similar interest like in other social networks.

- Owners of those spaces have a lot of leeway to run things as they see fit.

Personally, I don't like the growing trend of every community being a Discord server that is going to collect dust in the corner of my chat window unless I commit to keeping up with it every day, but I understand why it's happening. Discord is an adequate social hub for any project or hobby group with a very low barrier to entry, which is more important than the actual functionality being the best IMO.

[https]
They function differently, but in terms of what gets communities to actually for... | Hacker News

--
[Cookie]
[Received]
[Client]

; ilyag+[;;']; f5c40b4d; thanks ; +cart
Comment




Clear this field to post a new thread.
ItemAttributes
attribute value
Checksum: Yes
SHA1 (chain.log): f5c40b4db0eebba6460ca3c740a65557a5610852
Next: title: comment f
Previous: For clipping oth
Sequence: 2321
Notarized: 1711088327.01223
Client: CD06CFB6265139FB
Cookie: ilyag+[;;'] 4B38BE30A388AAFE
File: /txt/f5/c4/f5c40b4db0eebba6460ca3c740a65557a5610852.txt
Link: https://news.ycombinator.com/item?id=39787849
Type: txt
Received: 1711088106
SHA1 (Perl, Digest::SHA): f5c40b4db0eebba6460ca3c740a65557a5610852
Title: They function differently, but in terms of what gets communitie
Title: comment from hacker news
Domain: news.ycombinator.com
Thread
item_title add_timestamp
comment from hacker news (selected)
    title: comment from hacker news
Publish

localhost:2784
yavista.com
shitmyself.com
hypercode.com
ilyagulko.com
thankyou.scripts.mit.edu
qdb.us


Classify
Existing Labels:
#hastext; #hastitle; #client; #cookie; #https; #received

Add:
meta; flag; noise; textart; funny; good; approve; hide

Score:
0
title: comment from hack
#hastext; #hastitle; #signed; #parent; #title

>>comment from hac

title: comment from hacker news

; ilyag+[;;']; daaade63; thanks ; +cart
Chain
Sequence: 2321
Next: title: comment f
Previous: For clipping oth
Hashes
SHA1 (chain.log): f5c40b4db0eebba6460ca3c740a65557a5610852
SHA1 (Perl, Digest::SHA): f5c40b4db0eebba6460ca3c740a65557a5610852
index_log
indexing begins
file was organized (moved location, changed filename)
file hash = f5c40b4db0eebba6460ca3c740a65557a5610852
---
found token: cookie, : , 4B38BE30A388AAFE
found token: client, : , CD06CFB6265139FB
found token: received, : , 1711088106
found token: footer_separator, ,
found https address
finished finding tokens
tokens found: 5
token: cookie; spacer: : ; param = 4B38BE30A388AAFE
found cookie: 4B38BE30A388AAFE
token: client; spacer: : ; param = CD06CFB6265139FB
found client: 4B38BE30A388AAFE (overruled by signature)
token: received; spacer: : ; param = 1711088106
token: footer_separator; spacer: ; param =
token: https; spacer: ; param = https://news.ycombinator.com/item?id=39787849
---
item timestamp: 1711088327.01223
applying: cookie
valid: cookie
token found: cookie
applying: client
valid: client
token found: client
applying: received
valid: received
token found: received
applying: https
valid: https
token found: https
Cart
Paste
PrintedInfo

Q: When was this page printed?
Printed: April 29 2024 04:51:15.

Q: How old was the page when downloaded?
Age: Fresh!
pollyanna: fc2d252

Q: How can I get a fresher copy?
A: Ask the server to


Welcome ; Threads(16) ; Random ; Menu ; Help
let us not grow weary of doing good Expand; Minimal; Reprint; Cascade; Arrange; Float; Reset
PageMap