toad.social

Giacomo Tesio<a href="https://social.treehouse.systems/users/ariadne" class="u-url mention" rel="nofollow noopener" target="_blank">@ariadne@treehouse.systems</a> what about <a href="https://snac.tesio.it?t=fossilscm" class="mention hashtag" rel="nofollow noopener" target="_blank">#FossilSCM</a>? <a href="https://fossil-scm.org/home/doc/trunk/www/index.wiki" rel="nofollow noopener" target="_blank">https://fossil-scm.org/home/doc/trunk/www/index.wiki</a> It's the easiest forge to self-host but if you don't have an online server or a small vps, a cheap web hosting with <a href="https://snac.tesio.it?t=cgi" class="mention hashtag" rel="nofollow noopener" target="_blank">#cgi</a> support (the ones that often comes for free when you but a domain name) is enough!

Y⃒̸̷̝̜̙ͥͥͥngmar<a href="https://writing.exchange/@davepolaschek" class="u-url mention" rel="nofollow noopener" target="_blank">@davepolaschek</a> Fossil. For the weirdos like me who actually evaluate their options before choosing one and don't give a toss what the mainstream uses (and perhaps scoff at it).<a href="https://fossil-scm.org/" rel="nofollow noopener" translate="no" target="_blank">https://fossil-scm.org/</a>The name appears suited for "unfrozen caveman" people too, although that's probably not intended.In case you're wondering who uses this, the SQLite guy (D. Richard Hipp) wrote it for himself. So you're in good hands. Been keeping my personal stuff in it for years.<a href="https://social.tchncs.de/tags/Fossil" class="mention hashtag" rel="nofollow noopener" target="_blank">#Fossil</a> <a href="https://social.tchncs.de/tags/FossilSCM" class="mention hashtag" rel="nofollow noopener" target="_blank">#FossilSCM</a> <a href="https://social.tchncs.de/tags/VCS" class="mention hashtag" rel="nofollow noopener" target="_blank">#VCS</a>

nathanI'm used to and rely way too heavily on `git add -p` and rebase and/in Fork as a GUI, but I consider <a href="https://chaos.social/tags/fossilscm" class="mention hashtag" rel="nofollow noopener" target="_blank">#fossilscm</a> a beautiful tool and am intrigued to give it a try. But I want to know and learn from you why you decided to use it and how you use it in your daily business. I even might write a little piece or record a podcast.(please don't mastosplain. I know how to read the docs and how to use Google.)

nathanIs someone other than <a href="https://chaos.social/tags/fossilscm" class="mention hashtag" rel="nofollow noopener" target="_blank">#fossilscm</a> and <a href="https://chaos.social/tags/sqlite" class="mention hashtag" rel="nofollow noopener" target="_blank">#sqlite</a> using <a href="https://chaos.social/tags/fossilscm" class="mention hashtag" rel="nofollow noopener" target="_blank">#fossilscm</a> to develop (commercial) software as a team or company? I'd love to talk to you!

Wizards AnonymousAnyone migrate from <a href="https://mastodon.social/tags/GitHub" class="mention hashtag" rel="nofollow noopener" target="_blank">#GitHub</a> or <a href="https://mastodon.social/tags/GitLab" class="mention hashtag" rel="nofollow noopener" target="_blank">#GitLab</a> to <a href="https://mastodon.social/tags/Codeberg" class="mention hashtag" rel="nofollow noopener" target="_blank">#Codeberg</a> or other options? Curious what your experience might have been like. The 3 features I have a lot of interest in are Public <a href="https://mastodon.social/tags/Repositories" class="mention hashtag" rel="nofollow noopener" target="_blank">#Repositories</a>, Private Repositories, and <a href="https://mastodon.social/tags/GitHubPages" class="mention hashtag" rel="nofollow noopener" target="_blank">#GitHubPages</a>. GitHub offering all 3 of these for "<a href="https://mastodon.social/tags/free" class="mention hashtag" rel="nofollow noopener" target="_blank">#free</a>" is a huge advantage for "users". <a href="https://mastodon.social/tags/Forge" class="mention hashtag" rel="nofollow noopener" target="_blank">#Forge</a> <a href="https://mastodon.social/tags/Foregejo" class="mention hashtag" rel="nofollow noopener" target="_blank">#Foregejo</a> <a href="https://mastodon.social/tags/FossilSCM" class="mention hashtag" rel="nofollow noopener" target="_blank">#FossilSCM</a>

