gRegorLoveI just want to be able to inject a class="u-url" on a wiki link to [[page]], but looks like the template will just have to take the full URL and build the link.
Schnitzit could well be that the upcoming wave of silo deaths will simply drive a lot of people out of the internet and back into reality, some fraction to indieweb
aaronpkit occurs to me that now that we have people regularly joining the chat from Slack and the indiewebcamp.com web interface, we shouldn't really call this IRC anymore, since IRC is really just thing that broadcasts the messages around
[aaronpk]Argh. silo.pub checking for whether the post contains the username being mentioned is case sensitive so it added the capitalized version of the username I replied to and now that tweet looks ridiculous
petermolnarSchnitz: re "it could well be that the upcoming wave of silo deaths will simply drive a lot of people out of the internet and back into reality, some fraction to indieweb" -> https://petermolnar.eu/exodus/ last paragraph
[oliverpattison]I think this new ACM page should actually be moved to something like “AWS Certificate Manager” but I don’t know the best practice (new to this wiki) –Â does that sound right?
tanteksettings are a common silo feature that allows users to edit various aspects of their profile, including [[security]], [[privacy]], [[block]]ing, [[language]], [[notifications]], etc.
[shaners]!tell aaronpk loqi feature request: try to fetch name/contents for pasted URLs like tweet URLs. If there are mf2, give a little preview in the channel. If not, do nothing.
aaronpkhaving written code to generate this sort of "link preview" from microformats data a number of times now, I only want to write it one more time and turn it into a service so that I don't have to think about it again
[shaners]aaronpk: when you roll these services, do you also build an underlying package/library that does the core thing? So someone could re-use the functionality in their app without standing up a full service.
tantekIt's not a silo-quit, but I do see it as a silo-de-emphasis of sorts, since it's a deliberate limiting of searchability/discoverability of your FB POSSE copies, as well as who can see them by default, past/present/future.
aaronpkstep 1) back everything up. step 2) set up new mediawiki code with a copy of the database. step 3) run the upgrade script, then fiddle with updating extensions and such. step 4) swap domain names to launch the new site
tantekI have this general feeling that by taking silo profiles private, I am de-emphasizing them for public discovery, and thus shifting that emphasis for public discovery to my own site. That feels like an indieweb step forward.
petermolnartantek I've exported my FB past and manually deleted all of my {posts,likes}, nearly all of my photos, and lots of my comments; whatever was public is public on my site now, the rest is archived; no one will ever scroll back my facebook wall that far anyway, so what's the point?
tantekaaronpk: indeed. I'm trying to be very deliberate about it and documenting the steps so others can explore without having to commit (or even have a FB account)
tantekIt's more drastic because 1. you can't flip individual tweets to be public, 2. public tweets with hashtags have much more affect/discovery than public FB posts with hashtags
tantekfortnight is two weeks, the term a shortening of fo(u)rt(een-)night(s); fortnightly means every fortnight, the typical frequency of [[Homebrew Website Club]] meetups. See also [[Events]].