4 ms·

First I heard about a readme for your profile page. So the facebook-ification of GitHub progresses? At what point is LinkedIn going to be merged into GitHub? (

First I heard about a readme for your profile page. So the facebook-ification of GitHub progresses? At what point is LinkedIn going to be merged into GitHub? (Only partially /s)

deleted 6y ago
[deleted]
jomar 6y ago
It's just gone live in the last day or so. The designer talked about it here a few weeks ago: https://twitter.com/pifafu/status/1265773172520914944 https://twitter.com/pifafu/status/1265773172520914944 Personally I don't see much reason for this to be implemented via a git repository (rather than a text field in a database, like the existing Bio text), other than "we're GitHub, everything's a git repository, so why not". At the moment, it's a single-file repository. Perhaps they have some ideas for other things that could be served from there too. Weirdly at the moment it's required to be a public repository. This seems counterproductive: if it's my personal information blurb I don't much want other people looking at its history and I certainly don't want them forking it. (Are there any non-malicious reasons for doing that?)
- chrisshroba 6y ago
  To be honest, I'm not too concerned. Making it a git repo makes the history more readily available, but a bad actor could still get it from internet archive or other archive sites. And if the concern about forking is that someone could impersonate you, they could do so with a few extra steps by just looking at the rendered HTML of the README. I know there's something to be said for making malicious behavior more difficult to achieve, but in this case the amount of extra work someone would have to do is minuscule if this weren't implemented as public repos.
- victords 6y ago
  Are there malicious reasons for doing that?
- f311a 6y ago
  You can rewrite GitHub history and keep one commit. I was doing it for GitHub pages, because I didn't want to expose my blog edits.
- esnard 6y ago
  > Weirdly at the moment it's required to be a public repository. I guess they didn't want any past private repository to have its README public just because they added a profile feature.
- filleduchaos 6y ago
  > This seems counterproductive: if it's my personal information blurb I don't much want other people looking at its history and I certainly don't want them forking it. Taken to its logical conclusion, this would mean you're opposed to the existence of web archives (which you probably aren't).
dom96 6y ago
> So the facebook-ification of GitHub progresses? GitHub's premise has always been "social coding". They should indeed become more social, that may or may not remind you of Facebook but I personally have wanted more social features out of GitHub for a while.
- Geezus_42 6y ago
  It depends what "social features" you are referring to. I go to github for code not pictures of people's cats, meme, etc. If github became more like a Facebook feed where people just shit post their lives all day it would become useless from my imo.
  - jldugger 6y ago
    I mean, they built and added camo like a decade ago to allow your reaction gifs in code review to work over HTTPS. The shitposting is now a fact of life
- dudul 6y ago
  Which ones for example? On the one hand, I sometimes feel the same, but OTOH I don't want this thing to get so bloated with "social" features instead of features to get things done :)
lxe 6y ago
More like Myspacification. Can't wait for full HTML and CSS editing.

First I heard about a readme for your profile page. So the facebook-ification of GitHub progresses? At what point is LinkedIn going to be merged into GitHub? (Only partially /s)

deleted 6y ago

[deleted]

jomar 6y ago

It's just gone live in the last day or so. The designer talked about it here a few weeks ago: https://twitter.com/pifafu/status/1265773172520914944 https://twitter.com/pifafu/status/1265773172520914944 Personally I don't see much reason for this to be implemented via a git repository (rather than a text field in a database, like the existing Bio text), other than "we're GitHub, everything's a git repository, so why not". At the moment, it's a single-file repository. Perhaps they have some ideas for other things that could be served from there too. Weirdly at the moment it's required to be a public repository. This seems counterproductive: if it's my personal information blurb I don't much want other people looking at its history and I certainly don't want them forking it. (Are there any non-malicious reasons for doing that?)

chrisshroba 6y ago
To be honest, I'm not too concerned. Making it a git repo makes the history more readily available, but a bad actor could still get it from internet archive or other archive sites. And if the concern about forking is that someone could impersonate you, they could do so with a few extra steps by just looking at the rendered HTML of the README. I know there's something to be said for making malicious behavior more difficult to achieve, but in this case the amount of extra work someone would have to do is minuscule if this weren't implemented as public repos.
victords 6y ago
Are there malicious reasons for doing that?
f311a 6y ago
You can rewrite GitHub history and keep one commit. I was doing it for GitHub pages, because I didn't want to expose my blog edits.
esnard 6y ago
> Weirdly at the moment it's required to be a public repository. I guess they didn't want any past private repository to have its README public just because they added a profile feature.
filleduchaos 6y ago
> This seems counterproductive: if it's my personal information blurb I don't much want other people looking at its history and I certainly don't want them forking it. Taken to its logical conclusion, this would mean you're opposed to the existence of web archives (which you probably aren't).

dom96 6y ago

> So the facebook-ification of GitHub progresses? GitHub's premise has always been "social coding". They should indeed become more social, that may or may not remind you of Facebook but I personally have wanted more social features out of GitHub for a while.

Geezus_42 6y ago
It depends what "social features" you are referring to. I go to github for code not pictures of people's cats, meme, etc. If github became more like a Facebook feed where people just shit post their lives all day it would become useless from my imo.
- jldugger 6y ago
  I mean, they built and added camo like a decade ago to allow your reaction gifs in code review to work over HTTPS. The shitposting is now a fact of life
dudul 6y ago
Which ones for example? On the one hand, I sometimes feel the same, but OTOH I don't want this thing to get so bloated with "social" features instead of features to get things done :)

lxe 6y ago

More like Myspacification. Can't wait for full HTML and CSS editing.