Shamar<a href="https://fosstodon.org/@pemensik" class="u-url mention" rel="nofollow noopener" target="_blank">@pemensik</a>That what I did understood by reading the doc.<a href="https://qoto.org/tags/PowerDNS" class="mention hashtag" rel="nofollow noopener" target="_blank">#PowerDNS</a>'s <a href="https://qoto.org/tags/DNSDist" class="mention hashtag" rel="nofollow noopener" target="_blank">#DNSDist</a> seems a superb project, just maybe a bit overhelm for what it should do in this specific case. Yet seems likely the only option, actually.It's a bit of a shame no other <a href="https://qoto.org/tags/DoH" class="mention hashtag" rel="nofollow noopener" target="_blank">#DoH</a> <a href="https://qoto.org/tags/CGI" class="mention hashtag" rel="nofollow noopener" target="_blank">#CGI</a> have been written in compiled languages so far... which is likely why few resolver support such forwarding.When I first read about DNS-over-HTTP, I saw it as a further centralization attempt by <a href="https://qoto.org/tags/Google" class="mention hashtag" rel="nofollow noopener" target="_blank">#Google</a> & friends (which sadly includes <a href="https://mozilla.social/@mozilla" class="u-url mention" rel="nofollow noopener" target="_blank">@mozilla</a> these days), since to get a working DoH service you need good sysadmin skills and a stable public IP: not something a kid with a cheap shared hosting can set up.And ə PHP implementation would be too slow.<a href="https://qoto.org/tags/FossilSCM" class="mention hashtag" rel="nofollow noopener" target="_blank">#FossilSCM</a> made me realize that a simple CGI in C could have good performances and be widely distributed, so I wrote one (still early alpha).Now I can use it in most (non enterprise managed¹) browser, but I'd like to try it system wide.Anyway... thanks for your help guys!<a href="https://social.sdf.org/@draeath" class="u-url mention" rel="nofollow noopener" target="_blank">@draeath</a>

Todd A. Jacobs | Pragmatic CybersecurityI deeply respect <a href="https://infosec.exchange/@briankrebs" class="u-url mention" rel="nofollow noopener" target="_blank">@briankrebs</a>, but in this case I think the data he's presenting is fundamentally invalid. A little-known fact about <a href="https://infosec.exchange/tags/Git" class="mention hashtag" rel="nofollow noopener" target="_blank">#Git</a> history is that <a href="https://infosec.exchange/tags/timestamps" class="mention hashtag" rel="nofollow noopener" target="_blank">#timestamps</a> are both definable and mutable. While you might be able to make statements about when a Git commit was pushed to a server using the server-side SSH or HTTP logs, the fact that you can set GIT_AUTHOR_DATE and GIT_COMMITTER_DATE as environment variables means you can't rely on commit timestamps alone for this type of analysis.This is a feature of Git since the ability to squash or rewrite its mutable history is a key differentiator compared to <a href="https://infosec.exchange/tags/FossilSCM" class="mention hashtag" rel="nofollow noopener" target="_blank">#FossilSCM</a> or other <a href="https://infosec.exchange/tags/SCMs" class="mention hashtag" rel="nofollow noopener" target="_blank">#SCMs</a> that treat history as immutable(ish). For example, allowing one to do things like report a commit as the time a patch or source document was originally written rather than just noting when it was committed or merged can be very useful in accurately representing the real-world evolution of data created outside the repository.This is not a flaw in Git. Anyone savvy enough to craft the <a href="https://infosec.exchange/tags/xz" class="mention hashtag" rel="nofollow noopener" target="_blank">#xz</a> attack could just as easily have adjusted their system clocks instead, leading to fraudulent timestamps in the commit history anyway.Forensically, you'd need to look at the timestamps from NTP-backed server or router logs, not just the Git history. All Git clients are technically "offline" until they push one or more commits to a remote, so there's really no way to validate client-side SCM timestamps. This is also true of email headers, filesystem attributes, and any other data that relies on real system clocks or user-defined timestamps, so you'd need more points of correlation than are provided here.<a href="https://www.linkedin.com/posts/bkrebs_one-of-the-more-interesting-graphics-ive-activity-7181358250112471040-fzeG" rel="nofollow noopener" translate="no" target="_blank">https://www.linkedin.com/posts/bkrebs_one-of-the-more-interesting-graphics-ive-activity-7181358250112471040-fzeG</a>

