Thinking of redoing this (sigh)
https://developers.facebook.com/docs/pages/getting-started
The curl command:
-i include headers
-X POST use method
or maybe
https://developers.facebook.com/docs/sharing/reference/send-dialog
But then:
The publish_actions permission will be deprecated. This permission
granted apps access to publish posts to Facebook as the logged in
user. Apps created from today onwards will not have access to this
permission. Apps created before today that have been previously
approved to request publish_actions can continue to do so until
August 1, 2018. No further apps will be approved to use
publish_actions via app review. Developers currently utilizing
publish_actions are encouraged to switch to Facebook's Share dialogs
for web, iOS and Android.
https://developers.facebook.com/blog/post/2018/04/24/new-facebook-platform-product-changes-policy-updates/
---
NOTE: A lot of this is outdated information, but kept here for hysterical
rasins.
https://community.letsencrypt.org/t/end-of-life-plan-for-acmev1/88430
---
2019-04-28T16:54:00-05:00
https://dev.to/kenbellows/stop-using-so-many-divs-an-intro-to-semantic-html-3i9i
Using HTML5.
---
2019-03-30T20:46:00-05:00
Yup. To add to that, posting a reply to your own blog and setting
rel=“in-reply-to” and notifying the author with Webmention provides standard
decentralized comments/notifications. See aaronparecki.com and the indieweb
community for examples.
also
https://news.ycombinator.com/item?id=19532614
2018-04-03T21:43-05:00
Webmention:
https://webmention.rocks/
https://indieweb.org/Webmention-developer
https://www.w3.org/TR/webmention/
Meta information for HTML5
check source of view-source:https://tommorris.org/pages/blogroll
https://indieweb.org/lost_infrastructure
2007-08-29T16:44-05:00
About adding backlinks in old entries to new entries, one thing to
keep in mind is to put said links at the top, according to
http://www.wordyard.com/2007/08/28/can-newspapers-fix-old-errors/#comment-978
2016-12-23T03:28-05:00
After spending a few hours on this, I realized that it would be
harder than expected to support. I would either have to seriously
restructure the code to support this feature, or parse the entry
twice, which is doable, but doesn't sit well with me.
So, I'm putting this here in the notes, where it will languish for
years, instead of in the TODO, where it did languish for years.
---
http://www.eglug.org/book/export/html/1923
http://10up.github.io/Engineering-Best-Practices/css/#syntax-formatting
https://www.google.com/webmasters/tools/mobile-friendly/
http://googlewebmastercentral.blogspot.com/2014/11/helping-users-find-mobile-friendly-pages.html
http://googlewebmastercentral.blogspot.com/2015/02/finding-more-mobile-friendly-search.html
https://developers.google.com/web/fundamentals/layouts/?hl=en
https://css-tricks.com/snippets/css/media-queries-for-standard-devices/
http://stackoverflow.com/questions/3839809/detect-iphone-ipad-purely-by-css
http://stackoverflow.com/questions/14914407/css-detect-either-iphone-ipad-or-any-other-handheld
https://news.ycombinator.com/item?id=9413992
http://ogp.me/
http://openlike.org/
(uses http://www.w3.org/TR/rdfa-core/)
Maybe integrate discount (see ~/apps) as a filter.
http://www.pell.portland.or.us/~orc/Code/markdown/
How about this:
#define --- —
#define -- –
#define `` ‘
#define '' ”
#define ... …
or some similar type of declaration for inputing data?
see 2007/01/09.1 for some details
----------
restructuring both bp.c and addentry.c
int main(int argc,char *argv[])
{
Cgi cgi;
MemInit();
BufferInit();
DdtInit();
CleanInit();
if (CgiNew(&cgi,NULL) == ERR_OKAY)
{
switch(CgiMethod(cgi))
{
case GET: rc = main_cgi_get (cgi,argv,argc); break;
case POST: rc = main_cgi_post(cgi,argv,argc); break;
default: rc = XXX ; break;
}
}
else
rc = main_cli(argc,argv);
return(rc);
}
int main_cgi_get(Cgi cgi,int argc,char *argv[])
{
}
int main_cgi_post(Cgi cgi,int argc,char *argv[])
{
}
int main_cli(int argc,char *argv[])
{
}
GET:
$PATH_INFO tumbler
POST:
email = 'yes' | 'no'
filter = 'text' | 'mixed' | 'html'
update = 'new' | 'modify' | 'edit' | 'template' | 'other'
author = string || $REMOTE_USER
title = string
class = string
date = string
body = string
cmd = --> 'new' | 'show' | 'edit' | 'delete'
PUT:
DELETE:
CLI:
--config filespec
--cmd 'new' | --> 'show' [ | 'edit' | 'delete' ]
--file input
--stdin read from stdin
--email read from stdin as email
--update --> 'new' | 'modify' | 'edit' | 'template' | 'other'
--entry tumbler
-------------------------------------------------------------------
Permissions for transcluding----look into adding a query string with
permissions.
Adding comments.
Adding a new field to struct blogentry
typdef struct blogentry
{
Node node;
char *date;
int number;
char *title;
char *class;
char *author;
size_t bsize;
void *body;
int comments; /* new field */
BlogEntry *entries;
} *BlogEntry;
Okay, and use the existing infrastructure for the comments. This means
that we *can* have comments on comments, but we'll leave that for later.
URL space wise, I might want to just limit the comments to individual days
(I'm not trying for the Talmudic software yet). So we have:
/2003/2/14/comments --illegal (return 404)
/2003/2/14.1/comments --yes, all comments
/2003/2/14.1/comments/1 -- first comment
/2003/2/14.1/comments/1-3 -- first three comments
Hmmm ... maybe ...
/2003/2/14.1 -- just the entry
/2003/2/14.1/ -- entry + return all comments?
/2003/2/14.1/1 -- first comment
/2003/2/14.1/1-3 -- first three comments
/2003/2/14.1/1/ -- first comment + all 2l comments
/2003/2/14.1/1/1 -- first 2l comment
/2003/2/14.1/1/1-3 -- first three 2l comments
I like this idea. Will have to expand the tumblers to support this, but
that shouldn't be too difficult.
blog stuff:
...
from http://www.tantek.com/log/2002/11.html#L20021124t1454
added
Talmud---the study
Mishna (text)
Gemara (commentaries on text)
TODO:
Return error upon requests for entries before
first, or after current day.
Fix local link code---if it starts with `/', then
it's probably not under journal storage.
+ fix internal links for both entries and files
+ done
NOTES: