Cities: Skylines may be the game that I will finally be getting a gaming PC for. That is all.
Wir ziehen um; von Hoheluft-West (ca. 16k Menschen pro Quadratkilometer) nach Groß Flottbek (ca. 4k Menschen pro Quadratkilometer). Und irgendwie verspüre ich vor dieser Veränderung sehr viel mehr Nervosität als vor der Geburt unseres Sohnes. Vielleicht, weil immer klar war, dass wir das, was uns durch den Kleinen erwarten würde, immer bedingungslos hinnehmen müssten, während man sich so einen Umzug ja doch noch einmal überlegen oder, wenn es wirklich ganz schlimm ist, nach ein paar Monaten wieder umziehen könnte.
Die Wohnung ist ein bisschen größer als die alte (mit Kinder- und Arbeitszimmer, hurra), aber auch doppelt so teuer, ein bisschen weniger hübsch, und an einer gut befahrenen Straße (statt der Oase, in der wir bisher verweilten.) Übergeben wurde sie uns frisch saniert, aber mit komplett verschmutzten Fenstern und Urinspuren auf der Klobrille – in Hamburg muss man so etwas leider hinnehmen können.
Wahrscheinlich muss man sich einfach darauf verlassen, dass alles total super wird, wenn man sich erst einmal eingerichtet hat. Zur Not kann man ja wieder ausziehen.
So, IndiePants… Should I upgrade already or wait some more?
Please do yourself a favor and wait – unless it’s okay to wipe your data every now and then (and I’m serious about this – this isn’t maintainer-sprek for “it’s really unstable”. It’s actually quite stable! But you will need to reset your database eventually.)
The reason is the following: the database schema is still pretty much in flux, and instead of adding more and more Rails database migrations for every little change I make, I currently still work with the original migrations, which is a complete no-go in large-team and/or already-live projects, but neither is IndiePants already live, nor is a large team working on it. \o/
If you want to give it a try, the bundled heroku_bootstrap script is probably the fastest way to get it up and running (well, on Heroku), but please only do this if you want to see if the code is real (it is.) You will lose your data, and possibly your sanity.
We’re about to move into a new apartment, which is going to occupy a major part of my spare time over the next ~5 weeks, so progress will a bit slower than it has been recently. I’m hoping to be able to launch the new Pants some time May-ish.
Woohoo, IndiePants will finally store uploaded images in the database by default, thanks to the newly improved support for PostgreSQL in ActiveRecord. I did have to switch to the current HEAD of Rails 4.2.1 (which isn’t officially released yet), but other than that, implementing this was trivial. Check out my custom Dragonfly data store which uses a very simple ActiveRecord model to access a just as simple table. This table has a
bytea column, which ActiveRecord now supports as
I could probably have executed queries directly without going through ActiveRecord, but my gut tells me that this will eventually be useful for querying the binaries table. Also, I’m lazy.
Storing binary data in the database often evokes an unpleasant reaction in developers, the biggest worry being about performance. Well, turns out PostgreSQL is actually really good at handling binary data – and even if it wasn’t, it would probably still perform better than pulling files off S3 over and over again. In the end, no matter what you do, you will want to cache served images on the HTTP level (which is heaps of fun with the way Dragonfly works, as you don’t need to manually expire cache keys.) Either way, if you want to host Pants on your own server and don’t want to put binary data into your database, you can simply reconfigure Dragonfly to use S3, the local file system (not recommended), or whatever other data store you prefer.
So #Pants != IndiePants? I thought it was supposed to be a rename.
IndiePants is a big new version of Pants, big enough to be its own project on GitHub – when it launches, it will simply replace Pants, without a rename. “IndiePants” is simply a working title; I could have called it “Pants 2.0”, but using a version number simply didn’t feel right.
The name stems from the fact that this new version has significantly improved support for IndieWeb schemas and protocols; in fact, Microformats2 and Webmention are taking center stage now, instead of being an extra in a mostly proprietary environment. Removing the old non-IndieWeb code also allowed me to significantly improve performance and portability.
DIS GON B GUD!
I don’t think there are any beyond those that you can see listed on my Following page (of which many have already been abandoned, unfortunately.) So all in all I would wager that you’re not missing much at the moment.
This is partly my fault, as I haven’t really been driving people towards #Pants a lot lately, the primary reason for this being my ongoing work on IndiePants (which, by the way, is shaping up nicely.) Once I’ve deployed the new code and migrated everyone I can to it, I will get back to pestering people about Pants in every channel known to man (and cat), and it’s going to be beautiful!
Hopefully you’re not disappointed by the currently somewhat minute amount of activity. If you are, I’m hoping to be able to convince you to take another look by the time the new bits are online.
Well, it works and is quite easy to bend to my will. But so were Phoenix and Hydra. Yes, I actually went through almost all incarnations of sdegutis’ automation tools, migrating my config again and again… luarocks (which is used to install Mjolnir’s extensions) sucks a bit, though. Sometimes, the extensions cannot be loaded and have to be reinstalled. Also, there’s no easy way to upgrade all installed rocks. But Mjolnir itself is stable.
I love Lua (apparently I’m expected to give a quick talk about it at the next RUGHH meetup), but it’s simply not built for the kind of system-level, package-oriented scripting we know from other scripting languages. But holy crap, OpenResty (nginx + Lua) is a thing of beauty.
Have a look at my Mjolnir (Phoenix’s grandchild so to say) config:
Are you happy with Mjolnir? I love Lua, but haven’t had a chance to try this yet.
- terminals - Win-1
- editor - Win-2
- browser - Win-3
- irc/jabber - Win-4
- mail - Win-5
That’s actually a great idea and the first time that I’m tempted to go multi-desktop. (Actually, I may end up hacking this into my Phoenix configuration instead.)
I recently switched to Atom as my primary editor. Yes, it takes ages to start up. Yes, I still fundamentally disagree with the concept of feeding potentially system-destroying code to a non-sandboxed Node process. But I’m still enjoying it; the overall performance has vastly improved over the last couple of months, there are some nice plugins, and it just feels good to be using a piece of software that is under active, rapidly iterating development.
But I’m having the weirdest problem with something I was not expecting: Atom’s default application icon is invisible to me. No, I’m not colorblind or anything; I can perfectly see it, my brain just doesn’t seem to associate it with “code editing”. Worse, I usually end up switching to Textual (my IRC client) instead. Textual’s icon is nice and fat and purple and just screams “code”. I’ve been trying to break this habit, with no success.
There’s a surprising number of alternative Atom icons out there, but every update of the application will wipe it, and I just can’t be bothered to re-apply a custom icon over and over again. I’m hoping that at some point in the future, Atom plugins are able to install new icons, or maybe my brain magically fixes itself.
(Yes, I know you are using Vim. Good for you!)
Wenn jetzt jemand, der keinen Pants-Blog hat einen Pants-Blog besucht, tut er das wegen den Blogs und Webmentions und die internen Konversationen, die Pants-User unter sich führen, sind für ihn weniger interessant. Deswegen fände ich eine optische Unterscheidung der Replys innerhalb Pants zur besseren Übersicht nicht schlecht.
Ah. Uh. Da muss ich mal drüber nachdenken. Prinzipiell hänge ich sehr da dran, dass in Pants (genau wie im Web selbst) alles eine Antwort auf etwas anderes sein kann. Was ich aber auf jeden Fall einbauen möchte ist, dass man beim Schreiben einer Antwort aussuchen kann, ob diese auch im eigenen Blog (= auf der Startseite und im ATOM-Feed) publiziert wird. Diese Information kann ich dann auch beim Syndizieren an andere User verwenden, um sie entsprechend unterschiedlich zu rendern.
Every hour we spend on Twitter or Facebook instead of reading and writing elsewhere is just making this worse — and I’m as guilty as anyone.
Social networks have powerful benefits and are here to stay. But like any trend, we’ve swung too far in that direction for our own good, as both producers and consumers. I hope the pendulum starts to swing back soon, because it hasn’t yet. It’s going to get worse before it gets better, if it ever does.
If we want it to get better, we need to start pushing back against the trend, modernizing blogs, and building what we want to come next.
Wünschen würde ich mir eine Profilseite, wobei ich mir fast sicher bin, dass @hmans.de die bereits fertig hat
Hm, naja… :)
und vielleicht noch eine optische Trennung zwischen internen und externen Replys, auch, um Besuchern von Extern einen besseren Überblick zu verschaffen.
Huch, ich fürchte, das musst du mir näher erklären. Interne vs. externe Replies? Huh?
Also a reply to gbw499: Sorry if I came off as harsh, I didn’t mean to bad mouth pants in any way! Not only would it be highly hypocritical given that I’m running pants here, but I also really really really like it.
Don’t worry, I didn’t think you were being harsh, or even badmouthing Pants. It’s all good! :)
I think this is the underlying issue at play. Although I don’t think that really is an issue, I personally prefer a car that is convenient to use for me, but I don’t mind putting some effort into setting up and maintaining pants on my server. I think it’s really easy to drift into an elitist kind of thinking over this, or an us vs them mentality, but I think it really boils down to where people put their priorities.
This. And this is exactly my thinking; I’m okay with people using messengers that have been proven insecure over and over again. I’m okay with people using social networks that have been proven to use their users’ data for less than noble purposes. I’m okay with people reading tabloid newspapers that have been proven to bend the truth when it fits them. I realize I’m sounding sarcastic, but I’m seriously, honestly, utterly okay with all of this. I’m probably one of the last people to get worked up about issues like these. It’s hard to imagine, but I’m actually a very laid-back person.
What I’m generally not okay with is when people give up. When people go “I hate Facebook, but what can you do”. When people don’t even understand that there is a whole World Wide Web behind the fancy apps they’re using. I’m not okay with this because the Web is and has always been trivially easy to get involved with. The barrier to contributing to, or even just claiming your own little corner of the web has always been extremely, laughably low, today even more than before.
But giving up is putting all of this at risk. Giving up shows that simplicity isn’t worth fighting for. Giving up is what leads to gated marketplaces where only manufacturer-sanctioned tools, ideas and opinions are allowed. This is the Anti-Web. I don’t want it, and neither should anyone else.
Pants is just my attempt at tipping the scales the other way. As the maintainer of the project, it’s personally important to me that people use and enjoy Pants (because if they do, I’ve been doing things right), but as someone who loves the Web, I don’t really care if you use Pants or just set up your own webpage somewhere or maybe even just do something seemingly trivial like partaking in a forum outside of Facebook. The Web is important, and people should be reminded that it’s out there.
This is very very exciting to hear! Is there any way to support you without contributing code to the project? I don’t know any Ruby and I have no idea about RoR, and quite frankly not the time to put work into yet another hobby project.
It’s probably too early as this new version (the Github project is here) is still very much in flux. I’ve gone to some lengths to map out the remaining work in the issue tracker, specifically marking issues that I already know I’ll need some help with with a help-needed label. Generally, though, I’d like to roll it out first before opening it up to pull requests et al. We’re definitely talking about another couple of weeks minimum.
- Mein Blog wird aber von “normalen”, teils nicht technik-affinen Menschen gelesen und ich will ihre Kommentare Seite haben - ich weiß nicht, ob das überhaupt mit der reinen Lehre der Pants-replies zu vereinen ist.
Das “Problem” habe ich auf dem Radar. Es ist ein ziemliches Dilemma; auf der einen Seite will ich auf Pants-Sites (zumindest optional) ein einfaches Kommentarformular anbieten (wie man es von Wordpress kennt), auf der anderen Seite will ich dafür aber auch auf keinen Fall mit den grundlegenden Prinzipien brechen, die bei Pants Anwendung finden (allen voran, dass du deinen Content auf deiner Site hostest, und andere ihre Kommentare auf ihren Sites.)
Natürlich kann man nicht jeden Nutzer, der nur mal kurz einen Kommentar posten will, dazu zwingen, sich erst einmal eine eigene Pants-Site anzulegen, das ist mir bewusst. Ich habe aber eine Idee für ein IndieWeb-kompatibles Kommentarsystem, das beide Seiten des Problems prima lösen würde.
Mehr dazu, wenn es so weit ist (was noch etwas dauern kann, da ich derzeit nicht irrsinnig viel Zeit habe.) Jedenfalls habe ich das Thema auf dem Radar und will es selber gut gelöst sehen.
- Mal ganz davon abgesehen, dass ich rein vom technischen Wissen nicht in der Lage (~zu faul) bin, eine Pants-Instanz selbst zu hosten (Oder?)
Die neue Version von Pants, die ich bald ausrollen will, hat einen hervorragend funktionierenden One-Click-Installer für Heroku. Damit kann man, wenn man Pants selber hosten will, es supereinfach an den Start bringen, und hat gleich auch noch einen eigenen Fork des Codes, den man hacken kann, wenn man will.
- Ob Pants mit all den Änderungen noch so schlank sein kann, darf zumindest bedacht werden.
Nun, mir persönlich ist es extrem wichtig, Pants schlank zu halten, weswegen ich bisher zu vielen Ideen Nein sagen musste. Siehe mein Rant von gestern – Pants soll die Blogging-Engine sein, die ich benutzen möchte, und im Prinzip ist sie das auch heute schon. Und wie du weißt, habe ich an so etwas ziemlich hohe Ansprüche (naja, sonst würde ich ja auch nicht einen großen Teil meiner Freizeit in ihre Entwicklung investieren.)
But anyway, I personally feel that there is a more nuanced approach to this. Don’t get me wrong, I love me the idea of pants, but I don’t feel like this is mass marketable. We are in this mess where we abuse the web because not many people want what might be a great thing from an ideological standpoint. People like convenience. Although this is neither here nor there, I’m just a lousy underling in the machinery of the web’s destruction.
The mass market, whatever or whoever that is, will never be interested in Pants. People generally want things to be convenient first, good second; even if they claim something else, just like everyone complaining about how shitty WhatsApp is, but still keep using it (Disclaimer: I use WhatsApp and generally have no beef with it.)
It’s a mistake to think that a product just needs to solve a problem in order to be successful. If this was true, we’d all be using HTML5 web apps on our smartphones while listening to Ogg Vorbis music, etc.; in the end, convenience always wins, MP3s were easier to listen to, native apps are faster and flashier, yadda yadda.
When Ello had its 15 minutes, I almost burnt out on Pants and IndieWeb. Ello taught me that the product doesn’t matter nearly as much as the story. The Pants story wasn’t really exciting, and I’m not really in it for story, I just want to build something cool.
There was a point not too long ago when I was seriously considering dropping this project for good, as I didn’t feel I would have the energy to keep going at it, knowing that most people wouldn’t care as long as I didn’t come up with some fancy story and a possible VC.
But then I realized something: I still like to blog, and I could never use any of the other blogging engines. I dislike every single one of them, for different reasons. Pants, with its very basic structure and UI, its built-in Markdown and hashtag support, its IndieWeb features, is, to me, the perfect blogging engine, and honestly the only one I would ever want to use. Even if I ended up being the only user, I would keep building it. There is no way for me to stop, even if sometimes I feel it may cost me my sanity.
The good news is that things aren’t looking nearly as bleak as I once made them out to be. The big new version of Pants that I’m working on is shaping up nicely. It does more, has better IndieWeb support, performs better, and all with less code. The instance I will be hosting will finally offer self-signups, and if you want to run your own instance, there is a one-click install button for Heroku and a set of Docker images for everything else.
I don’t care how mass marketable Pants is. To me, it’s the best thing ever, and I can’t be stopped.
Ha! Namen für meine LFG-Plattform gefunden und die Domains gefunden. Bald geht’s ab! :-)
Mein Dragonfly scheitert an deinem SSL. Huch! Werde ich mal checken müssen.
Man, you guys would hate me if you knew what I do at my day job. Remind me to never say anything about it on #pants :p
FWIW, I currently spend most of my working time consulting tech companies that, well, let’s just say they aren’t quite aligned with what I’m doing with #pants.
I don’t consider this a problem. My day job feeds my family, and my spare-time Pants adventures hopefully contribute to keeping the web a sane place for people like myself. I’m in the lucky position that I don’t have to make a project like Pants my day job. This gives me quite a lot of control, which is something I’m enjoying very much. :)
Having said that, I have a couple of ideas how I may be able to exploit Pants commercially (without immediately “breaking” it), but I’m in absolutely no rush to turn myself into a slave of what should just be a fun little punk project.
Every now and then I give Safari another try and generally enjoy it – right up to the point where its ludicrous “Back” swipe animation reminds me that Apple really doesn’t understand the web.
I don’t even mind the actual animation itself – even though I wish I could simply disable it. What bothers me is that the page that is being displayed underneath the one you’re swiping away is merely a screenshot of the previous page, and only once the animation has completed, the actual page become active – often triggering page changes, sometimes even a full reload.
Even if the animation just lasts a puny second, it is a second that my computer is essentially lying to me about what I’m going to see next, for the sake of showing off a stupid animation that adds no value whatsoever.
Apple, you used to be cool. What happened?
Load more posts