Ryan Makes, DreamscaperFossil SCM users here? <a href="https://fosstodon.org/tags/fossil" class="mention hashtag" rel="nofollow noopener" target="_blank">#fossil</a> <a href="https://fosstodon.org/tags/fossilscm" class="mention hashtag" rel="nofollow noopener" target="_blank">#fossilscm</a> I'm considering using it for my notebase. Any experiences or links to share?

Kristoffer Lawson<a href="https://indieweb.social/@maphew" class="u-url mention" rel="nofollow noopener" target="_blank">@maphew</a> <a href="https://2c.taoetc.org/@beto" class="u-url mention" rel="nofollow noopener" target="_blank">@beto</a> <a href="https://hachyderm.io/@sara" class="u-url mention" rel="nofollow noopener" target="_blank">@sara</a> <a href="https://attractive.space/tags/FossilSCM" class="mention hashtag" rel="nofollow noopener" target="_blank">#FossilSCM</a> is absolutely wonderful. For many people the use would be much simpler with Fossil. The default is to sync, and everything contained in an easily compilable binary, with the repository being one file. Plus, as you mention, distributed tickets, wiki etc. For my personal projects I don’t use git anymore.

matt<a href="https://2c.taoetc.org/@beto" class="u-url mention" rel="nofollow noopener" target="_blank">@beto</a> <a href="https://hachyderm.io/@sara" class="u-url mention" rel="nofollow noopener" target="_blank">@sara</a> <a href="https://indieweb.social/tags/FossilSCM" class="mention hashtag" rel="nofollow noopener" target="_blank">#FossilSCM</a> is the better designed product. Distributed version control & tickets & comments & web UI & syncing across servers in a single executable & database file & cross platform. It's brilliant, full stop.But, it's not interested in appealing to masses. It either works for you or doesn't. Not a fit for me. Still, I wish many people to see & experience it so they know what is possible, and build another one. It shouldn't be the only project in its class! <a href="https://fossil-scm.org/" rel="nofollow noopener" target="_blank">https://fossil-scm.org/</a>

LisPi<a href="https://infosec.exchange/@karl" class="u-url mention" rel="nofollow noopener" target="_blank">@karl</a> <a href="https://social.treehouse.systems/@marcan" class="u-url mention" rel="nofollow noopener" target="_blank">@marcan</a> A large part of that is entirely <a href="https://mastodon.top/tags/git" class="mention hashtag" rel="nofollow noopener" target="_blank">#git</a>'s fault, because <a href="https://mastodon.top/tags/FossilSCM" class="mention hashtag" rel="nofollow noopener" target="_blank">#FossilSCM</a> has no such problem (it has different ones instead mostly from its focus on cathedral development...).Git's design insistence on carrying none of the other project metadata and tooling required for its use is a problem.

Recent searches

Search options

Administered by:

Server stats:

#fossilscm