流量站日志
888 subscribers
132 photos
9 files
214 links
分享我如何在一周开发一个图片流量站并在一个月达到Google千万索引自然搜索达百万UV并赚取上千美刀💰然后在三个月被Google Kill的神奇经历。

也会分享一些和互联网流量相关的技术。

博客地址:https://www.bmpi.dev
被动收入电报频道:@bmpi365
学习&技术&投资电报群组:@bmpi_group
Web流量研究频道:@web_cpc
i365电报频道:@improve365

想加微信群请加improve365_cn备注TG拉群
Download Telegram
to view and join the conversation
流量站日志
Photo
https://homepages.cae.wisc.edu/~ece533/project/f06/aguilera_rpt.pdf 这篇论文对比了BMP、TIFF、PNG、JPEG、JPEG 2000的压缩比较,值得一看
jpeg和jpg是同一种格式,只因为早期Windows后缀不允许四个的后缀名
jpeg的压缩效果也不错,而且支持Safari,或许Chrome可以使用webp,而Safari可以给jpeg格式,这样存储就需要两种后缀的文件了,能不能在s3中存储png,在特定UA的浏览器请求时给予不同的格式的图片呢?可以研究下
user->browser->js check ua->imgix(image convert api)->s3
流量站日志
imgix处理1000个图片3美刀,太贵了
user->browser->js check ua->aws lambda->s3 这种方案应该便宜一些
https://docs.aws.amazon.com/solutions/latest/serverless-image-handler/overview.html AWS的图片处理方案还是便宜,1 million images processed, 15 GB storage and 50 GB data transfer也才不到90块钱人民币
流量站日志
https://medium.com/nona-web/converting-images-to-webp-from-cdn-9433b56a3d52
1. Listen for requests to CDN, and trigger a Lambda function that hijacks any viewer request.
2. Determine if the request event is for an image and if the browser requesting the resource supports WebP based on the user-agent we receive from the request.
3. If we determine that the request is for an image and that the browser supports WebP, we replace it with therequest uri image extension with .webp and add the original extension into the request header
4. Next, we trigger a separate Lambda that hijacks any CDN origin response.
5. If the request uri on the response event has a .webp extension, and the response status is a 404, we check our S3 bucket for the same image, but with the original extension, we placed into our request header in step 3.
6. If we find an image with the original extension in S3, we run a WebP conversion using Sharp and place it in the origin response, otherwise, we leave the 404 response unaltered.
流量站日志
1. Listen for requests to CDN, and trigger a Lambda function that hijacks any viewer request. 2. Determine if the request event is for an image and if the browser requesting the resource supports WebP based on the user-agent we receive from the request. 3.…
aws lambda edge查看器请求大小不能超过1MB,而源响应却可以很大,所以在打包的时候尤其注意不要将node module打包到查看器请求zip包中(这个大坑花了半天时间)
流量站日志
https://bloggingwizard.com/push-notifications/
浏览器通知🆚邮件订阅,前者比后者ROI高2-10倍,博客可以考虑优先支持浏览器通知
流量站日志
https://github.com/LouisBarranqueiro/hexo-theme-tranquilpeak/issues/387
You will need a server (or service) in the middle. Remember that Hexo just generate static site and there is no "action" beyond HTML transfer from the server where you host your site. That being said, one alternative you can try is to design a deployment plugin for hexo that actually send a message through a push service API. That would be simple to accomplish and your readers only have to subscribe to that push service (ie. Google Cloud Message, NMA, etc).
Other option: AWS SNS can be used to implement a push service and/or/mixed email/sms messaging. You will have to setup a queue, push to it on hexo deploy, and design a interface that can subscribe your readers to a list of recipients. I never used it as push service but I do use it to notify me after a success/failure hexo generate on travis-ci. This is paid option and I know there are other suppliers already prepared as push service, you just need use their API.
IFTTT integration: Use your RSS feed on a IFTTT applet to trigger a push notification through one of the available services (like notify my droid, etc).
Other idea: Telegram Channel and a ChatBot (switch Telegram for: skype, facebook messenger, slack or other way a "chatBot" can push messages to). I use this to be notified by my homeTheather system when a new episode of my favorite TV Show is available. To accomplish this I wrote a microservice that receive a HTTP request and send it as message to me (or family group chat in my case) through a Telegram ChatBot. Telegram offers a thing called Channel, it is like a whatzapp group chat but only Channel owner can write message while all other members can just receive that message. (very similar to a Push notification). The microservice I wrote is way too simple written (badly) in NodeJS, runs for free on Hook.io but could be run on AWS Lambda or Google Cloud Function, App Engine, Heroku or any other, few modifications needed.
Based on the microservice idea above and a mix of push service or IFTTT I think it should be pretty simple to have a deploy plugin for hexo where the deploy action is a simple API call or a HTTP request to specified URL and PUSH messages would be sent way. The worst part, IMHO, would be to elect a push service free for the subscribers (your reader) and with no need to install apps (many would no use if they have to install a new app just because of you).