3 ms·

We need a light switch for static hosting

13 points by harryvederci 4y ago

rini17 4y ago
It's too easy to lose a domain, though. I had a decent one with email forwarding set up just in case something happens to my gmail, gave that email address to everyone...and lost it when i neglected to pay stuff for months cause of health problems. Now I have to beg some squatter to get it back.
- harryvederci 4y ago
  Oh man, that sucks. But with people randomly getting cancelled on these platforms though, I guess it's still less risky to get a domain?
  - rini17 4y ago
    Depends. We have GDPR here so at least I can request all my data from these platforms. If I screw something up on my server or domain, noone can help me.
  - marbu 4y ago
    Someone can still try to sue you over trademark or copyright infringement. That said, it's quite harder for the one using it against you compared to sheer AI system flagging your account, as it requires paying lawyers a going to a court.
tenebrisalietum 4y ago
> they could have an endpoint “/following.json”, containing an array of urls from people whose stuff they like to read. I'm game. This will work with Gemini too. Literally just an array of URLs? Don't you want at least a name for the array? Or does that make it took complex? { "following": [ "https://news.ycombinator.com", "https://aol.com" ] }
- dreamlessfate 4y ago
  This is just RSS. It was released 23 years ago. It was very popular and a big part of the web. The model that harryvederci is describing is exactly what the internet looked like prior to the rise of Facebook/Twitter, during the dawn of Web 2.0. Everyone had their own blog, on their own site. And you could curate your own feed of people you wanted to following using RSS feeds.
  - harryvederci 4y ago
    Thanks for providing some historical context. I'm familiar with RSS in the sense of providing a way to publish my own updates, I do that on willfennel.com as well. I'm also using it (with newsboat) to "subscribe" to RSS feeds myself, but those aren't shared anywhere by me currently. What I'm not aware of is what you're saying, that RSS is a way to let people know what content I'm consuming. > The model that harryvederci is describing is exactly what the internet looked like prior to the rise of Facebook/Twitter, during the dawn of Web 2.0. How was the "following" part of it implemented back then? Where would I find out what blogs you were following, if I looked at your own RSS feed?
    - ZeroGravitas 4y ago
      This was known as a "blogroll" and would just be a list of links of other sites you read/liked. https://en.m.wikipedia.org/wiki/Glossary_of_blogging#blogroll https://en.m.wikipedia.org/wiki/Glossary_of_blogging#blogrol... Before that there web web rings https://en.m.wikipedia.org/wiki/Webring https://en.m.wikipedia.org/wiki/Webring
      - harryvederci 4y ago
        After a quick search I haven't found a good example of a blogroll yet. Was this something that was added as a part of the html on a page? I think an advantage of an endpoint with just the information (regardless of if that's in JSON, newline-separated plain-text, etc) would be that you could query them witout everyone and their mother having to create custom parsers. Think "consuming an API" instead of "surfing the internet in a browser". I believe webrings also fall into the "surfing" part, which is not what I'm going for here.

13 points by harryvederci 4y ago

It's too easy to lose a domain, though. I had a decent one with email forwarding set up just in case something happens to my gmail, gave that email address to everyone...and lost it when i neglected to pay stuff for months cause of health problems. Now I have to beg some squatter to get it back.

harryvederci 4y ago
Oh man, that sucks. But with people randomly getting cancelled on these platforms though, I guess it's still less risky to get a domain?
- rini17 4y ago
  Depends. We have GDPR here so at least I can request all my data from these platforms. If I screw something up on my server or domain, noone can help me.
- marbu 4y ago
  Someone can still try to sue you over trademark or copyright infringement. That said, it's quite harder for the one using it against you compared to sheer AI system flagging your account, as it requires paying lawyers a going to a court.

tenebrisalietum 4y ago

> they could have an endpoint “/following.json”, containing an array of urls from people whose stuff they like to read. I'm game. This will work with Gemini too. Literally just an array of URLs? Don't you want at least a name for the array? Or does that make it took complex? { "following": [ "https://news.ycombinator.com", "https://aol.com" ] }

dreamlessfate 4y ago
This is just RSS. It was released 23 years ago. It was very popular and a big part of the web. The model that harryvederci is describing is exactly what the internet looked like prior to the rise of Facebook/Twitter, during the dawn of Web 2.0. Everyone had their own blog, on their own site. And you could curate your own feed of people you wanted to following using RSS feeds.
- harryvederci 4y ago
  Thanks for providing some historical context. I'm familiar with RSS in the sense of providing a way to publish my own updates, I do that on willfennel.com as well. I'm also using it (with newsboat) to "subscribe" to RSS feeds myself, but those aren't shared anywhere by me currently. What I'm not aware of is what you're saying, that RSS is a way to let people know what content I'm consuming. > The model that harryvederci is describing is exactly what the internet looked like prior to the rise of Facebook/Twitter, during the dawn of Web 2.0. How was the "following" part of it implemented back then? Where would I find out what blogs you were following, if I looked at your own RSS feed?
  - ZeroGravitas 4y ago
    This was known as a "blogroll" and would just be a list of links of other sites you read/liked. https://en.m.wikipedia.org/wiki/Glossary_of_blogging#blogroll https://en.m.wikipedia.org/wiki/Glossary_of_blogging#blogrol... Before that there web web rings https://en.m.wikipedia.org/wiki/Webring https://en.m.wikipedia.org/wiki/Webring
    - harryvederci 4y ago
      After a quick search I haven't found a good example of a blogroll yet. Was this something that was added as a part of the html on a page? I think an advantage of an endpoint with just the information (regardless of if that's in JSON, newline-separated plain-text, etc) would be that you could query them witout everyone and their mother having to create custom parsers. Think "consuming an API" instead of "surfing the internet in a browser". I believe webrings also fall into the "surfing" part, which is not what I'm going for here.